Mercurial > emacs
view admin/notes/BRANCH @ 93070:d94ac0f6a006
* w32fns.c (hourglass_timer, hourglass_hwnd): New variables.
(syms_of_w32fns): Initialize them.
(HOURGLASS_ID): New constant.
(x_window_to_frame): Don't check hourglass_window.
(w32_wnd_proc) <WM_TIMER>: Handle hourglass_timer.
(w32_wnd_proc) <WM_EXITMENULOOP>: Set pending hourglass cursor.
(w32_wnd_proc) <WM_SETCURSOR>: Set the hourglass or current cursor.
(w32_wnd_proc) <WM_EMACS_SETCURSOR>: Set frame's current_cursor.
Only change the cursor if hourglass is not active.
(Fx_create_frame): Initialize frame's current_cursor.
(hourglass_atimer): Remove.
(hourglass_started): New function.
(start_hourglass, cancel_hourglass, hide_hourglass): Adapt to w32.
(show_hourglass): Adapt to w32, changing argument to frame.
* w32term.h (struct w32_output): Remove hourglass_window.
Add current_cursor.
* eval.c (call_debugger, Fsignal):
* keyboard.c (recursive_edit_1, cmd_error, Ftop_level)
(command_loop_1, Fread_key_sequence, Fread_key_sequence_vector)
(Fexecute_extended_command, cancel_hourglass_unwind):
* minibuf.c (read_minibuf):
* fns.c (Fy_or_n_p): Enable hourglass when HAVE_WINDOW_SYSTEM.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Wed, 19 Mar 2008 17:02:22 +0000 |
parents | 7dd2d0d806e8 |
children | b2b85b22b20e 8080c98e919f |
line wrap: on
line source
This file describes the CVS branch in which it is maintained. Everything below the line is branch-specific. ________________________________________________________________________ This is the "HEAD" branch, otherwise known as the "trunk". Its primary purpose is to accumulate changes that are not yet partitioned into a specific (versioned) release. When people say "use CVS emacs", this is the branch they are talking about. Likewise, a "cvs checkout" without the "-r" option results in this branch. The plans for this branch are not specified; Emacs hackers add to it relatively free of constraint (aside from proper legal / accounting practices), although sometimes there is related discussion on the emacs-devel mailing list. The closure process for this branch is undocumented; concepts such as "freeze", "release", or "integration with the trunk" are not applicable to this branch.