>>>> "Kyle" == Kyle Jones
<kyle_jones(a)wonderworks.com> writes:
Kyle>
Kyle> Hrvoje Niksic writes:
> Kyle Jones <kyle_jones(a)wonderworks.com> writes:
>
> > focus-frame is still crocked with regard to the frame selection
> > hooks which means it may have to be commented out for the release.
>
> It passed my initial tests. It should be no more broken than
> `select-frame', because it (among other things) actually *calls*
> select-frame.
>
> Do you have a specific repeat-by procedure?
Kyle>
Kyle> focus-follows-mouse == nil
Kyle>
Kyle> Make three frames and
Kyle>
Kyle> (add-hook 'deselect-frame-hook 'redraw-frame)
Kyle>
Kyle> Then use focus-frame to focus on another frame. The redraw happens
Kyle> in the wrong frame.
Hi Kyle,
I've been looking into this using
(add-hook 'deselect-frame-hook (lambda () (insert "deselect\n")))
since my redraw-frame is too fast to really notice. I can reproduce
this bug, however, the same bug exists for select-frame. I am quite
confident that my focus changes didn't change the behavior when
focus-follows-mouse is nil, so I guess it's been broken a while. I
happen to have 20.0-b28 (comes with sparcworks) and it also exhibits
this bug with select-frame. This XEmacs version seems to pre-date
focus-follows-mouse.
Kyle> If instead you add redraw-frame to select-frame-hook and use
Kyle> focus-frame, the correct frame gets the redraw. But if you then
Kyle> move the mouse into a third frame, the first frame (the one that
Kyle> used to have the focus) is redrawn, which suggests some internal
Kyle> confusion about which frame is being selected.
I am unable to reproduce this. I used the analogous hook and
everything seems to be behaving correctly.
greg