From: martin rudalics <rudalics@gmx.at>
To: Erik Charlebois <erikcharlebois@gmail.com>
Cc: 14180@debbugs.gnu.org
Subject: bug#14180: PATCH Better fullscreen frame support on Windows
Date: Sat, 13 Apr 2013 10:03:09 +0200 [thread overview]
Message-ID: <5169113D.7040801@gmx.at> (raw)
In-Reply-To: <CAC+abJbzLG0N+GeTfYW05Do91z6jzHQxWqZwwYSLA5_QPmZhmA@mail.gmail.com>
> That's correct. The modeline scrollbar is slightly clipped.
It's because we currently do not distribute spare pixel lines to other
windows but simply append them at the end of the mode-line without,
however, storing the pixel height in the window. The display engine
doesn't know anything about this and therefore cannot draw the scroll
bar long enough. I suppose the remaining pixel lines of the screen are
cleared by Windows using FRAME_BACKGROUND_PIXEL but never checked that.
Here I changed the behavior by appending the extra pixel lines to the
windows that "most need it".
> I just doubled checked toggling scrollbars, menubar and toolbar on and off
> while in fullscreen and it all works as expected.
>
> Thanks for the reminder since I usually run with all those elements off :).
I intended to ask you that too. At least some of these can have very
nasty delayed effects (at least with the old maximized/fullscreen mode).
In particular, independently setting margin widths and scrollbar widths
and the internal border widths of frames.
martin
next prev parent reply other threads:[~2013-04-13 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 4:59 bug#14180: PATCH Better fullscreen frame support on Windows Erik Charlebois
2013-04-12 9:28 ` martin rudalics
2013-04-12 19:32 ` Erik Charlebois
2013-04-13 8:03 ` martin rudalics [this message]
2013-04-13 10:09 ` Eli Zaretskii
2013-04-13 11:33 ` Jan Djärv
2013-04-13 11:56 ` Eli Zaretskii
2013-04-14 1:23 ` Erik Charlebois
2013-04-14 6:41 ` Eli Zaretskii
2013-04-20 0:42 ` Erik Charlebois
2013-04-20 7:36 ` Eli Zaretskii
2013-04-20 14:34 ` Stefan Monnier
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=5169113D.7040801@gmx.at \
--to=rudalics@gmx.at \
--cc=14180@debbugs.gnu.org \
--cc=erikcharlebois@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.