wxlua-users Mailing List for wxLua

Hello,
I have compiled wxWidgets 3.0.1 on mac osx 10.9 (also widgets sample)
when compiling wxLuaModule:
Morundi:wxluabuild Morundi$ make wxLuaModule
Scanning dependencies of target wxLuaModule
[ 2%] Building CXX object 
modules/luamodule/CMakeFiles/wxLuaModule.dir/luamodule.cpp.o
In file included from 
/Users/Morundi/Downloads/wxLua-2.8.12.3-src/modules/luamodule/luamodule.cpp:21:
In file included from 
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/app.h:19:
In file included from 
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/event.h:16:
In file included from 
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/object.h:19:
In file included from 
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/memory.h:15:
In file included from 
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/string.h:46:
/Users/Morundi/Downloads/wxWidgets-3.0.1/include/wx/strvararg.h:30:18: fatal 
error: 'tr1/type_traits' file not found
 #include <tr1/type_traits>
Any thoughts?
Best
victor bombi 

Hi, John,
Thank you for your prompt reply.
>1. STC seems does not work for wxstc.wxSTC_LEX_CPP, I just changed the editor:SetLexer(wxstc.wxSTC_LEX_LUA) -> editor:SetLexer(wxstc.wxSTC_LEX_CPP) in the editor.wx.wlua, then run the editor.wx.wlua, the editor did not show what inputted. the editor worked well for other languages.
>Does the wxStEdit editor handle CPP highlighting correctly? In order to use the lexer you need to set a fair number of extra things. You can look at the code in editor.wx.lua for the Lua lexer and then look at the code in wxStEdit, though I will admit that it is quite complicated, to see what values to use for the cpp lexer.
-->Yes, the wxStEdit editor handles C/CPP highlighting correctly.
>2. The .exe file generated from wxLuaFreezed.exe cannot get run, even in cmd prompt, showed nothing.
>That is very strange, does wxLua.exe run correctly? They aren't very different at all.
--> wxLua.exe can run correctly, for example wxLua.exe can run editor.wx.wlua correctly.
>3. wxStEdit.exe and wxLuaEdit.exe take many time to start, about 15 seconds.
>Again, very strange, can you break into them with a debugger and see where they are during this long time?
--> I did not yet compile the debug files of wxStEdit.exe and wxLuaEdit.exe successfully, will continue to do it later.
>BTW: Do you have plan to release official binary release against wxWidgets 3.0, alpha or beta version, or even a work version is OK.
>I do, but as you might guess I have little time to work on it. I do plan to release one soonish.
 --> It is better to have an official binary, thanks.
Best Regards,
Ethan

On Fri, Sep 5, 2014 at 1:44 AM, Zhang, Ethan <Eth...@ar...> wrote:
>
>
> 1. STC seems does not work for wxstc.wxSTC_LEX_CPP, I just changed the
> editor:SetLexer(wxstc.wxSTC_LEX_LUA) ->
> editor:SetLexer(wxstc.wxSTC_LEX_CPP) in the editor.wx.wlua, then run the
> editor.wx.wlua, the editor did not show what inputted. the editor worked
> well for other languages.
>
>
Does the wxStEdit editor handle CPP highlighting correctly? In order to use
the lexer you need to set a fair number of extra things. You can look at
the code in editor.wx.lua for the Lua lexer and then look at the code in
wxStEdit, though I will admit that it is quite complicated, to see what
values to use for the cpp lexer.
2. The .exe file generated from wxLuaFreezed.exe cannot get run, even in
> cmd prompt, showed nothing.
>
>
>
That is very strange, does wxLua.exe run correctly? They aren't very
different at all.
 3. wxStEdit.exe and wxLuaEdit.exe take many time to start, about 15
> seconds.
>
>
Again, very strange, can you break into them with a debugger and see where
they are during this long time?
>
> BTW: Do you have plan to release official binary release against wxWidgets
> 3.0, alpha or beta version, or even a work version is OK.
>
>
I do, but as you might guess I have little time to work on it. I do plan to
release one soonish.
Regards,
 John

1. Please check the attached file, you can find that the first line in the editor does NOT have a line number in the line number margin, and the line number 1 is against the second line in the editor.
For the attached file mentioned here, please check the attached file <wxlua.png> in post : https://sourceforge.net/p/wxlua/mailman/message/32805144/

<I do not know why my last two post did not include the email content, post again.>
For the issue: STC seems does not work for wxstc.wxSTC_LEX_CPP, something found through my tests,
1. I found all the lexers (ASM, D, CPP, PERL, SQL) using LexerFactory in the line like LexerModule lmCPP(SCLEX_CPP, LexerCPP::LexerFactoryCPP, "cpp", cppWordLists) have the same issue.
2. Please check the attached file, you can find that the first line in the editor does NOT have a line number in the line number margin, and the line number 1 is against the second line in the editor.
3. When I input in the first line (the caret is in the first line), it seems the input chars are put in the second line.

Hi, ALL
I compiled the newest wxlua against wxWidgets 3.0.1 by visual studio 2013 and Cmak2.8.12.2 in Windows 7, the compiling was smooth.
I found some APPs issues for the my generated wxLua apps that I could not solve :
1. STC seems does not work for wxstc.wxSTC_LEX_CPP, I just changed the editor:SetLexer(wxstc.wxSTC_LEX_LUA) -> editor:SetLexer(wxstc.wxSTC_LEX_CPP) in the editor.wx.wlua, then run the editor.wx.wlua, the editor did not show what inputted. the editor worked well for other languages.
2. The .exe file generated from wxLuaFreezed.exe cannot get run, even in cmd prompt, showed nothing.
3. wxStEdit.exe and wxLuaEdit.exe take many time to start, about 15 seconds.
Maybe I missed something when compile wxlua, any comments are appreciated.
BTW: Do you have plan to release official binary release against wxWidgets 3.0, alpha or beta version, or even a work version is OK.
Thanks for you great works.
Thanks.

eth...@ar...