From: David Chamberlain <dc46and2@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin@cygwin.com
Subject: Re: Fullscreen application with Cygwin/X in multiwindow mode
Date: Thu, 01 Dec 2016 15:10:00 -0000 [thread overview]
Message-ID: <CAHvVhSuzm_ePaMtra-hGS8fjUN9+AvOf6RrMzeWFqGpk_yRaXg@mail.gmail.com> (raw)
In-Reply-To: <b133f87a-3c84-9085-03cd-926ae0dcb1f6@dronecode.org.uk>
On Thu, Dec 1, 2016 at 6:23 AM, Jon Turney <jon.turney@dronecode.org.uk> wrote:
> Patches are always welcome.
>
> I think this should be pretty straightforward to add, although it might be a
> bit tedious.
>
> [1],[2] should help you get started :)
>
> Looking at this in a little more detail, I wasn't quite accurate in my
> statement above: There is very limited support for this state, in that
> windows which are created with it are probably shown correctly.
>
> I think what's needed is extend the handling of _NET_WM_STATE messages so it
> can handle a window being changed to _NET_WM_STATE_FULLSCREEN. (At the
> moment _NET_WM_STATE is, only handled when it can be mapped down to an
> equivalent WM_CHANGE_STATE message, see [3])
>
> [1] https://x.cygwin.com/docs/cg/cygwin-x-cg.html
> [2] https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html
> [3]
> https://cgit.freedesktop.org/~jturney/xserver/commit/?h=cygwin-release-1.19&id=55c2ca8cd9287850077102d4ba662cfd2c571ca9
Thanks for the references. I'll see if I can come up with a patch.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-12-01 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 8:06 David Chamberlain
2016-11-25 2:50 ` Jon Turney
2016-11-29 14:12 ` David Chamberlain
2016-11-29 14:29 ` Andrey Repin
2016-12-01 12:23 ` Jon Turney
2016-12-01 15:10 ` David Chamberlain [this message]
2016-12-01 15:07 ` David Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHvVhSuzm_ePaMtra-hGS8fjUN9+AvOf6RrMzeWFqGpk_yRaXg@mail.gmail.com \
--to=dc46and2@gmail.com \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).