On 4/2/06, John Labenski <[EMAIL PROTECTED]> wrote:

> > > 1. My wxWidgets installation doesn't include wxSTC, and I had to
>
> You're using a RPM of wxWidgets or something else?

Something else :-)  I use a quite alternative distribution
(www.gobolinux.org), which has a very own packaging and compiling
system.

But no problem for me here. So far I'm not missing wxLuaEdit and friends.

> > > 3. I think that the 'include' directory in '#include
> > > <wxbind/include/wxbind.h>' is a bit cumbersome (I would prefer just
> > > something like '#include <wxbind/wxbind.h>', for example). I can live
> > > with this, though. :-)
> > this was not to pollute the compiler line with a lot of include paths
> > (we would need one for each subfolder in modules\ ...).
>
> Agreed, this may not be "standard", but all you have to include is the
> modules dir to get everything.

OK. Again, no problem for me. It was just a comment.

> > > 4. I had to link with 'wxlua_gtk2_wxluasocket-2.6', even though I
> > > don't use sockets. Otherwise, I get some linking errors concerning
> > > names that I would expect to find at 'wxlua_gtk2_wxluadebug-2.6'
> > > instead:
>
> The problem is from the wxluasetup.h having
> #define wxLUA_USE_wxLuaDebugServer 1
> which makes the wxlbind lib #include "wxluasocket/include/wxldserv.h"
>
> This is set by default so that the wxlua app program works. We had a
> discussion a while back about how to most simply allow multiple
> wxluasetup.h files to generate different wxbind libs for different
> programs, but found that "tricks" that would work for one compiler
> would fail for others.

Once more, that's not a real problem for me. I just found it strange...

> > > 5. Calling the Lua 'print()' function from a script run using
> > > 'wxLuaState::RunFile()' doesn't print anything at the terminal. Is
> > > this being redirected to somewhere?
> > these last two are meat for John, I think ;)
>
> It's being sent as an wxEVT_LUA_CONSOLE (see wxlstate.h) event from
> the function wxLua_lua_printFunction that's pushed on the lua_State,
> see
> bool wxLuaState::Create(wxEvtHandler *handler, wxWindowID id)
>
> I think you can just call
> wxLuaState::RegisterFunction(NULL, wxT("print"));
> to get back the original print function.
>
> or pushing the original function back will work
> lbaselib.c:static int luaB_print (lua_State *L)

Thanks! I'll try this.

LMB

Reply via email to