wxlua-users Mailing List for wxLua

Bugs item #1729217, was opened at 2007年06月01日 01:41
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=1729217&group_id=140042
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Pavel Vozenilek (pvozenilek)
Assigned to: Nobody/Anonymous (nobody)
Summary: no 2.6 compatibility -> compilation failure
Initial Comment:
I compile the fresh CVS wxLua (after big changes announced today by John Labenski) with wxWidgets 2.8.4 and Lua 5.1.2, using MingW GCC 4.1.2 (unofficial) on WinXP.
In wxlua/src/wxstate.cpp, ~line 836, the test
 while (node != NULL)
should be changed to 
 while (node != 0)
to avoid compiler warning.
I use wxWidgets without 2.6 compatibility but wxLua tries to use symbols:
* wxEVT_SCROLL_ENDSCROLL
* WXK_NEXT
* WXK_NUMPAD_NEXT
* WXK_PRIOR
* wxDIALOG_MODAL
* wxDIALOG_MODELESS
* wxPASSWORD
and several more and finds none.
----------------------------------------------------------------------
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=1729217&group_id=140042

For the adventuresome only, make a backup of the current source you
have in case something is really wrong. I will be away for the next
few days...
Committed to the CVS head are quite a few changes to how wxLua handles
overloaded (more than one function with the same name) functions,
static class member functions, and class member enums.
static class member functions:
 wx.ClassName_StaticMemberFunc is now wx.ClassName.StaticMemberFunc
class member enums
 wx.ClassName_MemberEnum is now wx.ClassName.MemberEnum
Overloaded functions are now generated automatically and which
function to call is automatically determined. This means that
previously %renamed functions or constructors probably use the C++
function name.
 Examples :
 wxEmptyBitmap(w, h) is now wxBitmap(w, h)
 wxBitmapFromFile('name') is now wxBitmap('name')
 wxSizer::AddWindow and AddSizer is now just Add(...)
 wxPenCopy(otherPen) is now just wxPen(otherPen)
Also the %property tag was removed and they are generated on the fly at runtime.
There is a list of what has changed in the docs/changelog.txt file
here, which does not exaustively list the individual function changes
(too many), but lists what was changed overall.
http://wxlua.cvs.sourceforge.net/wxlua/wxLua/docs/
See also wxluaref.html, wxlua.html, and bindings.html which have been
updated as well.
All the samples have been updated and everything seems to work as
planned. I hope everyone agrees that this new way is far better and
though it may be a little painful right now, we won't have to ever do
it again. :)
Finally, there may be a few rough edges with the remaining %renamed
functions and I plan to carefully go though the rest of them to get
rid of anything else that's a little ugly.
Regards,
 John Labenski

On 5/29/07, Andre <ar...@ki...> wrote:
> Sorry just finding them one at the time
>
> line 1870 change from
> ok = debuggerServer:AddBreakPoint(fileName, nextLine)
> ok = debuggerServer:AddBreakPoint(filePath, nextLine)
>
> changing fileName to filePath
Thanks! Changed in CVS, but I can't commit until other things are fixed.
 John Labenski

John Labenski <jlabenski@...> writes:
> 
> The bindings have some GetXXX and SetXXX functions declared using the
> %property tag.
> 
> For example, the wxSize bindings have
> 
> int wxSize::GetWidth()
> void wxSize::SetWidth(int width)
> %property=Width, read, write
> 
> and can be accessed as
> 
> s = wx.wxSize(0,0)
> print(s.Width) <==> print(s:GetWidth())
> s.Width = 5 <==> s:SetWidth(5)
> 
I have been using them. If it make your life easier I can change my code.
To tell you the true I find the get and set somewhat suspect :) Here you to each
is own.
Please just post if you will remove them I will vhange my code now and get it
over with I really don't mind.
Andre

Sorry just finding them one at the time
line 1870 change from 
ok = debuggerServer:AddBreakPoint(fileName, nextLine)
ok = debuggerServer:AddBreakPoint(filePath, nextLine)
changing fileName to filePath
Andre

On 5/28/07, Hakki Dogusan <dog...@tr...> wrote:
> Hi,
>
> John Labenski wrote:
> >
> > ps. Just a heads up, I'm rewriting quite a bit of the internals of
> > wxLua so that all static member class functions and enums are part of
> > a table with the name of the class. You can call the class constructor
> > just like before.
> > [snip]
>
> Could you show a usage sample please? I updated from CVS but no change
> committed for samples about this usage.
It turned out to be a much bigger job than I thought. Unfortunately
I'm not done yet.
-John Labenski

The bindings have some GetXXX and SetXXX functions declared using the
%property tag.
For example, the wxSize bindings have
int wxSize::GetWidth()
void wxSize::SetWidth(int width)
%property=Width, read, write
and can be accessed as
s = wx.wxSize(0,0)
print(s.Width) <==> print(s:GetWidth())
s.Width = 5 <==> s:SetWidth(5)
I have made some massive changes to the bindings that allow functions
to be seamlessly overloaded (no more hacks like wxBitmap(...),
wxBitmapFromFile(...), and wxEmptyBitmap(...)). However, in order to
do this, the C binding functions are named when generated and since
many functions are #ifdefed for different platforms and wxWidgets
versions it has become hard to tell if a function will actually exist
when compiled with any given platform or version.
Bottom line, I personally don't use them and find them a little
suspect, in that they're probably more confusing than anything. There
only benefit I can see is that you save a little typing... (note: they
only work for GetXXX and SetXXX where the SetXXX function takes 1
parameter)
Thoughts? If none I will finish the changes off and leave them
disabled. If people really like them, they can be made to work...
Regards,
 John Labenski

Hi,
John Labenski wrote:
> 
> ps. Just a heads up, I'm rewriting quite a bit of the internals of
> wxLua so that all static member class functions and enums are part of
> a table with the name of the class. You can call the class constructor
> just like before. 
> [snip]
Could you show a usage sample please? I updated from CVS but no change 
committed for samples about this usage.
--
Regards,
Hakki Dogusan

On 5/24/07, Andre <ar...@ki...> wrote:
> -- ASCII values for common chars
> local char_CR = string.byte("\n")
> local char_LF = string.byte("\r")
>
> I think this should be reversed
>
> local char_CR = string.byte("\r")
> local char_LF = string.byte("\n")
>
Oops, thanks, fixed now.
John Labenski
ps. Just a heads up, I'm rewriting quite a bit of the internals of
wxLua so that all static member class functions and enums are part of
a table with the name of the class. You can call the class constructor
just like before. I also want to complete overriding all of the
functions that are currently renamed to get rid of the confusion about
them. However, since nobody likes to update their code, I'm going to
add much better error messages showing the expected input for the
functions and a way to print out the expected inputs so you don't have
to check the docs as often.

On 5/27/07, Andre <ar...@ki...> wrote:
> the case:
> wxLUASOCKET_DEBUGGER_CMD_ADD_BREAKPOINT
> is missing a break statement.
>
Thank you, fixed now.
John Labenski

the case:
wxLUASOCKET_DEBUGGER_CMD_ADD_BREAKPOINT 
is missing a break statement.
Andre

Hi,
(In case you're not following Lua list)
(Warning! This is a test release. There are too many "not implemented" 
messages and TODO's.)
- Binding for Cairo-1.4.6
- Source included
- Win32 binary included, compiled with Mingw
- There is a snippet runner app, written with wxLua
- Code::Blocks project file for cairo included
 (It's a XML file, you may edit before usage)
- lcario creates two -namespace- tables:
 cairo - for functions
 CAIRO - for constants, enums
 this simplifies translating C code to Lua, ie:
 cairo_set_operator (cr, CAIRO_OPERATOR_ADD);
 becomes:
 cairo.set_operator (cr, CAIRO.OPERATOR_ADD)
- Unzip somewhere, run run.bat :)
You can get it here:
http://www.dogusan.net/dogusanh/download/luacairo.zip (3206Kb)
--
Regards,
Hakki Dogusan

-- ASCII values for common chars
local char_CR = string.byte("\n")
local char_LF = string.byte("\r")
I think this should be reversed
local char_CR = string.byte("\r")
local char_LF = string.byte("\n")
Andre

John Labenski <jlabenski@...> writes:
> Thanks for the staktree.h include, it's probably best to put that in the
> header.
The new version compile and runs
Thanks
Andre
> John Labenski
> 
> ps. Let me know what you think of the the new stack dialog. I replaced
> the old treectrl hack with a listctrl and I think it's a lot nicer
> code wise, but maybe not as nice visually. But then again, the old
> control was really broken in GTK and really couldn't be fixed since we
> were asking it to do things it wasn't meant to do.
> 
I have not been working on this project for 2 months.
The debugger works a LOT BETTER the stack looks great just spend a short time.
I will move the change in my code in the next couple of days looking forward to
upgrade the whole thing.

On 5/23/07, Andre <ar...@ki...> wrote:
> The following changes made the file compile using nmake
>
> file dservice.cpp, staktree.cpp
>
> ------------------------
> #include "wx/wxprec.h"
>
> #ifdef __BORLANDC__
> #pragma hdrstop
> #endif
>
> #ifndef WX_PRECOMP
> #include "wx/wx.h"
> #endif
> ----------------------------------
> remove error eof when looking for pch
> -----------------------------------
>
> file: staktree.h
>
> --------------------
> #include "wx/listctrl.h"
> ----------------------
>
> Hopefully this will help to find proper fixes
That's strange that you have to add the pch stuff to an empty file. In
any case dservice.cpp, staktree.cpp and their headers will be removed
soon. I've added the code above temporarily.
Thanks for the staktree.h include, it's probably best to put that in the header.
Thanks,
 John Labenski
ps. Let me know what you think of the the new stack dialog. I replaced
the old treectrl hack with a listctrl and I think it's a lot nicer
code wise, but maybe not as nice visually. But then again, the old
control was really broken in GTK and really couldn't be fixed since we
were asking it to do things it wasn't meant to do.

The following changes made the file compile using nmake
file dservice.cpp, staktree.cpp
------------------------
#include "wx/wxprec.h"
#ifdef __BORLANDC__
 #pragma hdrstop
#endif
#ifndef WX_PRECOMP
 #include "wx/wx.h"
#endif
---------------------------------- 
remove error eof when looking for pch
-----------------------------------
file: staktree.h
--------------------
#include "wx/listctrl.h"
----------------------
Hopefully this will help to find proper fixes 
Andre

Hi,
woot, yes! thank you, now it works like a charm ^_^
~ Kenneth
Bradley Smith wrote:
> Kenneth Forsbäck wrote:
>> Hi,
>>
>> indeed,
>>
>> wx.wxMessageBox(tostring(aboutBackground:Ok()), "results", wx.wxOK +
>> wx.wxICON_INFORMATION, instanceAbout)
>>
>> results in false. I tried using an absolute path, but that didn't work
>> either. There's also nothing wrong with the current directory in lua,
>> i.e. the root dir, so the image path is then:
>> "interface/about/aboutBackground.png"
>>
>> ~ Kenneth
> 
> You might want to try this:
> 
> local aboutBackground = 
> wx.wxBitmapFromFile("interface/about/aboutBackground.bmp", 
> wx.wxBITMAP_TYPE_BMP)
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Kenneth Forsbäck wrote:
> Hi,
> 
> indeed,
> 
> wx.wxMessageBox(tostring(aboutBackground:Ok()), "results", wx.wxOK +
> wx.wxICON_INFORMATION, instanceAbout)
> 
> results in false. I tried using an absolute path, but that didn't work
> either. There's also nothing wrong with the current directory in lua,
> i.e. the root dir, so the image path is then:
> "interface/about/aboutBackground.png"
> 
> ~ Kenneth
You might want to try this:
local aboutBackground = 
wx.wxBitmapFromFile("interface/about/aboutBackground.bmp", 
wx.wxBITMAP_TYPE_BMP)

the script is launched from "i:\src\studio\" and the CWD is the same, so
the image path "interface/about/aboutBackground.png" is corret.
I even tried with an absolute path
"i:\src\studio\interface\about\aboutBackground.png", and it still
doesn't work O_O
John Labenski wrote:
> 
> Try using wx.wxGetCwd() to see what dir wxWidgets would use for
> loading the bitmap.

T24gNS8yMi8wNywgSGFra2kgRG9ndXNhbiA8ZG9ndXNhbmhAdHIubmV0PiB3cm90ZToKPiBIaSwK
Pgo+IEtlbm5ldGggRm9yc2LkY2sgeWF6bf3+Ogo+ID4gU0drc0NncHBibVJsWldRc0NncDNlQzUz
ZUUxbGMzTmhaMlZDYjNnb2RHOXpkSEpwYm1jb1lXSnZkWFJDWVdOclozSnZkVzVrT2s5cgo+IFtz
bmlwcGVkLCBpbWFnZT9dCj4KPgo+IEluIGFkZGl0aW9uIHRvIGNoZWNraW5nIGFib3V0QmFja2dy
b3VuZDpPaygpLCB1c2luZyBhbiBhYnNvbHV0ZSBwYXRoIGZvcgo+IGltYWdlIGNvdWxkIGJlIHVz
ZWZ1bC4uCgpUcnkgdXNpbmcgd3gud3hHZXRDd2QoKSB0byBzZWUgd2hhdCBkaXIgd3hXaWRnZXRz
IHdvdWxkIHVzZSBmb3IKbG9hZGluZyB0aGUgYml0bWFwLgoKUmVnYXJkcywKICAgIEpvaG4gTGFi
ZW5za2kK

Hi,
Kenneth Forsbäck yazmış:
> SGksCgppbmRlZWQsCgp3eC53eE1lc3NhZ2VCb3godG9zdHJpbmcoYWJvdXRCYWNrZ3JvdW5kOk9r
[snipped, image?]
In addition to checking aboutBackground:Ok(), using an absolute path for 
image could be useful..
--
Regards,
Hakki Dogusan

Hi,
indeed,
wx.wxMessageBox(tostring(aboutBackground:Ok()), "results", wx.wxOK +
wx.wxICON_INFORMATION, instanceAbout)
results in false. I tried using an absolute path, but that didn't work
either. There's also nothing wrong with the current directory in lua,
i.e. the root dir, so the image path is then:
"interface/about/aboutBackground.png"
~ Kenneth
Hakki Dogusan wrote:
> Hi,
> 
> Kenneth Forsbäck yazmış:
>> Hi,
>>
>> yes it works now, I can see the red rectangle. How strange, I even tried
>> making a new image, even tried png instead of bmp, and it still doesn't
>> work O_O. I doubt there's anything wrong with the image...
>>
>> ~ Kenneth
>>
> 
> Maybe it's not loading?
> 
> What is the result of aboutBackground:Ok() ?
> 
> 
> 
> --
> Regards,
> Hakki Dogusan

Hi,
Kenneth Forsbäck yazmış:
> Hi,
> 
> yes it works now, I can see the red rectangle. How strange, I even tried
> making a new image, even tried png instead of bmp, and it still doesn't
> work O_O. I doubt there's anything wrong with the image...
> 
> ~ Kenneth
> 
Maybe it's not loading?
What is the result of aboutBackground:Ok() ?
--
Regards,
Hakki Dogusan

Hi,
yes it works now, I can see the red rectangle. How strange, I even tried
making a new image, even tried png instead of bmp, and it still doesn't
work O_O. I doubt there's anything wrong with the image...
~ Kenneth
Hakki Dogusan wrote:
> Hi,
> 
> Kenneth Forsbäck yazmış:
>> Hi,
>>
>> LOL, no I did not connect those events ^_^, and most certainly not a
>> stupid question.
>>
>> However, it still doesn't work! Only thing that changed is that now the
>> panel isn't visible any more, there's only the dark gray background of
>> the frame.
>>
>> ~ Kenneth
>>
> 
> Ok, it's painting now :)
> 
> To be sure, could you please change OnPaint like this:
> 
> function OnPaint(event)
> local dc = wx.wxPaintDC(aboutPanel)
> dc:SetBrush(wx.wxRED_BRUSH)
> dc:DrawRectangle(0, 0, 100, 100)
> dc:Delete() -- clean up
> end
> 
> If this works, then your bitmap may be faulty..
> 
> 
> --
> Regards,
> Hakki Dogusan
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users

Hi,
Kenneth Forsbäck yazmış:
> Hi,
> 
> LOL, no I did not connect those events ^_^, and most certainly not a
> stupid question.
> 
> However, it still doesn't work! Only thing that changed is that now the
> panel isn't visible any more, there's only the dark gray background of
> the frame.
> 
> ~ Kenneth
> 
Ok, it's painting now :)
To be sure, could you please change OnPaint like this:
function OnPaint(event)
 local dc = wx.wxPaintDC(aboutPanel)
 dc:SetBrush(wx.wxRED_BRUSH)
 dc:DrawRectangle(0, 0, 100, 100)
 dc:Delete() -- clean up
end
If this works, then your bitmap may be faulty..
--
Regards,
Hakki Dogusan