wxlua-users Mailing List for wxLua (Page 2)

Hi,

John Labenski wrote:
> On 6/26/07, Hakki Dogusan <dog...@tr...> wrote:
>> Since it compiled with gcc-4.1.2 I tried to find my other -translation-
>> problem first. After -all day- compiling with different configurations,
>> a few minutes ago I found the reason! (Why it is always the last one you
>> look for?)
>>
>> loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)
>>
>> print(loc:GetString("&About")) --not translated
>> print(loc:GetString("&About", "wxstd")) --translated
>>
>> print(wx.wxGetTranslation("&About")) --not translated
>> print(wx.wxGetTranslation("&About", "wxstd")) --translated
>>
>>
>> Do you know a quick solution? :)
> 
> You're doing better than I... why doesn't this work at all? Note, I
> just added the Init() function so I could get the return value, which
> is false, but it seemed to have set it anyway, but then doesn't
> translate it...
> 
> ========= code =============
> 
> wx.wxLocale.AddCatalogLookupPathPrefix("c:\\labenski\\wx\\wxWidgets\\wxWidgets-2.8.4\\locale\\")

Is ther any .mo file there?

> print(wx.wxLocale.IsAvailable(wx.wxLANGUAGE_TURKISH))
> 
> loc = wx.wxLocale()
> print(loc:Init(wx.wxLANGUAGE_TURKISH))
> print(loc:IsOk())
> print(loc:GetSysName())
> print(loc:GetLanguage(), wx.wxLANGUAGE_TURKISH)
> 
> print(loc:GetString("&About")) --not translated
> print(loc:GetString("&About", "wxstd")) --translated
> 
> print(wx.wxGetTranslation("&About")) --not translated
> print(wx.wxGetTranslation("&About", "wxstd")) --translated
> 

If you change calling order then Init returns true (I checked with 
current cvs), ie:

loc = wx.wxLocale()
loc.AddCatalogLookupPathPrefix("f:/a_c/dsuye/locale")
print(loc:Init(wx.wxLANGUAGE_TURKISH))
--print("AddCatalog:", loc:AddCatalog("wxstd")) --loaded automatically
print("AddCatalog:", loc:AddCatalog("dsuye"))

[snip]

I think I found the reason of requiring szDomain parameter to translate..

[intl.h]
virtual const wxChar *
GetString(const wxChar *szOrigString,
           const wxChar *szDomain = NULL) const;

virtual const wxChar *
GetString(const wxChar *szOrigString,
           const wxChar *szOrigString2,
           size_t n,
           const wxChar *szDomain = NULL) const;

szDomain is declared as wxChar here, and:

[intl.cpp ~2608]
it is checked against NULL


but in [wxLua - datetime.cpp ~5733] it is declared and used as wxString:
//virtual wxString
//GetString(const wxString& szOrigString,
//          const wxString& szDomain = "") const;
static int LUACALL wxLua_wxLocale_GetString(lua_State *L)
...
const wxString szDomain = (argCount >= 3 ?
                            wxlState.GetwxStringType(3) :
                            wxString(wxEmptyString));
...

If we omit szDomain parameter, it gets an emty string instead of NULL!


What do you think?


> Dunno,
>     John Labenski
> 


--
Regards,
Hakki Dogusan

needs setup.h to be within \wxWidgets\include\wx other projects use the platform
directory.

the following warnings are issued 

luamodule.obj : warning LNK4217: locally defined symbol
?SetEventHandler@wxLuaState@@QAEXPAVwxEvtHandler@@@Z (public: void __thiscall
wxLuaState::SetEventHandler(class wxEvtHandler *)) imported in 
function _luaopen_wx luamodule.obj : warning LNK4217: locally defined symbol
?Create@wxLuaState@@QAE_NPAUlua_State@@W4wxLuaState_Type@@@Z (public: bool
__thiscall wxLuaState::Create(struct lua_State *,enum wxLuaState_Type)) 
imported in function _luaopen_wx
luamodule.obj : warning LNK4217: locally defined symbol ?Ok@wxLuaState@@QBE_NXZ
(public: bool __thiscall wxLuaState::Ok(void)const ) imported in function
_luaopen_wx
luamodule.obj : warning LNK4217: locally defined symbol ??0wxLuaState@@QAE@_N@Z
(public: __thiscall wxLuaState::wxLuaState(bool)) imported in function _$E1
luamodule.obj : warning LNK4049: locally defined symbol ?wxEVT_LUA_ERROR@@3HB
(int const wxEVT_LUA_ERROR) imported
luamodule.obj : warning LNK4049: locally defined symbol ?wxEVT_LUA_PRINT@@3HB
(int const wxEVT_LUA_PRINT) imported
luamodule.obj : warning LNK4217: locally defined symbol ??1wxLuaState@@UAE@XZ
(public: virtual __thiscall wxLuaState::~wxLuaState(void)) imported in function 
_$E2

This is rather odd importing local name ??? the warning does not specify which
one is used. I suspect the local one cannot be overridden.

Andre

> 
> Humm... you added it to only this file?
> wxLua/modules/build/msvc6/modules_mod_luamodule.dsp
> 
> I think you're right in that it has to be added since we're building a
> DLL ourselves and not an executable so we wouldn't want to have
> WXUSINGDLL when building the luamodule.
> 
> Is the above true?
> 

Since I am working within Visual Studio I just edited the properties but I think
that it is same as adding it to the dsp.

Thank you

Andre

On 6/26/07, Andre <ar...@ki...> wrote:
> I finally compiled mod_luamodule and luamodule.wx.lua runs happily.
>
> The only change I have made was to add WXMAKINGDLL to the pre-processor defined
> list. This may hint to the right solution.
>

Humm... you added it to only this file?
wxLua/modules/build/msvc6/modules_mod_luamodule.dsp

I think you're right in that it has to be added since we're building a
DLL ourselves and not an executable so we wouldn't want to have
WXUSINGDLL when building the luamodule.

Is the above true?

Thanks,
    John Labenski

I finally compiled mod_luamodule and luamodule.wx.lua runs happily.

The only change I have made was to add WXMAKINGDLL to the pre-processor defined
list. This may hint to the right solution.

Andre

On 6/26/07, Hakki Dogusan <dog...@tr...> wrote:
> Since it compiled with gcc-4.1.2 I tried to find my other -translation-
> problem first. After -all day- compiling with different configurations,
> a few minutes ago I found the reason! (Why it is always the last one you
> look for?)
>
> loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)
>
> print(loc:GetString("&About")) --not translated
> print(loc:GetString("&About", "wxstd")) --translated
>
> print(wx.wxGetTranslation("&About")) --not translated
> print(wx.wxGetTranslation("&About", "wxstd")) --translated
>
>
> Do you know a quick solution? :)

You're doing better than I... why doesn't this work at all? Note, I
just added the Init() function so I could get the return value, which
is false, but it seemed to have set it anyway, but then doesn't
translate it...

========= code =============

wx.wxLocale.AddCatalogLookupPathPrefix("c:\\labenski\\wx\\wxWidgets\\wxWidgets-2.8.4\\locale\\")
print(wx.wxLocale.IsAvailable(wx.wxLANGUAGE_TURKISH))

loc = wx.wxLocale()
print(loc:Init(wx.wxLANGUAGE_TURKISH))
print(loc:IsOk())
print(loc:GetSysName())
print(loc:GetLanguage(), wx.wxLANGUAGE_TURKISH)

print(loc:GetString("&About")) --not translated
print(loc:GetString("&About", "wxstd")) --translated

print(wx.wxGetTranslation("&About")) --not translated
print(wx.wxGetTranslation("&About", "wxstd")) --translated

========= output =============

true
false
true
Turkish_Turkey.1254
210	210
&About
&About
&About
&About

================

There is something called wxstd.po that is loaded by default if you
use this wxLocale constructor, see wxWidgets/include/wx/intl.h

    wxLocale(const wxChar *szName,                               //
name (for messages)
             const wxChar *szShort = (const wxChar *) NULL,      //
dir prefix (for msg files)
             const wxChar *szLocale = (const wxChar *) NULL,     //
locale (for setlocale)
             bool bLoadDefault = true,                           //
preload wxstd.mo?
             bool bConvertEncoding = false)                      //
convert Win<->Unix if necessary?


Dunno,
    John Labenski

Hi,

John Labenski wrote:
> On 6/26/07, Hakki Dogusan <dog...@tr...> wrote:
>> Hi,
>>
>> John Labenski wrote:
>>> On 6/25/07, Hakki Dogusan <dog...@tr...> wrote:
>>>> Hi,
>>>>
>>>> (xp,wx2.8.4,mingw)
>>>>
>>>> - Current cvs gives internal compiler error for wx_bind.cpp at line 493
>>>> with gcc-3.4.5. It compiles with un-official gcc-4.1.2.
>>> What is the code for this? I think the line numbers have changed as I
>>> did some updates last night.
>> To be sure, I made a cvs update and re-compiled. Same result:
>>
>> ../../wxbind/src/wx_bind.cpp:493: internal compiler error:
>> output_operand: inval
>> id expression as operand
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://www.mingw.org/bugs.shtml> for instructions.
>> mingw32-make[1]: *** [gccmswu_dll\wxbind_dll_wx_bind.o] Error 1
>> mingw32-make[1]: Leaving directory `F:/a_C/wxLua/modules/build/msw'
>> mingw32-make: *** [modules] Error 2
> 
> "id expression as operand" sounds like it might be that one of the
> wxUSE_XXX defines is perhaps something more complicated that the
> preprocessor doesn't like? All of the wxLUA_USE_XXX defines are either
> 1 or 0 so they're simple.
> 
> It could also be that there are a lot of these preprocessor conditions
> and it's stack has overflowed. I know that VC6 w/o the service packs
> has a lot of problems with "complicated" code.
> 
> If you feel inspired you could use /* */ to rem out the first half,
> then the second half... and so on to narrow down where the problem
> really is. I don't think it should take too long and it would be nice
> to figure out if there is a real problem or not.
> 

(I'll try to compile with gcc-3.4.5 later)

Since it compiled with gcc-4.1.2 I tried to find my other -translation- 
problem first. After -all day- compiling with different configurations, 
a few minutes ago I found the reason! (Why it is always the last one you 
look for?)

loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)

print(loc:GetString("&About")) --not translated
print(loc:GetString("&About", "wxstd")) --translated

print(wx.wxGetTranslation("&About")) --not translated
print(wx.wxGetTranslation("&About", "wxstd")) --translated


Do you know a quick solution? :)


> Thanks,
>     John Labenski
> 

--
Regards,
Hakki Dogusan

On 6/26/07, Hakki Dogusan <dog...@tr...> wrote:
> Hi,
>
> John Labenski wrote:
> > On 6/25/07, Hakki Dogusan <dog...@tr...> wrote:
> >> Hi,
> >>
> >> (xp,wx2.8.4,mingw)
> >>
> >> - Current cvs gives internal compiler error for wx_bind.cpp at line 493
> >> with gcc-3.4.5. It compiles with un-official gcc-4.1.2.
> >
> > What is the code for this? I think the line numbers have changed as I
> > did some updates last night.
>
> To be sure, I made a cvs update and re-compiled. Same result:
>
> ../../wxbind/src/wx_bind.cpp:493: internal compiler error:
> output_operand: inval
> id expression as operand
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.mingw.org/bugs.shtml> for instructions.
> mingw32-make[1]: *** [gccmswu_dll\wxbind_dll_wx_bind.o] Error 1
> mingw32-make[1]: Leaving directory `F:/a_C/wxLua/modules/build/msw'
> mingw32-make: *** [modules] Error 2

"id expression as operand" sounds like it might be that one of the
wxUSE_XXX defines is perhaps something more complicated that the
preprocessor doesn't like? All of the wxLUA_USE_XXX defines are either
1 or 0 so they're simple.

It could also be that there are a lot of these preprocessor conditions
and it's stack has overflowed. I know that VC6 w/o the service packs
has a lot of problems with "complicated" code.

If you feel inspired you could use /* */ to rem out the first half,
then the second half... and so on to narrow down where the problem
really is. I don't think it should take too long and it would be nice
to figure out if there is a real problem or not.

Thanks,
    John Labenski

Hi,

John Labenski wrote:
> On 6/25/07, Hakki Dogusan <dog...@tr...> wrote:
>> Hi,
>>
>> (xp,wx2.8.4,mingw)
>>
>> - Current cvs gives internal compiler error for wx_bind.cpp at line 493
>> with gcc-3.4.5. It compiles with un-official gcc-4.1.2.
> 
> What is the code for this? I think the line numbers have changed as I
> did some updates last night.
> 

To be sure, I made a cvs update and re-compiled. Same result:

../../wxbind/src/wx_bind.cpp:493: internal compiler error: 
output_operand: inval
id expression as operand
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make[1]: *** [gccmswu_dll\wxbind_dll_wx_bind.o] Error 1
mingw32-make[1]: Leaving directory `F:/a_C/wxLua/modules/build/msw'
mingw32-make: *** [modules] Error 2


makefile.gcc:
BUILD := release
UNICODE := 1
SHARED := 1
WX_SHARED := 1
WX_MONOLITHIC := 1

build cmd (some switches may not be necessary, I'm using same for wx):
mingw32-make -fmakefile.gcc VENDOR=ds USE_OPENGL=1 MONOLITHIC=1 
BUILD=release SHARED=1 RUNTIME_LIBS=dynamic UNICODE=1



[snip]
> 
> Regards,
>     John Labenski
> 


--
Regards,
Hakki Dogusan

Hi,

John Labenski wrote:
> On 6/25/07, Hakki Dogusan <dog...@tr...> wrote:
>> Hi,
>>
>> (xp,wx2.8.4,mingw)
>>
>> - Current cvs gives internal compiler error for wx_bind.cpp at line 493
>> with gcc-3.4.5. It compiles with un-official gcc-4.1.2.
> 
> What is the code for this? I think the line numbers have changed as I
> did some updates last night.
> 

wxLuaBindEvent* wxLuaGetEventList_wx(size_t &count)
{
     static wxLuaBindEvent eventList[] =
     {
         { "wxEVT_ACTIVATE", &wxEVT_ACTIVATE, 
&s_wxluatag_wxActivateEvent },
......
         { 0, 0, 0 },
     };                      //<--- DIES HERE!
     count = sizeof(eventList)/sizeof(wxLuaBindEvent) - 1;
     return eventList;
}



>> - I'm trying to use wxLocale but didn't succeded. Is something like as
>> following working for you?
>>
>> require"wx"
>> loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)
>> loc.AddCatalogLookupPathPrefix("f:/a_c/dsuye/locale")
>> print("AddCatalog:", loc:AddCatalog("wxstd"))
>> print("IsOk:", loc:IsOk())
>> print("CanonicalName:", loc:GetCanonicalName())
>> print("Locale:", loc:GetLocale())
>> print("Translation:", loc:GetString("&About")) --not translated!
> 
> I haven't used wxLocale at all. I have seen messages on wx-users about
> translating menu items and the use of &, (I don't remember the
> outcome) did you try it without it?
> 

I choosed "&About" hoping there exists a translation everywhere :) Yes, 
I tried with other strings.

> There's also the problem that Lua is not unicode and uses only char*
> not w_char* so wxLua always translates wxStrings (wxChars) back to
> ANSI 8-bit char*. So, even if wxLocale sucessfully translates a string
> it may get mangled when returned to Lua.
> 

But, I have to get this mangled string, don't I?

> Please let me know if you get it work and if there is some simple test
> that might be useful to add to samples/unittest.wx.lua.
> 

Of course..


> Regards,
>     John Labenski
> 

--
Regards,
Hakki Dogusan

On 6/25/07, Hakki Dogusan <dog...@tr...> wrote:
> Hi,
>
> (xp,wx2.8.4,mingw)
>
> - Current cvs gives internal compiler error for wx_bind.cpp at line 493
> with gcc-3.4.5. It compiles with un-official gcc-4.1.2.

What is the code for this? I think the line numbers have changed as I
did some updates last night.

> - I'm trying to use wxLocale but didn't succeded. Is something like as
> following working for you?
>
> require"wx"
> loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)
> loc.AddCatalogLookupPathPrefix("f:/a_c/dsuye/locale")
> print("AddCatalog:", loc:AddCatalog("wxstd"))
> print("IsOk:", loc:IsOk())
> print("CanonicalName:", loc:GetCanonicalName())
> print("Locale:", loc:GetLocale())
> print("Translation:", loc:GetString("&About")) --not translated!

I haven't used wxLocale at all. I have seen messages on wx-users about
translating menu items and the use of &, (I don't remember the
outcome) did you try it without it?

There's also the problem that Lua is not unicode and uses only char*
not w_char* so wxLua always translates wxStrings (wxChars) back to
ANSI 8-bit char*. So, even if wxLocale sucessfully translates a string
it may get mangled when returned to Lua.

Please let me know if you get it work and if there is some simple test
that might be useful to add to samples/unittest.wx.lua.

Regards,
    John Labenski

Hi,

(xp,wx2.8.4,mingw)

- Current cvs gives internal compiler error for wx_bind.cpp at line 493 
with gcc-3.4.5. It compiles with un-official gcc-4.1.2.


- I'm trying to use wxLocale but didn't succeded. Is something like as 
following working for you?

require"wx"
loc = wx.wxLocale(wx.wxLANGUAGE_TURKISH)
loc.AddCatalogLookupPathPrefix("f:/a_c/dsuye/locale")
print("AddCatalog:", loc:AddCatalog("wxstd"))
print("IsOk:", loc:IsOk())
print("CanonicalName:", loc:GetCanonicalName())
print("Locale:", loc:GetLocale())
print("Translation:", loc:GetString("&About")) --not translated!


--
Regards,
Hakki Dogusan

John Labenski <jlabenski@...> writes:

> > Debug Unicode Multilib
> > LINK : fatal error LNK1181: cannot open input file 'wxlua_msw28ud_wxlua.lib'
> > add C:\Programs\wxWidgets\wxLua\lib\vc_lib\ path
> > -------------- compile
> > LINK : fatal error LNK1181: cannot open input file 'wxmsw28ud_xrc.lib'
> > add path C:\Programs\wxWidgets\lib\vc_lib\
> 
> This is probably not appropriate, mixing dll and static lib builds.
> What are you using to build wxLua? The *.sln files?

I simply create a solution and compile unicode multilib.
> 
> There are a couple things you can try:
> 
> 1) Use "Batch build" in both wxLua and wxWigets to make sure that
> these two missing libs are compiled. Sometimes for dlls you have to

The libs are compiled I check and they are there, just the directory are missing
from the additional library in the linker.

> 
> 2) Could you try to load wxLua/build/msvc6/wxLua.dsw and let it
> convert it to a sln file and see if that works.
> 
This is what I did.
> > >
> > > > cannot link with wxAppInitializer now this is somewhat more obscure.
> > >
> > -------------- compile
> 
> This sounds like a bad wxWidgets build. Has anything changed since it
> last worked? If not, I bet the problem is because you've mixed dll and
> static lib builds, see above. When you build as a dll the
> WXDLLEXPORT_XXX defines are set appropriately, for static libs they're
> defined to nothing and so the functions aren't exported (and therefore
> "missing")
> 
I simply use default everywhere except for using unicode.
I think something happen when the dsw is turned into an sln.

> 
> ps. I just tried it again w/ MSVC6 and wxWidgets 2.8.4 with no problems.
> 

Never got it working on 7, always removed it from the build.

I will compile it with 6 and see what happen.

On 6/24/07, Andre <ar...@ki...> wrote:
> John Labenski <jlabenski@...> writes:
>
> >
> > On 6/24/07, Andre <arpin@...> wrote:
> > > A couple of library are not reachable but do exist easily fixed.
> >
> Debug Unicode Multilib
> LINK : fatal error LNK1181: cannot open input file 'wxlua_msw28ud_wxlua.lib'
> add C:\Programs\wxWidgets\wxLua\lib\vc_lib\ path
> -------------- compile
> LINK : fatal error LNK1181: cannot open input file 'wxmsw28ud_xrc.lib'
> add path C:\Programs\wxWidgets\lib\vc_lib\

This is probably not appropriate, mixing dll and static lib builds.
What are you using to build wxLua? The *.sln files?

There are a couple things you can try:

1) Use "Batch build" in both wxLua and wxWigets to make sure that
these two missing libs are compiled. Sometimes for dlls you have to
build a few times since the dlls have to get linked to libs (not the
static ones, but ones built for the dll, see wxLua/lib/vc_dll and you
should have a xxx.lib for every xxx.dll) and they fail unless they all
exist at once. Just keep pressing build until you don't get any more
errors about missing libs. (yeah it's ugly)

2) Could you try to load wxLua/build/msvc6/wxLua.dsw and let it
convert it to a sln file and see if that works.

> >
> > > cannot link with wxAppInitializer now this is somewhat more obscure.
> >
> -------------- compile
> luamodule.obj : error LNK2019: unresolved external symbol "__declspec(dllimport)
> public: __thiscall wxAppInitializer::wxAppInitializer(class wxAppConsole *
> (__cdecl*)(void))" (__imp_??0wxAppInitializer@@QAE@P6APAVwxAppConsole@@XZ@Z)
> referenced in function _$E7

This sounds like a bad wxWidgets build. Has anything changed since it
last worked? If not, I bet the problem is because you've mixed dll and
static lib builds, see above. When you build as a dll the
WXDLLEXPORT_XXX defines are set appropriately, for static libs they're
defined to nothing and so the functions aren't exported (and therefore
"missing")

Regards,
    John Labenski

ps. I just tried it again w/ MSVC6 and wxWidgets 2.8.4 with no problems.

John Labenski <jlabenski@...> writes:

> 
> On 6/24/07, Andre <arpin@...> wrote:
> > A couple of library are not reachable but do exist easily fixed.
> 
Debug Unicode Multilib
LINK : fatal error LNK1181: cannot open input file 'wxlua_msw28ud_wxlua.lib'
add C:\Programs\wxWidgets\wxLua\lib\vc_lib\ path
-------------- compile
LINK : fatal error LNK1181: cannot open input file 'wxmsw28ud_xrc.lib'
add path C:\Programs\wxWidgets\lib\vc_lib\

> 
> > cannot link with wxAppInitializer now this is somewhat more obscure.
> 
-------------- compile
luamodule.obj : error LNK2019: unresolved external symbol "__declspec(dllimport)
public: __thiscall wxAppInitializer::wxAppInitializer(class wxAppConsole *
(__cdecl*)(void))" (__imp_??0wxAppInitializer@@QAE@P6APAVwxAppConsole@@XZ@Z)
referenced in function _$E7

> Again, the error message would be helpful in understanding what the problem is.
> 
> > Any one can compile this code?
> 
> I don't use 2007, but it works with VC6.
> 

Hope this help

On 6/24/07, Andre <ar...@ki...> wrote:
> A couple of library are not reachable but do exist easily fixed.

What does this mean? What are the messages and your fixes?

> cannot link with wxAppInitializer not this is somewhat more obscure.

Again, the error message would be helpful in understanding what the problem is.

> Any one can compile this code?

I don't use 2007, but it works with VC6.

Regards,
    John Labenski

A couple of library are not reachable but do exist easily fixed.

cannot link with wxAppInitializer not this is somewhat more obscure.

Any one can compile this code?

Andre

John Labenski <jlabenski@...> writes:

> Therefore, if you compiled in 2.6
> (maybe that's what you're doing?) genwxbind.lua would still put a 4 as
> the maxargs.
> 
I use 2.8

> 
> Do you mind if we just sweep this under the rug for now... they can
> only have a smaller min and greater max than what really exists after
> taking the #ifdefs into account.  :)
> 


If it is your rug it is OK; there no more space under mine :)

Andre

On 6/15/07, Andre <ar...@ki...> wrote:
> > Try out the program samples/bindings.wx.lua! You can browse though all
> > of the bindings.
>
> Most impressive and extremely useful.

There's a few bugs in the version you're using, I've fixed them already.

> I look at it for a very short time will come back for sure.
>
> Why do wxColour:wxColour 4 has a maxargs of 4.

Humm, that is ok I think. The 4th one is the one with alpha.

    !%wxchkver_2_8 wxColour(red,  green,  blue)
    %wxchkver_2_8 wxColour(red, green, blue, alpha = wxALPHA_OPAQUE)
    wxColour(const wxString& colourName)
    wxColour(const wxColour& colour)

You bring up a good point though, currently the overload function is
created with min/maxargs set to min/max of all of the functions it
overloads and this is done by genwxbind.lua which doeesn't take into
account the wxchkver_2_8 above. Therefore, if you compiled in 2.6
(maybe that's what you're doing?) genwxbind.lua would still put a 4 as
the maxargs.

Ehhh... this is unfortunate, but not serious at since we don't use the
min/maxargs from the overload function. I just put them to the overall
min/max because maybe someday they might be used. The logic to add
them up correctly would create some ugly #ifdefs in the bindings and I
think that setting them at runtime would be overkill.

Do you mind if we just sweep this under the rug for now... they can
only have a smaller min and greater max than what really exists after
taking the #ifdefs into account.  :)

Regards,
    John Labenski

ps. Thanks for the wxlua.CompileLuaScript() fix.

> Try out the program samples/bindings.wx.lua! You can browse though all
> of the bindings.

Most impressive and extremely useful. 

I look at it for a very short time will come back for sure.

Why do wxColour:wxColour 4 has a maxargs of 4.

Andre

John Labenski <jlabenski@...> writes:

> It is wxlua.CompileLuaScript() now and everything else specific to
> wxLua or lua (not wxWidgets) will go there from now on.
> 

editor.wx.lua line 1723 should be changed

local ret, errMsg, line_num = wx.CompileLuaScript(editorText, filePath)

Andre

On 6/14/07, Andre <ar...@ki...> wrote:
>
> > I'm going to let the dust settle to make sure there aren't any more
> > problems and do a release.
> >
>
> I thing the binding for CompileLuaScript is missing

It is wxlua.CompileLuaScript() now and everything else specific to
wxLua or lua (not wxWidgets) will go there from now on.

Try out the program samples/bindings.wx.lua! You can browse though all
of the bindings.

Regards,
    John Labenski

> I'm going to let the dust settle to make sure there aren't any more
> problems and do a release.
> 

I thing the binding for CompileLuaScript is missing

Andre

On 6/14/07, Hakki Dogusan <dog...@tr...> wrote:
> Hi,
>
> I made following changes in wxlstate.cpp to compile (using a
> Code::Blocks project):
>
> -original LUALIB_API int luaopen_bit (lua_State *L) {
> -modified int LUACALL luaopen_bit (lua_State *L) {

Fixed, thanks.

> -original #include "wxlua.cpp"
> -original #include "wxlua_bind.cpp"
> -modified #include "wxlua/src/wxlua.cpp"
> -modified #include "wxlua/src/wxlua_bind.cpp"

This was a hack that I didn't think anyone would notice before I got a
change to redo the build files with bakefile.

> I tested BookWorm with new wxLua. After some -expected- changes (Delete
> vs delete, AddWindow vs Add, etc.) it worked.

Glad it still works and I hope you'll like it better.
    John Labenski

Hi,

John Labenski wrote:
> All the proposed major changes have been made and a complete list of
> them are in the changelog.
> 
> http://wxlua.cvs.sourceforge.net/wxlua/wxLua/docs/changelog.txt?view=markup
> 
> All the samples and docs have been updated, I'm done.
> 
> Browse changes here:
> http://wxlua.cvs.sourceforge.net/wxlua/wxLua/
> 
> I'm going to let the dust settle to make sure there aren't any more
> problems and do a release.
> 
> Regards,
>     John Labenski
> 

Huge changelog!

I made following changes in wxlstate.cpp to compile (using a 
Code::Blocks project):

-original LUALIB_API int luaopen_bit (lua_State *L) {
-modified int LUACALL luaopen_bit (lua_State *L) {

-original #include "wxlua.cpp"
-original #include "wxlua_bind.cpp"
-modified #include "wxlua/src/wxlua.cpp"
-modified #include "wxlua/src/wxlua_bind.cpp"


I tested BookWorm with new wxLua. After some -expected- changes (Delete 
vs delete, AddWindow vs Add, etc.) it worked.


Thank you!


--
Regards,
Hakki Dogusan