Hello Philipp,
You wrote:
Dan Williams wrote:[...] The problem with Cocoa is that OOo tries to do too many
things when an event is processed, including drawing and whatnot. Cocoa
really expects the app to simply update its internal state and then
re-draw itself when _needed_ (and asynchronously when it gets a drawRect:
message) rather thabn OOo's method of "get a mouse click and update
everything before returning". [...]
Huh ? When you press a VCL button it should be drawn clicked. How should aqua know that it has to send a "drawRect message" when a button got clicked ? Should vcl call some kind of invalidate method instead ?
Note: I have no clue on VCL or current GUI programming...
I have seen GUI code (GDI and Swing, if I recall correctly) that uses exactly this strategy: Drawing only ever occurs at the system's request. If the app wants to redraw something, it sends an invalidate call to system and later handles the corresponding redraw event. The advantage is a) uniform redraw handling, and b) the system may optimize such events. (E.g., don't redraw hidden things, or batch small redraws into a single event.) I thought this was common, but as my initial disclaimer says: I haven't done any GUI stuff in a while, and never with OOo.
However, I do find it rather strange that immediate redrawing could possibly cause application instability. I can't help but think that Cocoa must be at fault...
Well... just a thought.
Sincerely, Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
