Match the effect of FULLSCREEN_BOTH and FULLSCREEN_MAXIMIZED to docs on Windows.
src/w32term.c (w32fullscreen_hook): Swap FULLSCREEN_BOTH and FULLSCREEN_MAXIMIZED. Fixes: debbugs:13935
This commit is contained in:
parent
4e2df81da5
commit
5f795e34b3
3 changed files with 10 additions and 4 deletions
|
@ -632,8 +632,9 @@ possible. The value @code{fullboth} specifies that both the width and
|
|||
the height shall be set to the size of the screen. The value
|
||||
@code{maximized} specifies that the frame shall be maximized. The
|
||||
difference between @code{maximized} and @code{fullboth} is that the
|
||||
former still has window manager decorations while the latter really
|
||||
covers the whole screen.
|
||||
former can still be resized by dragging window manager decorations
|
||||
with the mouse, while the latter really covers the whole screen and
|
||||
does not allow resizing by mouse dragging.
|
||||
@end table
|
||||
|
||||
@node Layout Parameters
|
||||
|
|
|
@ -1,3 +1,8 @@
|
|||
2013-03-15 Eli Zaretskii <eliz@gnu.org>
|
||||
|
||||
* w32term.c (w32fullscreen_hook): Swap FULLSCREEN_BOTH and
|
||||
FULLSCREEN_MAXIMIZED. (Bug#13935)
|
||||
|
||||
2013-03-15 Dmitry Antipov <dmantipov@yandex.ru>
|
||||
|
||||
* region-cache.c (find_cache_boundary, move_cache_gap)
|
||||
|
|
|
@ -5682,10 +5682,10 @@ w32fullscreen_hook (FRAME_PTR f)
|
|||
|
||||
switch (f->want_fullscreen)
|
||||
{
|
||||
case FULLSCREEN_MAXIMIZED:
|
||||
case FULLSCREEN_BOTH:
|
||||
PostMessage (FRAME_W32_WINDOW (f), WM_SYSCOMMAND, SC_MAXIMIZE, 0);
|
||||
break;
|
||||
case FULLSCREEN_BOTH:
|
||||
case FULLSCREEN_MAXIMIZED:
|
||||
height =
|
||||
FRAME_PIXEL_HEIGHT_TO_TEXT_LINES (f, pixel_height)
|
||||
- XINT (Ftool_bar_lines_needed (selected_frame))
|
||||
|
|
Loading…
Add table
Reference in a new issue