wxlua-users Mailing List for wxLua

On Fri, 15 Oct 2010 16:43:50 -0400, John Labenski <jla...@gm...>
wrote:


...
> >> Try putting some print statements for the wxBitmapCombobox to prove
> >> that it's really valid and works.
> >>
> >> print(control:GetSize():GetWidth())
> >> print(control:GetName())
> >
> > Don't work:
> >
> > $ lua JY_controls.wx.lua
> > lua: JY_controls.wx.lua:515: wxLua: Unable to call an unknown method
> > 'GetSize' on a 'wxBitmapComboBox' type. stack traceback:
> >        [C]: ?
> >        JY_controls.wx.lua:515: in function 'CreateControlsWindow'
> >        JY_controls.wx.lua:1085: in function 'main'
> >        JY_controls.wx.lua:1124: in main chunk
> >        [C]: ?
> 
> Interesting? I'd stick with the CVS version in case there was some bug
> in the bindings back then, but I don't think that's the case. In any
> case since you're building it, use the CVS version, that's what I use.

Ok, after greping a bit I used the configure option
--disable-precomp-headers that solved the .pch PB... to discover another:
it don't work anymore with wxstedit; once unlinked, compilation was ok.

and now it's working good :)

Thanks for your help John and regards,
JY
-- 
Ignorance is the Mother of Devotion.
		-- Robert Burton

On Fri, Oct 15, 2010 at 4:41 PM, AndreArpin <ar...@ki...> wrote:
> Hi,
>
> Compiling wx.dll is much easier then it used to be but a couple of minor
> changes would help.
>
> using: msvc8\modules.sln [Debug Unicode DLL MultiLib]
>
> mod_luamodule_mono
>
> only enable
>   mod_lua
>   mod_luamodule_mono
>
> in the mod_luamodule_mono project properties
>
> remove WXUSINGDLL from the Preprocessor Definitions

Isn't this necessary to use the wxWidgets DLL?

> change (WXWIN)\lib\vc_dll to $(WXWIN)\lib\vc_lib in the
> linker Additionnal Library Directories

But wx.dll is a DLL.

> If this is done then you can install wxwidgets
> copy the setup.h file from msw to wx
> create both wxlua.exe etc and wx.dll without any changes.

I don't know what you mean about "install wxwidgets" and copy the
setup.h file. I have not tried wxWidgets 2.8.11 in MSW yet, but if you
checkout the SVN you have to copy wx/msw/setup0.h to wx/msw/setup.h.
Typically the wxWidgets.zip files for MSW has this done for you
already, but I remember that at least once this wasn't done and people
complained (maybe it was 2.8.11?).

> PS:
> wxWidgets-2.8.11.zip works without problem
> The current version of scintilla seems to work without problems after some
> modifications to stc.sln.

It works without problems in Linux, I haven't made a distribution,
because I don't think there are too many changes, but of course I
should.

Regards,
    John

On Fri, Oct 15, 2010 at 4:02 PM, Jean-Yves F. Barbier <12...@gm...> wrote:
> On Fri, 15 Oct 2010 13:14:04 -0400, John Labenski <jla...@gm...>
>
> # make
> (cd ./modules/ && make )
> make[1]: entrant dans le répertoire
> « /usr/src/LOCAL/LUA/wxLua_CVS_NCP/modules
> » /usr/src/LOCAL/LUA/wxLua/bk-deps g++ -c -o wxbindadv_dll_wxadv_bind.o
> -I.pch/wxprec_wxbindadv_dll -I../modules/wxbind/setup -I../modules -I./..
> -I/usr/include/lua5.1 -DWXMAKINGDLL_WXBINDADV -fPIC -DPIC
> -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8
> -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread
> -DwxLUA_USEBINDING_WXMEDIA=0 -I/usr/src/LOCAL/LUA/wxstedit/include
> -O2 ./wxbind/src/wxadv_bind.cpp
> ./wxbind/src/wxadv_bind.cpp:30:23:
> erreur: .pch/wxprec_wxbindadv_dll/wx/wxprec.h : Aucun fichier ou dossier de
> ce type
> make[1]: *** [wxbindadv_dll_wxadv_bind.o] Erreur 1
> make[1]: quittant le répertoire « /usr/src/LOCAL/LUA/wxLua_CVS_NCP/modules
> »
> make: *** [modules] Erreur 2

wx/wxprec.h should be from wxWidgets/include/wx/wxprec.h not
.pch/wxprec_wxbindadv_dll/wx/wxprec.h, which I'm sure shouldn't exist.
Is wxprec.h not in /usr/include/wx-2.8?

> Yep for almost all, except I have 2 msgs for both wxSashLayoutWindow &
> wxSashWindow: xxxxxx must have a top level windows as parent.
>
> I don't remember if it was the case yesterday, but I clearly remember
> that first time I tested it I had these widgets working.

This is probably ok, I don't get this message for some reason, but the
controls.wx.lua sample exercises nearly every control in wxWidgets
that wxLua wraps and stuffs them into a wxScrolledWindow just for demo
purposes. This is something that nobody would do in practice.

You can also use the Makefiles to build wxLua. For example, go into
wxLua/apps/wxlua/src and type $make. This will build wxLua using the
Lua in wxLua/modules/lua and put the libs into the dir that $wx-config
--exec-prefix returns. You can override where the libs are built into
by using this.

$make WXLUA_LIBDIR=/path/to/where/you/want/the/libs/put

If you poke though the Makefiles and wxLua/build/Makefile_wx-config.in
and Makefile_wx-config_targets.in you can override all of the
variables on the command line as above.

>> Try putting some print statements for the wxBitmapCombobox to prove
>> that it's really valid and works.
>>
>> print(control:GetSize():GetWidth())
>> print(control:GetName())
>
> Don't work:
>
> $ lua JY_controls.wx.lua
> lua: JY_controls.wx.lua:515: wxLua: Unable to call an unknown method
> 'GetSize' on a 'wxBitmapComboBox' type. stack traceback:
>        [C]: ?
>        JY_controls.wx.lua:515: in function 'CreateControlsWindow'
>        JY_controls.wx.lua:1085: in function 'main'
>        JY_controls.wx.lua:1124: in main chunk
>        [C]: ?

Interesting? I'd stick with the CVS version in case there was some bug
in the bindings back then, but I don't think that's the case. In any
case since you're building it, use the CVS version, that's what I use.

Regards,
    John

Hi,

Compiling wx.dll is much easier then it used to be but a couple of minor
changes would help.

using: msvc8\modules.sln [Debug Unicode DLL MultiLib]

mod_luamodule_mono

only enable 
   mod_lua 
   mod_luamodule_mono

in the mod_luamodule_mono project properties

remove WXUSINGDLL from the Preprocessor Definitions

change (WXWIN)\lib\vc_dll to $(WXWIN)\lib\vc_lib in the
linker Additionnal Library Directories 

If this is done then you can install wxwidgets 
copy the setup.h file from msw to wx 
create both wxlua.exe etc and wx.dll without any changes.

If you choose the "Debug Unicode" configuration.

I realize that this is a restricted configuration and that the changes would 
have to be propagated to other configurations for the changes to be generalized.

Andre

PS: 
wxWidgets-2.8.11.zip works without problem
The current version of scintilla seems to work without problems after some 
modifications to stc.sln.

On Fri, 15 Oct 2010 13:14:04 -0400, John Labenski <jla...@gm...>
wrote:


...
> You could try the CVS version, though there has only been minor fixes
> which I don't think would affect this.
> 
> http://sourceforge.net/projects/wxlua/develop
> 
> cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxlua
> co -P wxLua

Unfortunately it won't compile, this is a 2nd attempt to compile (no
configure error):

# make
(cd ./modules/ && make )
make[1]: entrant dans le répertoire
« /usr/src/LOCAL/LUA/wxLua_CVS_NCP/modules
» /usr/src/LOCAL/LUA/wxLua/bk-deps g++ -c -o wxbindadv_dll_wxadv_bind.o
-I.pch/wxprec_wxbindadv_dll -I../modules/wxbind/setup -I../modules -I./..
-I/usr/include/lua5.1 -DWXMAKINGDLL_WXBINDADV -fPIC -DPIC
-I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread
-DwxLUA_USEBINDING_WXMEDIA=0 -I/usr/src/LOCAL/LUA/wxstedit/include
-O2 ./wxbind/src/wxadv_bind.cpp 
./wxbind/src/wxadv_bind.cpp:30:23:
erreur: .pch/wxprec_wxbindadv_dll/wx/wxprec.h : Aucun fichier ou dossier de
ce type 
make[1]: *** [wxbindadv_dll_wxadv_bind.o] Erreur 1 
make[1]: quittant le répertoire « /usr/src/LOCAL/LUA/wxLua_CVS_NCP/modules
» 
make: *** [modules] Erreur 2
 
> > In fact I compiled an LUA 5.1 some months ago, but I destroyed it when
> > sid was updated.
> > As compilation was put into /usr/local I erased all LUA related
> > files/dirs before sid packages installation.
> 
> So long as there's no confusion for the linker it should be ok. The
> important thing is that the headers you compile with are for the libs
> you're linking to. If you don't add the wxBitmapCombobox to the sizer
> can you use it, can you select items and do the events from it show up
> in the log window below?

Yep for almost all, except I have 2 msgs for both wxSashLayoutWindow &
wxSashWindow: xxxxxx must have a top level windows as parent.

I don't remember if it was the case yesterday, but I clearly remember
that first time I tested it I had these widgets working.
 
> Try putting some print statements for the wxBitmapCombobox to prove
> that it's really valid and works.
> 
> print(control:GetSize():GetWidth())
> print(control:GetName())

Don't work:

$ lua JY_controls.wx.lua
lua: JY_controls.wx.lua:515: wxLua: Unable to call an unknown method
'GetSize' on a 'wxBitmapComboBox' type. stack traceback:
	[C]: ?
	JY_controls.wx.lua:515: in function 'CreateControlsWindow'
	JY_controls.wx.lua:1085: in function 'main'
	JY_controls.wx.lua:1124: in main chunk
	[C]: ?

...
> > I attached (permitted?) the ldd result: everything looks fine.
> 
> It does look ok. Does the sample run in wxLuaEdit or wxLuaFreeze?

No, I run it from "lua JY_controls.wx.lua" at command line.
 
...

In fact I first thought I found the reason: I had a 2.8.7 version
into /usr/lib (may be this day my spare neurone was absent.)

But after a whole system cleaning plus uninstall/reinstall LUA 5.1 + some
libs (all packages) and a new make install of 2.8.10 (tarball), I still
have the same issue.
I really don't understand where it can come from!
(I also made an "apt-get install --reinstall" for all libwx packages,
before compilation, to make sure I won't miss any file, just in case.)

JY
-- 
The big cities of America are becoming Third World countries.
		-- Nora Ephron

On Sun, Sep 12, 2010 at 5:30 AM, Chunlin Zhang <zha...@gm...> wrote:
> Now I want to use wxTextCtrl:GetInsertionPoint() to get input point,but I found
> that GetInsertionPoint is using character to count,not byte.So the result of
> GetInsertionPoint() is not suitable to use in wxTextCtrl string ,because
> wxTextCtrl string is lua string.
>
> For example,the system default encoding is UTF-8,when wxTextCtrl string have
> some muti-bytes character for example chinese characters,the GetInsertionPoint()
> result can not use in lua string.
>
> How can I do with this situation?

I don't really know or even if wxString handles it appropriately? If
you don't expect the text to be too long you could loop through
wxTextCtrl::GetText() and count chars. Depending on what you want,
would wxTextCtrl::GetRange() help figure out the position?

http://en.wikipedia.org/wiki/UTF-8

Regards,
    John

On Fri, Oct 15, 2010 at 10:33 AM, Jean-Yves F. Barbier <12...@gm...> wrote:
> ...
>> I have no problem with this sample in MSW and Mandriva Linux. What
>> wxLua are you using, did you compile it yourself?
>
> I use tarball wxLua-2.8.10.0-src.tar.gz from sourceforge.net

You could try the CVS version, though there has only been minor fixes
which I don't think would affect this.

http://sourceforge.net/projects/wxlua/develop

cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxlua
co -P wxLua

> In fact I compiled an LUA 5.1 some months ago, but I destroyed it when sid
> was updated.
> As compilation was put into /usr/local I erased all LUA related files/dirs
> before sid packages installation.

So long as there's no confusion for the linker it should be ok. The
important thing is that the headers you compile with are for the libs
you're linking to. If you don't add the wxBitmapCombobox to the sizer
can you use it, can you select items and do the events from it show up
in the log window below?

Try putting some print statements for the wxBitmapCombobox to prove
that it's really valid and works.

print(control:GetSize():GetWidth())
print(control:GetName())

> I also installed a bunch of rocks, acknowledging when it asked to replace
> some files/rocks with newer ones (may be I should stick to a basic install
> and only use rocks?)

wxLua shouldn't care about any of that, unless one of them overwrites
the Lua executable or library.

> I attached (permitted?) the ldd result: everything looks fine.

It does look ok. Does the sample run in wxLuaEdit or wxLuaFreeze?

> If you don't have any other tracking advice, I'll consider to uninstall LUA
> and all its components this WE; chase all possible files and erase them,
> then restart from scratch (which will be a PITA because I also use many
> addons, such as MAPM, classlib, etc and some are long to compile.)
>
> I'll test w/ a genuine install, and if it works, restart to install
> libs & rocks and retest between each install to see what going on.
>
> Do you advise restarting with an LUA tarball or can I stick to the packages?
> (I mean LUA *AND* libs [some might be overwritten by some rocks])

I would at least recompile wxLua and then try it. You don't even have
to run make install until you're sure it all works.

Regards,
    John

On Fri, 15 Oct 2010 09:51:50 -0400, John Labenski <jla...@gm...>
wrote:


...
> I have no problem with this sample in MSW and Mandriva Linux. What
> wxLua are you using, did you compile it yourself?

I use tarball wxLua-2.8.10.0-src.tar.gz from sourceforge.net

>  What wxWidgets version and from where? 

wx2.8 v. 2.8.10.1-3 sid package

> What Lua version and are you sure you're
> compiling wxLua using the lua-devel package from Debian sid or are you
> compiling wxLua with it's own Lua (in modules/lua) and then running it
> with the system installed Lua?

LUA v. 5.1.4-5 sid package
The compilation configure returned it is using the system LUA, not the
embedded one.

> The fact that the wxBitmapComboBox is created and does show if not
> added to the sizer, but crashes when added to the sizer makes me think
> that you have mismatched libraries.

In fact I compiled an LUA 5.1 some months ago, but I destroyed it when sid
was updated.
As compilation was put into /usr/local I erased all LUA related files/dirs
before sid packages installation.

I also installed a bunch of rocks, acknowledging when it asked to replace
some files/rocks with newer ones (may be I should stick to a basic install
and only use rocks?)

The only modif I made to the regular compilation was:
./configure --with-wxstedit-prefix=/usr/src/LOCAL/WXLUA/wxstedit

> You can get very strange and
> nearly undebuggable errors in these cases. Try running ldd on the
> wxLua libs to make sure that the libs it links to are appropriate,
> especially liblua.so being in /lib/, /usr/lib/, or somewhere like that
> to confirm that you're using the system Lua.

I attached (permitted?) the ldd result: everything looks fine.

If you don't have any other tracking advice, I'll consider to uninstall LUA
and all its components this WE; chase all possible files and erase them,
then restart from scratch (which will be a PITA because I also use many
addons, such as MAPM, classlib, etc and some are long to compile.)

I'll test w/ a genuine install, and if it works, restart to install
libs & rocks and retest between each install to see what going on.

Do you advise restarting with an LUA tarball or can I stick to the packages?
(I mean LUA *AND* libs [some might be overwritten by some rocks])

> Hope this helps,
>      John

Thanxs
JY
-- 
There is a fly on your nose.

On Thu, Oct 14, 2010 at 11:13 PM, Jean-Yves F. Barbier <12...@gm...> wrote:
> Hi list,
>
> There's something I don't understand in the example "controls.wx.lua",
> the insertion of the "wx.wxBitmapComboBox" crashes the program with this
> output:
>
> $ lua JY_controls.wx.lua
> lua: JY_controls.wx.lua:435: wxLua: Function call has invalid argument 2 on
> method 03.
>
> Function called: 'Add(wxFlexGridSizer, wxBitmapComboBox, number, number, number)'
> 01. wxSizer::Add(wxSizer(self), number [, number, number, number, number, wxObject])
> 02. wxSizer::Add(wxSizer(self) [, wxSizer, number, number, number, wxObject])
> 03. wxSizer::Add(wxSizer(self) [, wxWindow, number, number, number, wxObject])
> stack traceback: [C]: in function 'Add'
>        JY_controls.wx.lua:435: in function 'AddControl'
>        JY_controls.wx.lua:514: in function 'CreateControlsWindow'
>        JY_controls.wx.lua:1081: in function 'main'
>        JY_controls.wx.lua:1120: in main chunk
>        [C]: ?
>
> The file's almost genuine (I just added some print lines to try to
> understand what's wrong) and it works when I comment its last line:
> "AddControl("wxBitmapComboBox", control)", making this control obviously
> overlap the throbber (first) one.
>
> So my question is: is this example wrong, or has my wxLua compilation
> a hidden PB? - Debian sid 32 bits on an Athlon XP2600+ with regular LUA
> packages.

I have no problem with this sample in MSW and Mandriva Linux. What
wxLua are you using, did you compile it yourself? What wxWidgets
version and from where? What Lua version and are you sure you're
compiling wxLua using the lua-devel package from Debian sid or are you
compiling wxLua with it's own Lua (in modules/lua) and then running it
with the system installed Lua?

The fact that the wxBitmapComboBox is created and does show if not
added to the sizer, but crashes when added to the sizer makes me think
that you have mismatched libraries. You can get very strange and
nearly undebuggable errors in these cases. Try running ldd on the
wxLua libs to make sure that the libs it links to are appropriate,
especially liblua.so being in /lib/, /usr/lib/, or somewhere like that
to confirm that you're using the system Lua.

Hope this helps,
     John

Hi list,


There's something I don't understand in the example "controls.wx.lua",
the insertion of the "wx.wxBitmapComboBox" crashes the program with this
output:

$ lua JY_controls.wx.lua
lua: JY_controls.wx.lua:435: wxLua: Function call has invalid argument 2 on
method 03.

Function called: 'Add(wxFlexGridSizer, wxBitmapComboBox, number, number, number)'
01. wxSizer::Add(wxSizer(self), number [, number, number, number, number, wxObject])
02. wxSizer::Add(wxSizer(self) [, wxSizer, number, number, number, wxObject])
03. wxSizer::Add(wxSizer(self) [, wxWindow, number, number, number, wxObject])
stack traceback: [C]: in function 'Add'
	JY_controls.wx.lua:435: in function 'AddControl'
	JY_controls.wx.lua:514: in function 'CreateControlsWindow'
	JY_controls.wx.lua:1081: in function 'main'
	JY_controls.wx.lua:1120: in main chunk
	[C]: ?

The file's almost genuine (I just added some print lines to try to
understand what's wrong) and it works when I comment its last line:
"AddControl("wxBitmapComboBox", control)", making this control obviously
overlap the throbber (first) one.

So my question is: is this example wrong, or has my wxLua compilation
a hidden PB? - Debian sid 32 bits on an Athlon XP2600+ with regular LUA
packages.

JY
-- 
The man on tops walks a lonely street; the "chain" of command is often a
noose.