From: Zhang, E. <Eth...@AR...> - 2014-09-09 07:38:00
|
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 |