2:26 p.m.
Andy Piper <andy(a)xemacs.org> writes:
>(save-current-window
What's this --^^^^?
I meant save-selected-window
Moreover I can't see any redisplay optimizations you refer to.
Why not?
Sure redisplay doesn't kick in till events trigger, but this
cannot
be true for widgets - you have to modify properties when you are
asked to and this will cause some flicker.
Why can you do make changes to the internal structure and then have
the visual representation sync up with them at with redisplay time?
That is what happens with all the other stuff?
I wonder whether we could do some specific optimization
of this particular case (e.g. not call update-tab-in-gutter if we are in a
window-excursion)?
I looked at that, but save-selected-window is bitch in that (just a
macro).
I still wonder why all that code uses select-window. Maybe there
should be a set-window just like set-buffer vs switch-to-buffer?
Jan
5:27 p.m.
New subject: Gutter redisplay too agressive.
At 03:26 PM 12/23/99 +0100, Jan Vroonhof wrote:
Why can you do make changes to the internal structure and then have
the visual representation sync up with them at with redisplay time?
That is what happens with all the other stuff?
This happens with redisplay artifacts that we have control over, but
widgets are beyond my control - its up to the toolkit to decide when to
display or not :)
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd
12:11 a.m.
New subject: Gutter redisplay too agressive.
Jan Vroonhof writes:
I still wonder why all that code uses select-window.
Speaking for VM, the answer is that the scrolling routines scroll-up
and scroll-down operate on the selected window. Otherwise I would
avoid using select-window, because it reorders the buffer list.
There's also window configuration. Both VM and GNUS offer
sophisticated windwo configuration options. In the case of VM,
the last action of the procedure that applies a configuration to
the display is to call select-window.
8:10 a.m.
New subject: Gutter redisplay too agressive.
At 04:11 PM 12/23/99 -0800, Kyle Jones wrote:
Jan Vroonhof writes:
> I still wonder why all that code uses select-window.
Speaking for VM, the answer is that the scrolling routines scroll-up
and scroll-down operate on the selected window. Otherwise I would
avoid using select-window, because it reorders the buffer list.
I'm still keen to fix this in lisp, maybe by turning off the gutter update
if we are in a window excursion.
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd
12:54 a.m.
New subject: Gutter redisplay too agressive.
Andy Piper writes:
At 04:11 PM 12/23/99 -0800, Kyle Jones wrote:
>Jan Vroonhof writes:
> > I still wonder why all that code uses select-window.
>
>Speaking for VM, the answer is that the scrolling routines scroll-up
>and scroll-down operate on the selected window. Otherwise I would
>avoid using select-window, because it reorders the buffer list.
I'm still keen to fix this in lisp, maybe by turning off the gutter update
if we are in a window excursion.
I think we should do what redisplay does. Record the changes that
should affect the gutter as they happen, but only compute and display
the results when the system goes idle, i.e. when XEmacs is waiting
for an event. I think this means that update-tab-in-gutter shoudl be
on pre-idle-hook, and should be smarter about whether an update needs
to happen or not.
2:04 p.m.
New subject: Gutter redisplay too agressive.
At 04:54 PM 12/24/99 -0800, Kyle Jones wrote:
I think we should do what redisplay does. Record the changes that
should affect the gutter as they happen, but only compute and display
the results when the system goes idle, i.e. when XEmacs is waiting
for an event. I think this means that update-tab-in-gutter shoudl be
on pre-idle-hook, and should be smarter about whether an update needs
to happen or not.
I think what I need to do is fix set-image-instance-property to record hte
desired change but not actually do it until update_subwindow gets called.
This is now true for subwindow resizing but not for properties.
Its easy to fix under X, less so for mswindows .....
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd
9079
days inactive
9101
days old
5 comments
3 participants
participants (3)
-
Andy Piper -
Jan Vroonhof -
Kyle Jones