On Mon, Dec 19, 2011 at 6:22 AM, klaas.holwerda <n...@klaasholwerda.nl> wrote:
>
> This i get with 2.9.2 .
>
> 2>Compiling...
> 1>wxaui_bind.cpp
> 2>wxaui_bind.cpp
> 2>..\..\..\wxLua\trunk\wxLua\modules\wxbind\src\wxaui_bind.cpp(696) : error
> C2039: 'curState' : is
> not a member of 'wxAuiTabContainerButton'
> 2> C:\soft\wxWidgets-2.9.2\include\wx/aui/auibook.h(116) : see
> declaration of
> 'wxAuiTabContainerButton'
> 2>..\..\..\wxLua\trunk\wxLua\modules\wxbind\src\wxaui_bind.cpp(730) : error
> C2039: 'disBitmap' : is
> not a member of 'wxAuiTabContainerButton'
> 2> C:\soft\wxWidgets-2.9.2\include\wx/aui/auibook.h(116) : see
> declaration of
These were recently renamed. I have now made then #ifdefed for 2.9.3
instead of 2.9.2 and that should work. Though if you have a checkout
half-way between 2.9.2 and 2.9.3 then there's nothing I can do and you
should just update.
> For 2.8 i see:
>
> 2>..\..\..\wxLua\trunk\wxLua\modules\wxbind\src\wxcore_gdi.cpp(8396) : error
> C2666:
> 'wxCursor::wxCursor' : 2 overloads have similar conversions
> 2> C:\soft\wxWidgets-2.8.12\include\wx/msw/cursor.h(29): could be
> 'wxCursor::wxCursor(const
> wxString &,long,int,int)'
> 2> C:\soft\wxWidgets-2.8.12\include\wx/msw/cursor.h(26): or
> 'wxCursor::wxCursor(const
> char [],int,int,int,int,const char [])'
> 2> while trying to match the argument list '(const wxString,
> wxBitmapType, int, int)'
> 3>..\..\..\wxLua\trunk\wxLua\modules\wxbind\src\wxcore_gdi.cpp(8396) : error
> C2666:
> 'wxCursor::wxCursor' : 2 overloads have similar conversions
> 3> C:\soft\wxWidgets-2.8.12\include\wx/msw/cursor.h(29): could be
> 'wxCursor::wxCursor(const
> wxString &,long,int,int)'
> 3> C:\soft\wxWidgets-2.8.12\include\wx/msw/cursor.h(26): or
> 'wxCursor::wxCursor(const
> char [],int,int,int,int,const char [])'
>
> I don't know how to see what compiler i use with VC, i only see /D WIN32 so i
> ques that means i am
> compiling 32bit. The rest is default, or what Cmake thinks/says it is.
> This is windows7 64 bit. For 2.8 i used debug non unicode. So that is the
> reason for the string
> confusion i think.
This really does seem like a overload problem. wxLua tries to call the
wxCursor(wxString, ...) constructor using a wxString as the first
parameter, but somehow the compiler thinks that the const char[] is
equally good. I don't know if I blame the compiler, but I don't think
we can do much more than #ifdefing that function for > 2.8 ||
__UNICODE__. In 2.9 the second parameter is the enum wxBitmapType so
you won't see this problem. Note that I had just typedefed
wxBitmapType to an int in 2.8 to simplify things.
Both of these problems should be fixed for you in SVN now.
Regards,
John
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
