> Please read this for a better understanding, only
> wxEvtHander::AddPendingEvent() is safe from worker threads.
> http://docs.wxwidgets.org/trunk/overview_thread.html
Yes but this is for just one window messaging system. I would like to have
two independent
window messaging systems connected by lindas.
> Is there any difference between luaBitOp and the one wxLua provides?
The main reason I am using it is because I need it in secondary
lanes.(requiring wx for that would be
too much, besides it cant be done)
> If, and only if, all you want to get at is
> wxEvtHander::AddPendingEvent() perhaps Lindas will work for you?
> Again, I've never used LuaLanes, but sending Lindas to the main thread
> look like they were made for this purpose.
I use wxEVT_IDLE for receiving linda messages. I wanted to have two
completely independent
wx lua_States because it would make some tasks more easy.
> On the other hand, if you want to use wxWidgets structures like a
> wxImage, wxRect, etc, then consider that calling require("wx") takes a
> fair amount of time itself and it may not be worth creating the
> thread. Perhaps you can extract the work that needs to be done in
> pure-Lua structures.
I am not sure about what you mean. If you mean sending by lindas some kind
of description for the
work to be done by the wx lane and receiving the answer by lindas also, That
is what I am already
doing for creating windows from other lanes or using wxDir.
Best Regards
Victor Bombi
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
