From: grischka <grishka@gmx.de>
To: jasonr@f2s.com
Cc: 1348@emacsbugs.donarmstrong.com
Subject: bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows
Date: Tue, 02 Dec 2008 15:11:23 +0100 [thread overview]
Message-ID: <4935420B.5060706@gmx.de> (raw)
In-Reply-To: <1228203763.4934e6f38c1b2@webmail.freedom2surf.net>
jasonr wrote:
> Quoting grischka:
>
>> Below is a patch that fixes the problem on windows.
>
> I believe this patch is incorrect, as it will result in the message handling
> code running in the context of the Lisp thread, which will result in a whole
> host of unreproducable crashing bugs if left like that. Probably the reason it
> seems to work is that it introduces a delay that is generally long enough for
> the real resizing or moving to take place before the Lisp thread continues.
Believes are not an approach to code, coincidentally none of the above
do apply.
> Inter-thread synchronization is what is needed here to fix this safely and
> deterministically.
Nicely put. This is the theory.
(As to practical things that need fixing:
HRGN orig_clip;
GetClipRgn(s->hdc, orig_clip);
Or:
for (i = 0; i < len; i++)
ExtTextOutW (s->hdc, x + i, y, options, NULL,
s->char2b + from + i, 1, NULL);
)
next prev parent reply other threads:[~2008-12-02 14:11 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4935420B.5060706@gmx.de \
--to=grishka@gmx.de \
--cc=1348@emacsbugs.donarmstrong.com \
--cc=jasonr@f2s.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).