Re: Progress bars + events [Re: crash when using W3]
At 11:58 PM 4/5/00 -0700, Ben Wing wrote:
the problem here is andy's event code.
andy, i'm not sure i really believe that you need to cycle the event code
to
get
widgets to redisplay, but in any case you should
Why do you find this hard to believe. Surely its obvious that Xt will not
display anything unless given an opportunity to. When you are executing
lisp code this opportunity does not exist except through programmer provision.
(1) hide the logic to do this in the c code; the lisp code should do
nothing
other than call (redisplay widget)
(2) make sure your event-cycling code processes *NO* events at all. this
includes non-user events. queue the events instead.
Agree.
in other words, dispatch-non-command-events must go, and i am
proposing a
Agree.
general function (redisplay OBJECT) to replace the existing ad-hoc
functions.
Not sure about the semantics of this. You are not redisplaying a widget
per-se you are simply doing a blocking next-event so that the Xt event loop
processes X events for things other than the XEmacs widget.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd