all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: grischka <grishka@gmx.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 1348@emacsbugs.donarmstrong.com
Subject: bug#1348: set-frame-width and set-frame-position seem buggy on at	least MSWindows
Date: Sun, 30 Nov 2008 18:40:15 +0100	[thread overview]
Message-ID: <4932CFFF.6000204@gmx.de> (raw)
In-Reply-To: <49325AAA.5090606@gmx.at>

martin rudalics wrote:

>  >> I have never looked into that code.  IIUC one problem is flickering 
> when
>  >> a frame gets redrawn too often.  Moreover, it's not always safe to
>  >> redraw frames.
>  >
>  > Redraw? Isn't this about resize rather than redraw?
> 
> You can, in one command, issue a number of resize requests.  I doubt we
> want each of them cause a redisplay/redraw before the command completes.

But who said anything about redisplay/redraw?  What it needs to
wait for is the notification from the window system or toolkit
that the resize request was carried out.

Otherwise emacs runs into situations where the state of it's
internal variables w.r.t. frame size/position is not consistent
with the state of the GUI, and in consequence the inconsistent
GUI state works back on these variables.  (by means of the logic
meant for mouse sizing/dragging)

I guess that is the basic problem. There may be additional aspects
like toolkit differences or race conditions.







  reply	other threads:[~2008-11-30 17:40 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 21:22 bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows grischka
2008-11-27 13:41 ` martin rudalics
2008-11-27 17:45   ` grischka
2008-11-27 19:48     ` martin rudalics
2008-11-29 19:42       ` grischka
2008-11-30  9:19         ` martin rudalics
2008-11-30 17:40           ` grischka [this message]
2008-11-30 20:02             ` martin rudalics
2008-11-30 22:04               ` grischka
2008-11-30 22:50                 ` martin rudalics
2008-11-30 23:08                   ` grischka
2008-11-30 23:54           ` jasonr
2008-12-01  7:28             ` martin rudalics
2008-12-01  8:22               ` jasonr
2008-12-01  9:34                 ` martin rudalics
2008-12-02  6:11                   ` grischka
2008-12-02  7:42                     ` jasonr
2008-12-02 14:11                       ` grischka
2008-12-02 15:54                     ` martin rudalics
2008-12-02 20:04                       ` Eli Zaretskii
2008-12-03 10:17                         ` martin rudalics
2008-12-03 18:32                           ` Eli Zaretskii
2008-12-04 18:00                             ` martin rudalics
2008-12-16 17:11                               ` grischka
2008-12-03  0:09                       ` grischka
2008-12-03 10:17                         ` martin rudalics
2008-12-03 17:24                           ` grischka
2008-12-03 21:41                             ` Stefan Monnier
2008-12-04 17:58                             ` martin rudalics
2008-12-04 23:24                               ` grischka
2008-12-05  6:20                                 ` Eli Zaretskii
2008-12-05 15:58                                   ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 21:43 grischka
2008-12-04  4:07 ` Eli Zaretskii
2008-11-17 15:06 grischka
2008-11-14 22:46 Themba Fletcher
2008-11-15  9:40 ` Eli Zaretskii
2008-11-15 10:04   ` Eli Zaretskii
2008-11-15 14:12     ` martin rudalics
2008-11-17 20:50   ` Themba Fletcher
2008-11-18 13:03     ` martin rudalics
2014-09-21 18:02 ` martin rudalics

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=4932CFFF.6000204@gmx.de \
    --to=grishka@gmx.de \
    --cc=1348@emacsbugs.donarmstrong.com \
    --cc=rudalics@gmx.at \
    /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.