John Labenski <[EMAIL PROTECTED]> writes: > Look at the samples and you'll see that the wx.dll module is always > "required", but of course if you're running the wxLuaFreeze executable > it is already loaded so require "wx" does nothing. > > So, I don't think we need a new program lux.exe, since lua.exe does > exactly the above. > > Bottom line, wxLua and wxLuaFreeze are linked to the equivalent to > wx.dll and automatically load it into Lua. >
I agree it is just that wxLuaFreeze would have had to create a new program so I use the name lux. Yes what I like to have is Lua with wx.dll. I can compile wx.dll using the library specified by wxlua. It works for most programs, so it is probably the right libraries. When it fail it is because of an addressing error. I have try to narrow the problem down. binding fail when you open a folder. editor when you open a 3 th file. One of my own program fail when I try to open a file. The all seem to be memory related. I do not undestand LUA enough to be able to find the exact cause of the problem. It is usable but not really stable. Why using the name wx.dll. Wouldn't wxlua.dll more appropriate. One could imagine wxlua.dll being used with the regular wx.dll then the name would not conflict. Maybe I am confused. Andre ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ wxlua-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxlua-users
