wxlua-users — wxLua list for users and developers

[wxlua-users] utf8 quick and dirty

[Andre A. <ar...@ki...>]

Hi,

	wxString str = wxString(luastr, wxConvUTF8);
	return str.Length()==0 ? wxString(luastr) : str;

This solution may look crazy but works surprisingly well.

We have no idea what kind of file has just been read.
Guessing is are only choice. If it is not UTF8 we are in trouble.

What happen to string.match(string,"%a") in either cases for example?

Andre

Re: [wxlua-users] CMake

[Andre A. <ar...@ki...>]

> 
> If you change the defines
> 
> 30 	#define WXLUA_USE_WXSTR_CONVUTF8 1
> 31 	#define WXLUA_USE_WXSTR_CONVCURRENT 0
> 
> to
> 
> 30 	#define WXLUA_USE_WXSTR_CONVUTF8 0
> 31 	#define WXLUA_USE_WXSTR_CONVCURRENT 1
> 

it does work

I think there a problem with the current version: 
é is character 130 should display as ‚ in the editor just a bit strange
this character set thing.
---------------- command line
echo {é} > xx

--- added the following code in editor.lua at line 891
    for w in string.gmatch(file_text, ".") do 
        print(w,string.byte(w), #w, '<<<')
    end
    for w in string.gmatch(file_text, ".") do 
        editor:AppendText('{'..string.byte(w)..'}'..'<'..w..'>')       
    end
    print(editor.Length, 'before append character')
    editor:AppendText('='..string.char(130)..'=')
    print(editor.Length, 'before append text', #file_text)
    editor:AppendText(file_text)  -- this does not append any text
    print(editor.Length, 'after append text', #file_text)

------------------------------------------------
command line:
E:\wxWidgets\wxLua\cmake\apps\wxlua\Debug\wxLua.exe editor.wx.lua xx
--------------------- output
[E:\wxWidgets\wxLua\samples]{   123     1       <<<
        130     1       <<<
}       125     1       <<<
        13      1       <<<

        10      1       <<<
30      before append character
30      before append text      5
30      after append text       5
----------------------------: file displayed in the editor
{123}<{>{125}<}>{13}<
>{10}<
>

Notice that character 130 cannot be added to the editor.
    editor:AppendText('='..string.char(130)..'=') does nothing

also if a file contains a character above 128 then it cannot be edited
    editor:AppendText(file_text) does nothing

André

Re: [wxlua-users] CMake

[John L. <jla...@gm...>]

On Fri, May 4, 2012 at 12:31 PM, Andre Arpin <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> OK there is a light at the end of the tunnel.
>
> using the following batch
>
> cd "E:\wxWidgets\wxLua\
> md cmake
> cd cmake
> cmake -trace -G "Visual Studio 9 2008" -DwxWidgets_ROOT_DIR:STRING=E:/wxWidgets
> -DwxWidgets_LIB_DIR:STRING=E:/wxWidgets/lib/vc_lib  E:/wxWidgets/wxLua
>
> and removing the incremental link in
>
> wxLua
> wxLuaCan
> wxLuaFreeze
>
> Compile successfully.

The incremental linker in 2008 seems to have a lot of problems. For
awhile I had to always build twice or more because the first time the
linker died. This wasn't the case here was it? In other words, when
you build the wxLua app one of the wxLua libs that the apps links to
had not built correctly. If you turn the incremental linker back on
and press build a few times do you see the linker (segfault or
whatever it was) error in the build output window?

I applied SP1 to VS2008 and it seemed to have made it a little better,
but the linker would still crash. Mysteriously, a half a year later
the linker now works great... I didn't change anything, unless some
Win7 security patch fixed something.

Here's one of the discussions about it, there are many many more...
http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/2a29f8ec-7c71-475d-a358-f2f1b0458f8b

> The current version does not seem to support unicode characters.
> ex:
> echo ["╪"] > xx

How is the file encoded, UTF-8 or UTF-16?

If I run this code in wxLua or wxLuaEdit I get a message box with that
character as the caption and the text so it works fine when pasted
into a program's source code.
wx.wxMessageBox("╪", "╪")

I made a change recently to use UTF8 for Lua, this means that if you
use Lua to open a file as a string, the string is treated as though
it's UTF8 when it is passed to wxWidgets, i.e. nothing is done if it's
just regular ASCII 0-127, but translated otherwise. However, if you
try to open a file that is UTF16 (what windows uses/ed it's confusing)
you'll have a problem.

There was a message thread last week where this was discussed, see rev 67.

http://wxlua.svn.sourceforge.net/viewvc/wxlua/trunk/wxLua/modules/wxlua/include/wxlstate.h?view=log

If you change the defines

30 	#define WXLUA_USE_WXSTR_CONVUTF8 1
31 	#define WXLUA_USE_WXSTR_CONVCURRENT 0

to

30 	#define WXLUA_USE_WXSTR_CONVUTF8 0
31 	#define WXLUA_USE_WXSTR_CONVCURRENT 1

does it fix it for you? Even it does, we can't revert since otherwise
the text in the GUI is broken, I think it has something to do with the
file encoding and reading it from disk.

Regards,
    John

Re: [wxlua-users] CMake

[Andre A. <ar...@ki...>]

John Labenski <jlabenski@...> writes:

OK there is a light at the end of the tunnel.

using the following batch

cd "E:\wxWidgets\wxLua\
md cmake
cd cmake
cmake -trace -G "Visual Studio 9 2008" -DwxWidgets_ROOT_DIR:STRING=E:/wxWidgets 
-DwxWidgets_LIB_DIR:STRING=E:/wxWidgets/lib/vc_lib  E:/wxWidgets/wxLua

and removing the incremental link in 

wxLua
wxLuaCan
wxLuaFreeze

projects.

Compile successfully. 

The current version does not seem to support unicode characters.
ex:
echo ["╪"] > xx

E:\wxWidgets\wxLua\cmake\apps\wxlua\Debug\wxLua.exe -o xx

the file is empty. 

I will have to wait until this is corrected to upgrade since my editor is 
written using wxlua.

Thanks.
Andre

Re: [wxlua-users] CMake

[Andre A. <ar...@ki...>]

-- COMMAND LINE
md wxWidgets
set WXWIN=wxWidgets
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat"
--- DEV STUDIO
open 
E:\wxWidgets\build\msw\wx_vc9.sln compile default
-- COMMAND LINE

"E:\Program Files (x86)\CMake 2.8\bin\cmake-gui.exe"
-- CMAKE

source: E:/wxWidgets/wxLua
dest: E:/wxWidgets/wxLua/cmake

*****************************************************************************
* BUILD TYPE:        Debug
* BUILD_SHARED_LIBS: OFF
*****************************************************************************
* System is 32-bit TRUE, is 64-bit FALSE
*****************************************************************************
* CMAKE_SOURCE_DIR = E:/wxWidgets/wxLua
* CMAKE_BINARY_DIR = E:/wxWidgets/wxLua/cmake
*****************************************************************************
 
* Using these wxWidgets components: 
stc;scintilla;xrc;xml;net;media;richtext;aui;html;adv;core;base
* 
* Found wxWidgets :
* - wxWidgets_VERSION      = 2.9.3 = 2.9.3
* - wxWidgets_COMPONENTS   = 
stc;scintilla;xrc;xml;net;media;richtext;aui;html;adv;core;base
* - wxWidgets_INCLUDE_DIRS = E:/wxWidgets/lib/vc_lib/mswud;E:/wxWidgets/include
* - wxWidgets_LIBRARY_DIRS = 
* - wxWidgets_LIBRARIES    = E:/wxWidgets/lib/vc_lib/wxmsw29ud_stc.lib  (REMOVE 
THE REST)
* - wxWidgets_CXX_FLAGS    = 
* - wxWidgets_DEFINITIONS  = UNICODE;_UNICODE
* - wxWidgets_DEFINITIONS_DEBUG = _DEBUG;__WXDEBUG__
* - wxWidgets_PORTNAME     = msw
* - wxWidgets_UNIVNAME     = 
* - wxWidgets_UNICODEFLAG  = u
* - wxWidgets_DEBUGFLAG    = d

--- DEV STUDIO
open: E:\wxWidgets\wxLua\cmake\apps\wxLuaApps.sln (compile default)

same  errors

Andre

Re: [wxlua-users] CMake

[John L. <jla...@gm...>]

On Thu, May 3, 2012 at 1:43 PM, Andre Arpin <ar...@ki...> wrote:
> run cmake
>
> point source and destination to
> E:\wxWidgets\wxLua

In CMake you can (and want to) choose a different directory for the
build output. You can then easily delete the whole build or any part
of it and rerun cmake to regenerate it.

> generate sln's
>
> compile
> E:\wxWidgets\wxLua\apps\wxLuaApps.sln in debug mode (default)

You should probably open the root dir wxLua.sln file. The other ones
may work... but that might not be guaranteed.

> wxlua and wxfreeze bot fail to link.
>
> first few errors follow
>
> 2>wxmsw29ud_stc.lib(stc.obj) : error LNK2019: unresolved external symbol
> _Scintilla_LinkLexers referenced in function "public: bool __thiscall
> wxStyledTextCtrl::Create(class wxWindow *,int,class wxPoint const &,class wxSize
> const &,long,class wxString const &)" (?
> Create@wxStyledTextCtrl@@QAE_NPAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@
> @@Z)

It looks like you're not linking to the scintilla lib somehow. I
explicitly add it if stc is in the wxWidgets_COMPONENTS which it
should be.

Please do a svn update and rerun cmake.

Did you modify the wxWidgets_COMPONENTS variable? Is scintilla and stc
in there? Try clearing the cache and rerunning or better yet, wipe the
whole build dir and start over.

Finally, just to be sure, right click on the wxlua app project in the
Visual Studio solution and select properties. Look for "Linking" and
view the command line. It will show you to libs that the app links to,
you'll see the rest of the wxWidgets libs as well as the wxLua libs.
Is scintilla and stc in there?

Regards,
    John

[wxlua-users] CMake

[Andre A. <ar...@ki...>]

The current version has been much improve. 
Like the change to the console.

CMake is still not a joy.

Create an new copy of the current version, wxWidgets-2.9.3 and wxLua

Set wxwin to point to the new version.
compile wx_vc9.sln in debug mode (default)
run cmake

point source and destination to 
E:\wxWidgets\wxLua

generate sln's

compile 
E:\wxWidgets\wxLua\apps\wxLuaApps.sln in debug mode (default)

wxlua and wxfreeze bot fail to link.

first few errors follow

2>wxmsw29ud_stc.lib(stc.obj) : error LNK2019: unresolved external symbol 
_Scintilla_LinkLexers referenced in function "public: bool __thiscall 
wxStyledTextCtrl::Create(class wxWindow *,int,class wxPoint const &,class wxSize 
const &,long,class wxString const &)" (?
Create@wxStyledTextCtrl@@QAE_NPAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@
@@Z)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2019: unresolved external symbol 
"protected: virtual __thiscall ScintillaBase::~ScintillaBase(void)" (??
1ScintillaBase@@MAE@XZ) referenced in function "public: virtual __thiscall 
ScintillaWX::~ScintillaWX(void)" (??1ScintillaWX@@UAE@XZ)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2019: unresolved external symbol 
"protected: __thiscall ScintillaBase::ScintillaBase(void)" (??
0ScintillaBase@@IAE@XZ) referenced in function "public: __thiscall 
ScintillaWX::ScintillaWX(class wxStyledTextCtrl *)" (??
0ScintillaWX@@QAE@PAVwxStyledTextCtrl@@@Z)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2001: unresolved external symbol 
"protected: virtual void __thiscall Editor::NotifyModifyAttempt(class Document 
*,void *)" (?NotifyModifyAttempt@Editor@@MAEXPAVDocument@@PAX@Z)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2001: unresolved external symbol 
"protected: virtual void __thiscall Editor::NotifySavePoint(class Document 
*,void *,bool)" (?NotifySavePoint@Editor@@MAEXPAVDocument@@PAX_N@Z)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2001: unresolved external symbol 
"protected: virtual void __thiscall Editor::NotifyModified(class Document 
*,class DocModification,void *)" (?
NotifyModified@Editor@@MAEXPAVDocument@@VDocModification@@PAX@Z)
4>wxmsw29ud_stc.lib(stc.obj) : error LNK2019: unresolved external symbol 
_Scintilla_LinkLexers referenced in function "public: bool __thiscall 
wxStyledTextCtrl::Create(class wxWindow *,int,class wxPoint const &,class wxSize 
const &,long,class wxString const &)" (?
Create@wxStyledTextCtrl@@QAE_NPAVwxWindow@@HABVwxPoint@@ABVwxSize@@JABVwxString@
@@Z)
2>wxmsw29ud_stc.lib(ScintillaWX.obj) : error LNK2001: unresolved external symbol 
"protected: virtual void __thiscall Editor::NotifyDeleted(class Document *,void 
*)" (?NotifyDeleted@Editor@@MAEXPAVDocument@@PAX@Z)

Andre

Re: [wxlua-users] Using wxWidgets 2.9.3

[John L. <jla...@gm...>]

On Wed, May 2, 2012 at 12:53 AM, John Labenski <jla...@gm...> wrote:
>> Change in wxlua_printFunction of file wxlstate.cpp
>>
>> The console did not display messages because
>> wxlState.GetEventHandler() == NULL
>> and !wxApp::IsMainLoopRunning() is also true
>>
>> commenting these tests makes the console display but is this right?
>
>> I am surprise that this works since the handler is used to invoke
>> wxLuaStandaloneApp::OnLua
>> so I am wondering if some changes have been done in wxWidgets event handler

I reworked this a little. wxLua can now print to the DOS console or
create a new DOS console as needed for stdout. I renamed some of the
switches for the wxLua program since I felt that they were poorly
named before.

I hope this works better now.

Regards,
     John

Re: [wxlua-users] Using wxWidgets 2.9.3

[John L. <jla...@gm...>]

On Wed, May 2, 2012 at 2:25 PM, Andre Arpin <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
>> You are using the CMake build?
>>
> no visual studio 2008
> had to make a few changes to the projects.

Try the CMake projects. The Visual Studio projects are generated from
Bakefile and they will only support 2.8 or 2.9.

I have yet to write docs for CMake, but it's as simple as downloading cmake

http://www.cmake.org/cmake/resources/software.html

ruunning it, set the source to the root dir of wxLua, set the build
dir to some new dir and press configure. You will probably have to set
the variables wxWidgets_ROOT_DIR and wxStEdit_ROOT_DIR and
reconfigure. When done, you have some very nice Visual Studio
projects.

> Using multilib with mod_luamodule_mono it compiles and half run with strange
> problems.
>
> The wxCalendarCtrl is not the one with version 2.9 or the one in the previous
> versions. Works mind you. Maybe one intended for unix. So the DLL and the exe
> do not run the same code 'wow'. I think I link all the same libs but will check
> this carefully.
>
> When terminating and sometime while running, the heap breaks. I think it is an
> allocation in one space and release in another. I have solved this problem once
> before but I could not trace it this time.

If any of these problems are shown in one of the samples let me know.
I have not seen any problems with 2.9.

Regards,
    John

Re: [wxlua-users] Multibyte characters not working with Unicode build

[strawman <str...@la...>]

On 02/05/2012 04:52, John Labenski wrote:
> Sorry about the delay, I committed a fix to SVN that I hope should
> work. We've gone through this before, but I think this time it's
> right. Now we always treat Lua as UTF8.
>
> Note that it only works with wxWidgets built in Unicode mode and has
> been tested in 2.8 and 2.9 in GTK and MSW.

Huge thanks for this; rebuilt against 2.8.12 and everything I've tried 
thus far works perfectly.

Re: [wxlua-users] Using wxWidgets 2.9.3

[Andre A. <ar...@ki...>]

John Labenski <jlabenski@...> writes:

> You are using the CMake build?
> 
no visual studio 2008
had to make a few changes to the projects.

> 
> I have not really tested the wx.dll built by CMake. I was trying to
> statically link the wxWidgets libs so we would only have the single
> dll.
> 

Using multilib with mod_luamodule_mono it compiles and half run with strange 
problems.

The wxCalendarCtrl is not the one with version 2.9 or the one in the previous 
versions. Works mind you. Maybe one intended for unix. So the DLL and the exe
do not run the same code 'wow'. I think I link all the same libs but will check 
this carefully.

When terminating and sometime while running, the heap breaks. I think it is an 
allocation in one space and release in another. I have solved this problem once 
before but I could not trace it this time. 

Keeping this as an easy problem to solve when I have time :)

Andre

Re: [wxlua-users] change to editor.lua

[Andre A. <ar...@ki...>]

John Labenski <jlabenski@...> writes:

 
> Is there any reason? It's true that wxSAVE is deprecated since 2.8 and
> this should be done, but I'm just wondering why this stands out to
> you.

wx.wxSAVE is nul when I run.

Andre

Re: [wxlua-users] Using wxWidgets 2.9.3

[John L. <jla...@gm...>]

On Thu, Apr 26, 2012 at 8:54 AM, Andre Arpin <ar...@ki...> wrote:
> I am using visual studio 2008
>
> Overall the port went well.

You are using the CMake build?

> wx.dll does not work quite right any more. I will look at it later.

I have not really tested the wx.dll built by CMake. I was trying to
statically link the wxWidgets libs so we would only have the single
dll.

> Change in wxlua_printFunction of file wxlstate.cpp
>
> The console did not display messages because
> wxlState.GetEventHandler() == NULL
> and !wxApp::IsMainLoopRunning() is also true
>
> commenting these tests makes the console display but is this right?

> I am surprise that this works since the handler is used to invoke
> wxLuaStandaloneApp::OnLua
> so I am wondering if some changes have been done in wxWidgets event handler

Hummm, I thought it worked, but maybe it didn't.

Regards,
     John

Re: [wxlua-users] Need advise on closing a script's top level window

[John L. <jla...@gm...>]

On Tue, May 1, 2012 at 8:52 PM, Steve Murphree <sm...@sm...> wrote:

> I've managed to integrate wxLua into a DLL that my application uses.  The
> DLL is purely there to provide script capabilities.  When a user wants to
> run a script, the action ends up in the DLL which uses the following code:

I have not tried this myself.

Please see the link below if you haven't already. The README claims
the sample does exactly what you want.

http://svn.wxwidgets.org/viewvc/wx/wxWidgets/trunk/samples/dll/

> This, at first, seems to work fine.  The script will execute and show it's
> GUI window.  Take minimal.wx.lua, for example.  But when you are done
> playing with the script, you can't close its top level window!  I seem to

Other people have had similar problems, but I don't think the solution
suggested here (a hidden frame) is the right one, see the sample
above.
http://trac.wxwidgets.org/ticket/11496

Regards,
    John

Re: [wxlua-users] Multibyte characters not working with Unicode build

[John L. <jla...@gm...>]

On Fri, Apr 20, 2012 at 1:49 AM, strawman <str...@la...> wrote:
>> What is the text that you are trying to use?
>
> require"wx"
> a = wx.wxTextEntryDialog(wx.wxFrame(), "test тест テスト")
> a:ShowModal()
> print(a:GetValue())
>
> The caption appears as "test" and then garbage characters, and if I
> paste "test тест テスト" into the dialog, GetValue returns nil under 2.8
> and an empty string under 2.9.  "test" on its own works as expected.

Sorry about the delay, I committed a fix to SVN that I hope should
work. We've gone through this before, but I think this time it's
right. Now we always treat Lua as UTF8.

Note that it only works with wxWidgets built in Unicode mode and has
been tested in 2.8 and 2.9 in GTK and MSW.

Regards,
     John

Re: [wxlua-users] change to editor.lua

[John L. <jla...@gm...>]

On Tue, May 1, 2012 at 4:32 PM, Andre Arpin <ar...@ki...> wrote:
> Please change
> at line 980 wx.wxSAVE to wx.wxFD_SAVE

Is there any reason? It's true that wxSAVE is deprecated since 2.8 and
this should be done, but I'm just wondering why this stands out to
you.

I think that very soon I will remove all wxWidgets < 2.8 stuff.

Regards,
    John

[wxlua-users] Need advise on closing a script's top level window

[Steve M. <sm...@sm...>]

Hello, 

 

I've managed to integrate wxLua into a DLL that my application uses.  The
DLL is purely there to provide script capabilities.  When a user wants to
run a script, the action ends up in the DLL which uses the following code:

 

 

// luaControl constructor.  luaControl is derived from wxWindow.

luaControl::luaControl(wxWindow *parent, MINSTANCE mInst, wxMachPluginLuaApp
*pluginApp, HMCPLUG id)

{

    wxWindow::Create(parent, ID_LUAWIN);

    WXLUA_IMPLEMENT_BIND_ALL

 

    // OnInit() already called

    // wxLuaState::sm_wxAppMainLoop_will_run = false;

      

      m_wxlState = wxLuaState(this, wxID_ANY);

}

 

int luaControl::ExecuteScript(wxString &filename)

{

    if (!m_wxlState.Ok()) {

        return(-1);

    }

    int rc = m_wxlState.RunFile(filename);

    if (rc != 0) {

        wxString emsg = wxlua_LUA_ERR_msg(rc);

        mcSetLastError(this->m_cid, (const char *)emsg.char_str());

        return(rc);

    }

    while (m_wxlState.IsRunning())

      ;

    return(rc);

}

 

This, at first, seems to work fine.  The script will execute and show it's
GUI window.  Take minimal.wx.lua, for example.  But when you are done
playing with the script, you can't close its top level window!  I seem to
have painted myself into a corner.  I think it has something to do with the
fact that the application as a whole has multiple wxApp classes.  One for
the main GUI executable, one for a DLL that is the core of the application,
and one for the scripting DLL.  This is on Windows, for the moment, and
wxWidgets is compiled into static libs which all modules link to.  

 

It feels like it is hooking the GUI executable's main loop instead of the
script DLLs main loop.  Is there any way to force wxLua to use a particular
wxApp instance?  Or am I barking up the wrong tree?

 

Thanks, 

Steve

 

[wxlua-users] change to editor.lua

[Andre A. <ar...@ki...>]

Please change
at line 980 wx.wxSAVE to wx.wxFD_SAVE

Thank you 
Andre

[wxlua-users] Using wxWidgets 2.9.3

[Andre A. <ar...@ki...>]

I am using visual studio 2008

Overall the port went well.

wx.dll does not work quite right any more. I will look at it later.


Change in wxlua_printFunction of file wxlstate.cpp

The console did not display messages because 
wxlState.GetEventHandler() == NULL 
and !wxApp::IsMainLoopRunning() is also true

commenting these tests makes the console display but is this right?

    if (!wxlState.Ok() /* || (wxlState.GetEventHandler() == NULL) ||  
!wxApp::IsMainLoopRunning()*/)

I am surprise that this works since the handler is used to invoke 
wxLuaStandaloneApp::OnLua
so I am wondering if some changes have been done in wxWidgets event handler

Thanks for the excellent work.

Andre

Re: [wxlua-users] Multibyte characters not working with Unicode build

[strawman <str...@la...>]

On 19/04/2012 05:27, John Labenski wrote:
> What version of wxWidgets are you using?  2.8 or 2.9

This was with 2.8.12; I just built wxLua against 2.9.3 and tried again, 
and it's now returning an empty string instead of nil.  I'm building 
with TDM-GCC, if it makes any difference.

> What is the text that you are trying to use?

require"wx"
a = wx.wxTextEntryDialog(wx.wxFrame(), "test тест テスト")
a:ShowModal()
print(a:GetValue())

The caption appears as "test" and then garbage characters, and if I 
paste "test тест テスト" into the dialog, GetValue returns nil under 2.8 
and an empty string under 2.9.  "test" on its own works as expected.

Re: [wxlua-users] Multibyte characters not working with Unicode build

[John L. <jla...@gm...>]

On Tue, Apr 17, 2012 at 11:52 PM, strawman <str...@la...> wrote:
> With a Unicode build of wxMSW and wxLua, trying to access any string
> containing multibyte characters (e.g. with wxTextCtrl::GetValue) returns
> nil.  The same issue is present in the wxLua editor; if any multibyte
> characters are in the buffer when a script is saved, the saved file is 0
> bytes in length, and running the script silently fails.
>
> Is this a bug (or an issue with my build), or is there some specific way
> to correctly handle multibyte characters?

What version of wxWidgets are you using?  2.8 or 2.9

I have not done much with multibyte chars other than try to convert
them to and from Lua's 8 bit strings. There was some work done on this
years ago and it should still work, but of course the limitation is
that Lua itself is not multibyte. wxWidgets 2.9 uses UTF8 for it's
strings while 2.8 used UTF16, if I remember correctly, for the MSW
Unicode builds.

What is the text that you are trying to use?

Regards,
    John

[wxlua-users] Multibyte characters not working with Unicode build

[strawman <str...@la...>]

With a Unicode build of wxMSW and wxLua, trying to access any string 
containing multibyte characters (e.g. with wxTextCtrl::GetValue) returns 
nil.  The same issue is present in the wxLua editor; if any multibyte 
characters are in the buffer when a script is saved, the saved file is 0 
bytes in length, and running the script silently fails.

Is this a bug (or an issue with my build), or is there some specific way 
to correctly handle multibyte characters?

Re: [wxlua-users] 2.9.3 with cmake ubuntu

[John L. <jla...@gm...>]

On Sun, Apr 15, 2012 at 9:53 AM, klaas.holwerda <ng...@kl...> wrote:
>>> [ 19%] Building CXX object modules/luamodule/CMakeFiles/wxLuaModule.dir/__/wxbind/src/wxcore_gdi.cpp.o
>>> /home/klaas/soft/wxlua/trunk/wxLua/modules/wxbind/src/wxcore_gdi.cpp: In function ‘int
>>> wxLua_wxIconBundle_AddIcon(lua_State*)’:
>>> /home/klaas/soft/wxlua/trunk/wxLua/modules/wxbind/src/wxcore_gdi.cpp:7356:29: warning: ‘void
>>> wxIconBundle::AddIcon(const wxString&, long int)’ is deprecated (declared at
>>> /usr/local/include/wx-2.9/wx/iconbndl.h:91) [-Wdeprecated-declarations]
>>> /home/klaas/soft/wxlua/trunk/wxLua/modules/wxbind/src/wxcore_gdi.cpp: In function ‘int
>>> wxLua_wxIconBundle_GetIcon1(lua_State*)’:
>>> /home/klaas/soft/wxlua/trunk/wxLua/modules/wxbind/src/wxcore_gdi.cpp:7374:63: error: taking address
>>> of temporary [-fpermissive]
>> This line?
>> const wxIcon* returns = (const wxIcon*)&self->GetIcon(size);
>>
>> I'm not sure how to convince GCC that this is a not a temporary
>> variable since it isn't.
> Why not?? A wxIcon is returned from GetIcon(size), and that is a temporary i think.
> But i am not good at such thinks.

The GetIcon() function returns a reference to an element of an array
member of the wxIconBundle. This means that the reference is valid so
long as the array element exists which is reasonably non-temporary.

I see now that internally, that function actually uses a wxIcon*
pointer to that element then dereferences it to return it with a
comment saying that it is a workaround for the Borland compiler. This
is probably why GCC is getting confused.

>> Could you try this:
>> const wxIcon* returns = reinterpret_cast<const wxIcon*>(&self->GetIcon(size));
> Did not help.
> But the next does ( it stores/copies the return wxIcon first ):
>
>     static wxIcon icon = self->GetIcon(size);
>     const wxIcon* returns = (const wxIcon*) &icon;

If this function is called twice, the first call's icon gets changed
by the second call.

> or:
>     wxIcon icon = self->GetIcon(size);
>     const wxIcon* returns = (const wxIcon*) &icon;

This is definitely no good as the "icon" variable is definitely temporary.

>> Can you compile the wxWidgets media control sample without error?
> If you mean the MediaPlayer example, yes, and it works. I do not see another example, so i think
> that is the only one.

Yes, that one.

> With all the advice, i now get until here (see end this mail). The library -lgstinterfaces-0.10 is
> missing to link too? If i add it by hand as -lgstinterfaces-0.10 down here, on the commandline, it
> links.
> In aps/CMakeLists change this, also works:
>
>     LINK_LIBRARIES
>         #wxLuaBindLib
>         ${wxLuaBind_ALL_LIBS}
>         wxLuaSocketLib
>         wxLuaDebugLib
>         wxLuaLib
>         LuaLib
>         gstinterfaces-0.10
>         ${wxWidgets_LIBRARIES}
>
> With that i can compile completely! :-)

That's good, for now.

wxLua doesn't use anything in gstreamer besides what wxWidgets uses,
so I'm guessing that Ubuntu broke up the gstreamer library (or somehow
compiled it differently) so that wxWidgets itself should really link
to gstinterfaces as well. Maybe the sample doesn't call the
function(s) that use anything from it so that why you don't get the
linker error for gstinterfaces.

I'll see about installing the newest Ubuntu into a virtual machine.

> But -Wno-deprecated did not make much a difference for all the warnings??

I'll look into this.

Regards,
    John

Re: [wxlua-users] Deriving from wxDataObjectSimple

[strawman <str...@la...>]

On 13/04/2012 23:06, John Labenski wrote:
> ps. Do a SVN update. I had the signature wrong on
> wxLuaDataObjectSimple::SetData() so it would never be called by
> wxWidgets.

Looks like this was the issue; thanks again for the help, it works 
perfectly now.

Re: [wxlua-users] Latest Windows build created in 2009

[jimmy c. <jim...@ya...>]

Thanks for the response.
Regards,
Jimmy


________________________________
 From: John Labenski <jla...@gm...>
To: jimmy coyne <jim...@ya...>; wxl...@li... 
Sent: Saturday, 14 April 2012, 2:41
Subject: Re: [wxlua-users] Latest Windows build created in 2009
 
On Fri, Apr 13, 2012 at 5:16 PM, jimmy coyne <jim...@ya...> wrote:
> Hi,
> I just started to learn Lua and searching for a GUI library, wxLua looks
> like a popular and well respected choice. My first concern (well only one at
> this stage :-) ) was the date of the last build on windows, which looks like
> it was  2009. Is that really the date of the last release or am I missing
> something?

I have been very bad about making releases. There are a few new
features in the development version (subversion), but you have to
compile it yourself. Most of the changes in wxWidgets 2.8 have been
bug fixes for things that probably wouldn't affect wxLua users unless
they wrote very complicated programs. As a normal user you would not
find much, if any, difference, however I do plan to make a release
soonish. As soon as I get the new build files working more smoothly.

Regards,
     John

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
wxlua-users mailing list
wxl...@li...
https://lists.sourceforge.net/lists/listinfo/wxlua-users