From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: grischka Newsgroups: gmane.emacs.devel Subject: Re: GTK frame changes Date: Thu, 02 Jul 2009 19:46:12 +0200 Message-ID: <4A4CF264.6040306@gmx.de> References: <4A4CADCB.8000304@gmx.de> <4A4CC3D7.40109@swipnet.se> <4A4CD73D.2080802@gmx.de> <4A4CDDF2.4030608@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1246556796 472 80.91.229.12 (2 Jul 2009 17:46:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Jul 2009 17:46:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?UTF-8?B?SmFuIERqw6Rydg==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 02 19:46:29 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MMQMd-0003Ew-EN for ged-emacs-devel@m.gmane.org; Thu, 02 Jul 2009 19:46:27 +0200 Original-Received: from localhost ([127.0.0.1]:33730 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMQMc-0004PR-RS for ged-emacs-devel@m.gmane.org; Thu, 02 Jul 2009 13:46:26 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MMQMY-0004OM-9K for emacs-devel@gnu.org; Thu, 02 Jul 2009 13:46:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MMQMT-0004Ml-Ef for emacs-devel@gnu.org; Thu, 02 Jul 2009 13:46:21 -0400 Original-Received: from [199.232.76.173] (port=58702 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMQMT-0004Mi-9P for emacs-devel@gnu.org; Thu, 02 Jul 2009 13:46:17 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:45731) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MMQMS-0006Ew-Lt for emacs-devel@gnu.org; Thu, 02 Jul 2009 13:46:17 -0400 Original-Received: (qmail invoked by alias); 02 Jul 2009 17:46:14 -0000 Original-Received: from p57A0813F.dip0.t-ipconnect.de (EHLO [192.168.1.2]) [87.160.129.63] by mail.gmx.net (mp025) with SMTP; 02 Jul 2009 19:46:14 +0200 X-Authenticated: #18588216 X-Provags-ID: V01U2FsdGVkX188IS9Y/XE8DZMujm7RjKVUCr2hNo6ABIgucke4IP 14ZT8EKYRNUX9B User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <4A4CDDF2.4030608@swipnet.se> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.62 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:111917 Archived-At: Jan Djärv wrote: > > > grischka skrev: >> Jan Djärv wrote: >>> grischka skrev: >>>> Jan Djärv 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. Yes, but this reply is something in the sense of the X protocol, not in the sense of ConfigureNotify. It just means that the X server got the resize message when XSync returns. It doesn't mean at all that a ConfigureNotify is already in the client queue let alone that emacs now knows how big it is. --- grischka > > Jan D. >