>>>>> On Sat, 15 Jul 2006 11:47:15 +0300, Eli Zaretskii <[EMAIL PROTECTED]>
>>>>> said:
>> > The default value should still reflect what's appropriate for the platform,
>> > even if for most purposes it's ignored by the OS. The OS might not DTRT,
>> > but
>> > the behavior of Emacs code depends on the value of Emacs variables. For
>> > instance, doesn't it make a difference here? I think it does.
>> >
>> > (defun select-frame-set-input-focus (frame)
>> > "Select FRAME, raise it, and set input focus, if possible."
>> > (select-frame frame)
>> > (raise-frame frame)
>> > ;; Ensure, if possible, that frame gets input focus.
>> > (cond ((eq window-system 'x) (x-focus-frame frame))
>> > ((eq window-system 'w32) (w32-focus-frame frame)))
>> > (cond (focus-follows-mouse
>> > (set-mouse-position (selected-frame)
>> > (1- (frame-width)) 0)))))
> If so, I must ask you: did you actually tried this code? ("C-x 5 o"
> calls this function, so it would suffice to try that command.) I did
> try it, with both nil and t as values of focus-follows-mouse, and I
> don't see _any_ change in behavior whatsoever.
Let me confirm one thing. The value doesn't affect the behavior with
respect to the mouse position on W32, either? I'm asking because I'm
thinking about setting its default to nil on Mac Carbon, because if
the value is t, "C-x 5 o" moves the mouse pointer to the upper-right
corner of the focused frame.
YAMAMOTO Mitsuharu
[EMAIL PROTECTED]
_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
