From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: [mituharu@math.s.chiba-u.ac.jp: Re: silent PC vs. emacs]
Date: Tue, 05 Sep 2006 13:40:43 +0200 [thread overview]
Message-ID: <44FD623B.3020701@swipnet.se> (raw)
In-Reply-To: <E1GKXSf-0002dX-EV@fencepost.gnu.org>
Richard Stallman skrev:
> Does anyone see a problem with this?
> Can anyone confirm it is correct?
>
...
> #endif /* USE_X_TOOLKIT */
> - --- 10818,10857 ----
> x_process_timeouts (timer)
> struct atimer *timer;
> {
> + BLOCK_INPUT;
> if (toolkit_scroll_bar_interaction || popup_activated ())
> {
> while (XtAppPending (Xt_app_con) & XtIMTimer)
> XtAppProcessEvent (Xt_app_con, XtIMTimer);
> ! /* Reactivate the atimer for next time. */
> ! x_activate_timeout_atimer ();
This won't reactivate the timer because x_timeout_atimer_activated_flag is 1 ...
> }
> + else
> + x_timeout_atimer_activated_flag = 0;
> + UNBLOCK_INPUT;
> + }
> +
> + /* Install an asynchronous timer that processes Xt timeout events
> + every 0.1s as long as either `toolkit_scroll_bar_interaction' or
> + `popup_activated_flag' (in xmenu.c) is set. Make sure to call this
> + function whenever these variables are set. This is necessary
> + because some widget sets use timeouts internally, for example the
> + LessTif menu bar, or the Xaw3d scroll bar. When Xt timeouts aren't
> + processed, these widgets don't behave normally. */
> +
> + void
> + x_activate_timeout_atimer ()
> + {
> + BLOCK_INPUT;
> + if (!x_timeout_atimer_activated_flag)
... so this test will fail.
> + {
> + EMACS_TIME interval;
> +
> + EMACS_SET_SECS_USECS (interval, 0, 100000);
> + start_atimer (ATIMER_RELATIVE, interval, x_process_timeouts, 0);
> + x_timeout_atimer_activated_flag = 1;
> + }
> + UNBLOCK_INPUT;
> }
Jan D.
next prev parent reply other threads:[~2006-09-05 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 9:43 [mituharu@math.s.chiba-u.ac.jp: Re: silent PC vs. emacs] Richard Stallman
2006-09-05 11:40 ` Jan Djärv [this message]
2006-09-06 0:39 ` YAMAMOTO Mitsuharu
2006-09-06 4:50 ` Jan Djärv
2006-09-05 18:36 ` Eli Zaretskii
2006-09-07 21:15 ` Richard Stallman
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=44FD623B.3020701@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
/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.