On 6/4/06, Steve Kieu <[EMAIL PROTECTED]> wrote:
> I have repeatedly got the message when running the app in win98. With window
> 2000 and above, no problem. The app is like:
>
> at wxWidget app, at OnInit I start a wxLuaState and call run a file which
> is an command line argument.
> I have a wxThread class in c++ which just very simple thread to spawn
> another wxLuaState and run a file.lua . This class is accessible in lua
> script.
>
> Basically the first arg is the main window to open the GUI, and there is a
> menu to allow the thread to run another lua file in a different thread ; a
> server process. Everything works as expected in win2k . XP, but not win98.
> Even I do not have thread at all; just use wxLua and run the server script,
> which is a non GUI apps it gives the memory allocation error as well.
> However if I use the lua50.exe interprepter it works just fine so at the
> moment I have to wrap it using os.execute() call and use lua50.exe.
>
> Is there any GUI conflict if we use wxLua to run a Non GUI script in win98?
Not that I know of. It sounds like you know that you cannot call GUI
functions from a thread, so if you're not doing any GUI stuff in the
thread wxLuaState there shouldn't be a problem.
Can you debug this? It would be nice to fix, but I regularly use
multiple wxLuaStates without any problems. I just ran valgrind in
Linux and I get the usual X windows and GDK errors, which is a shame,
but nothing from wxLua.
Perhaps you could just make this simple test and see if it works?
wxApp::OnInit()
{
wxLuaState l1(true);
wxLuaState l2(true);
Regards,
John Labenski
_______________________________________________
Wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
