John Labenski wrote: > On 7/31/07, Scott Morgan <[EMAIL PROTECTED]> wrote: > >> Is there an easy method for seeing the console output, doesn't have to be >> via a console window, could be piped to a file or some other method. >> > > The print statements are trapped and wxLuaEvents are sent. Please see > apps/wxlua or apps/wxluaedit for how they're handled. Also > modules/wxlua/include/wxlstate.h and wxEVT_LUA_PRINT. > > You could even push your own "print" statement into lua, replacing the > one wxLua pushes into it. See modules.wxlua/src/wxlstate.cpp and > wxlua_printFunction(). >
Thanks, catching the wxEVT_LUA_PRINT and wxEVT_LUA_ERROR events works for me. Scott Morgan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ wxlua-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wxlua-users
