On Mon, 31 Jan 2005, Stephan Schaefer wrote:
Having done native widgets twice over (GTK, and then Aqua for NeoOffice/C) I spent the majority of my time with the Aqua stuff being frustrated with tying together the event model. There needed to be a couple threads: 1) The cocoa event loop for the NSApplication object, 2) The OOo event thread, and 3) The actual OOo drawing/everything-else thread. It seemed that even on a dual-processor machine, events took a while to get from Cocoa to OOo. 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". Or something like that. I kept running into really really long call-chains, deadlocks, and crashes resulting from this issue.
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 ?
Just my 2 cents, pl
--
Never be afraid to try something new. Remember:
amateurs built the ark; professionals built the Titanic.
-- Autor unbekannt--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
