all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: grischka <grishka@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: GTK frame changes
Date: Thu, 02 Jul 2009 18:18:58 +0200	[thread overview]
Message-ID: <4A4CDDF2.4030608@swipnet.se> (raw)
In-Reply-To: <4A4CD73D.2080802@gmx.de>



grischka skrev:
> Jan Djärv wrote:
>> grischka skrev:
>>> Jan Djärv <jan.h.d@swipnet.se> wrote in Changelog:
>>>
>>>> xg_frame_set_char_size): Do not set pixel width/height here or
>>>> call change_frame_size. Just call flush_and_sync.
>>>> (flush_and_sync): Reintroduced.
>>>
>>> Nice work and the idea is right IMO, just the problem remains that
>>> "flush_and_sync()" does not guarantee that the resize request was
>>> actually handled,  i.e. that a ConfigureNotify was received before
>>> flush_and_sync() returns.  In my tests in ~70% of runs this is not
>>> the case.
>>
>> No, it is not certain.  But if the X server handles requests from 
>> clients in sequence (which it should), it is certain.  
> 
> What makes you think that flush_and_sync would work if requests are
> handled sequentially by the X server?
> 

XSync sends a request to the server and waits for a reply.  The resize request 
is sent before that, so the resize should be handeled before the XSync reply 
is sent.

	Jan D.




  reply	other threads:[~2009-07-02 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 12:53 GTK frame changes grischka
2009-07-02 14:27 ` Jan Djärv
2009-07-02 15:50   ` grischka
2009-07-02 16:18     ` Jan Djärv [this message]
2009-07-02 17:46       ` grischka
2009-07-02 19:44         ` Jan Djärv
2009-07-03 10:53           ` grischka
2009-07-03 11:37             ` Jan Djärv
2009-07-03 12:14             ` Stephen J. Turnbull
2009-07-03 12:43               ` Jan Djärv
2009-07-03 12:47               ` Stephen J. Turnbull

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=4A4CDDF2.4030608@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=grishka@gmx.de \
    /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.