On 5/17/10 7:30 AM, JeahJeah wrote:
The function calls SetAttribute, and then sends the message *after*
SetAttribute has returned. That message then goes into a message cue,
then the function returns. *Then* the message cue is processed
Do you go back out to the main event loop before processing the message
queue?
The only thing I'm not sure about is
SetAttribute() - that may well not be synchronous - though I can't
find any reference that contains that information.
SetAttribute is of course synchronous.
My real question is whether you go back out to the main event loop
between SetAttribute calls?
I understand that the UI is not thread safe, so you need to come back
to your UI thread to do UI updates, which are based on the back end
data. But do people tend to use JavaScript for the UI stuff, having
it load an interface to get access to the cpu intensive data (or
however that's done), or do they just have UI updates done directly
from the C++ code, completely cutting out the JavaScript engine?
Either one should work fine, really.
-Boris
_______________________________________________
dev-embedding mailing list
dev-embedding@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-embedding
