wxlua-users Mailing List for wxLua

John Labenski <jlabenski@...> writes:

> 
> On Sat, Nov 20, 2010 at 4:55 PM, Andre Arpin <arpin@...> wrote:
> > The following modification allow wx.dll to work on window 7 / 64 bits.
> > Without it you get a warning specifiying that comctl32.dll is not loaded.
> > Why this suddenly happen is unknowned and will probably remain this way.
> >
> > // Override the base class virtual functions
> > bool wxLuaModuleApp::OnInit()
> > {
> > #ifdef __WXMSW__
> >        wxDynamicLibrary comctl32(_T("comctl32.dll"), wxDL_NOW);
> > #endif
> >    return true;
> > }
> 

Sorry to tell you that 
	::LoadLibrary(_T("comctl32.dll"));
has to be used. I think that I managed to lock the comctl32.dll
permanently when I tested wxDynamicLibrary.

Andre

> 
> I have applied a much simpler patch in CVS. I assume that you want to
> ignore the "#!/bin/lua" at the beginning so I check for "#!" and rem
> out the first line if it exists, this maintains line numbers.
> 
> http://wxlua.cvs.sourceforge.net/viewvc/wxlua/wxLua/samples/editor.wx.lua?
r1=1.60&r2=1.61
> 

Actually the test should be for '#' not '#!' to be consistent with lua.

Andre

John Labenski <jlabenski@...> writes:

Look good to me

On Wed, Nov 24, 2010 at 1:57 PM, Andre Arpin <ar...@ki...> wrote:
> SourceForge.net <noreply@...> writes:
>
>> The following code added to the CompileFunction solves the problem
>>     local firstLine = editor:GetTextRange(0, editor:PositionFromLine(1))
>>     if string.sub(firstLine, 1,1) == '#' then
>>         editorText = '--' .. string.sub(editorText, #firstLine)
>>     end

This destroys the editorText string right? It only contains
"--[contents after first line]".

> the folloding code is better
>
>    local editorText =  iff(string.char(editor:GetCharAt(0)) == '#',
>        '\n'..editor:GetTextRange(editor:PositionFromLine(1), editor.Length),
>        editor.Text)

I have applied a much simpler patch in CVS. I assume that you want to
ignore the "#!/bin/lua" at the beginning so I check for "#!" and rem
out the first line if it exists, this maintains line numbers.

http://wxlua.cvs.sourceforge.net/viewvc/wxlua/wxLua/samples/editor.wx.lua?r1=1.60&r2=1.61

Regards,
    John

SourceForge.net <noreply@...> writes:

> The following code added to the CompileFunction solves the problem
>     local firstLine = editor:GetTextRange(0, editor:PositionFromLine(1))
>     if string.sub(firstLine, 1,1) == '#' then
>         editorText = '--' .. string.sub(editorText, #firstLine)
>     end
> 

the folloding code is better

    local editorText =  iff(string.char(editor:GetCharAt(0)) == '#',
        '\n'..editor:GetTextRange(editor:PositionFromLine(1), editor.Length),
        editor.Text)

Andre

John Labenski <jlabenski@...> writes:

> 
> What compiler and version are you using?
> 
Visual Studi0 2008

> Well I don't have more than one version of Lua or wxWidgets installed. I
> installed them directly form the apt repository in Ubuntu. I checked ldd and
> did not find any .so that linked to anything outside the systems version of
> Lua.  Could it be a difference because wxLua is bound to 2.8.10 and the
> version I am building is using 2.8.11?

No, the only reason that wxLua hasn't been released for 2.8.11 is that
there aren't many (if any) changes in wxWidgets that would affect
people. I use wxLua compiled with 2.8.11 exclusively.

> I also tried using the local only versions and it still segmentation faults.

Please try to install "gdb" and then run

$gdb lua

In the gdb prompt type "run myprogram.lua", when it segfaults type
"bt" and post the results.

> So I did find out that if I use 'wxlua' to run the scripts everything works
> fine. So it seems to be erroring out using the wxLua Lua module (wx.so) from
> strait lua. Does that help at all? In fact, it is not the line of requiring

Yes, that's why I am thinking that there is some mismatch between the
Lua wxLua was compiled with and the Lua on your system. wxLua comes
with it's own Lua in wxLua/modules/lua, it's completely generic, but
has some patches applied. Please look at "config.log" or the output of
configure to see that wxLua is not compiling against
wxLua/modules/lua, but /usr/include/lua...

> that seg faults, it is the first time you call into the library and display
> a GUI element (like a wxMessageBox). Now if I pass the wrong parameters to a
> function in wxLua it will give me the normal wxLua error message. It does
> not actually seg fault on that. Does this help?

Not really, you can run apps with mismatched libs with some success,
until you hit a function that is different, then you crash.

Regards,
    John

On Tue, Nov 23, 2010 at 12:16 AM, John Labenski <jla...@gm...> wrote:

> > On Wed, Nov 3, 2010 at 1:02 PM, Ryan Pusztai <rpu...@gm...> wrote:
> >>
> >> Hi,
> >>
> >> I have downloaded the latest release of wxLua and built it using the
> >> documented method from the wxLua website (./configure, make, sudo make
> >> install). After I 'sudo make install' and I try to just simply 'require(
> >> "wx" )' and call wx.wxMessageBox("Hello") I get a Segmentation fault. It
> is
> >> building wxLua v2.8.10 with wxWidgets version 2.8.11. Any thoughts?
> >> Terminal output:
> >>   $ lua
> >>   Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
> >>   > require( "wx" )
> >>   > wx.wxMessageBox("hi")
> >>   Segmentation fault
> >
> > Any ideas about this? I sent it quite a while ago and not sure if anyone
> has
> > an idea. Thanks.
>
> Sorry no ideas. I would guess that you have mismatched versions of
> Lua. Maybe you have a system Lua installed or two versions of
> wxWidgets on your system? I would try running ldd on the wxlua libs
> and make sure that everything is in order. You can also try to execute
> the program using the lua executable that wxLua compiles, i.e. don't
> install it, but run everything from the directory you built it in, use
> $export LD_LIBRARY_PATH=/path/to/wxlua/libs to force it to find the
> proper ones.
>

Well I don't have more than one version of Lua or wxWidgets installed. I
installed them directly form the apt repository in Ubuntu. I checked ldd and
did not find any .so that linked to anything outside the systems version of
Lua.  Could it be a difference because wxLua is bound to 2.8.10 and the
version I am building is using 2.8.11?

I also tried using the local only versions and it still segmentation faults.

So I did find out that if I use 'wxlua' to run the scripts everything works
fine. So it seems to be erroring out using the wxLua Lua module (wx.so) from
strait lua. Does that help at all? In fact, it is not the line of requiring
that seg faults, it is the first time you call into the library and display
a GUI element (like a wxMessageBox). Now if I pass the wrong parameters to a
function in wxLua it will give me the normal wxLua error message. It does
not actually seg fault on that. Does this help?
-- 
Regards,
Ryan

OOPS, forgot to reroute this email to the ML.

...
> > 1- If I only give a 1,000 length to the ListCtrl, the scroll bar won't
> >   reflect the real number of rows, which is visually perturbating and
> > leads to 2 questions:  
> 
> You're using wxListCtrl::InsertItem() ? This will automatically update
> the listctrl. Use wxWindow::Freeze() and Thaw() before and after,
> respectively, around your adding/deleting code to not have the GUI
> updated until you're done.  

Thanks, I didn't knew these.

> >   A- Shall I give the ListCtrl the real row Nb of the table|view or just
> >      1,000? (and, of course, destroying unused rows out of MyList),  
> 
> Whatever is appropriate for your number of items.
>   
> >   B- How can I detect the ListCtrl comes to an end/beginning?  
> 
> You probably can't.  

That is the heart of the PB (to have the LC behave almost "normally"; just
like if it was displaying a whole list.)

> >   C- Shall I use more than one MyList? (smaller)  
> 
> Probably, your GUI must be usable.  

I don't understand what you mean

> > 2- I would say that, except for the 1,000 of the beginning & end, I
> > should "center" the ListCtrl visible rows into MyList (to avoid too
> > much read if the user goes back & forth); but is it the right thing to
> > do?  
> 
> You need to break your list into smaller bits. Alphabetically?  

Not especially as a normal click on a column's header is supposed to
re-sort the items; thus, if column is different from the last one, 
I'll be obliged to re-query the DB in order to avoid inconsistencies 
in my list.

> > 3- What will happen if my row number goes beyond 2^31?  
> 
> This will make the scrollbar useless. You wouldn't be able to drag it
> even one pixel without skipping over many many items.  

Ok, I feared a loop to -1.

> >   This can happen because the ERP I'd like to build is based on my
> > former work (IT hardware sale) and each serialized item will have its
> > own row (in a large company, adding all these items on up to 2 years
> > warranty you can eventually cross this boundary.)  
> 
> I recommend showing 1000 or so items at a time and have buttons for
> going to the previous/next page, +/- 10 pages forward or back, and to
> the first/last page.  

THIS is precisely what I'd like to avoid: years ago, I used such a widget
in a Cial program and it was a PITA.
The few I learn about programming is to take the user's place, make it the
most intuitive, good-looking and pleasant to use (and lock anything else:)

Is there any other solution(s) to avoid that?

JY
-- 
* joeyh installs debian using only his big toe, for a change of pace
		-- in #debian-boot

On Tue, 23 Nov 2010 00:21:11 -0500, John Labenski <jla...@gm...>
wrote:

> > I've got a difference between a wxLua and python display aspect: an
> > empty LictCtrl has its columns headers displayed under python but not
> > under wxLua, is this normal?
> 
> Perhaps, different versions of wxWidgets may behave a little
> differently, unless you compiled them both yourself. I assume that
> once the wxListCtrl is populated it works as expected?

Yep, sorry for the noise
 
> > In a wxLua frame, I've got some 'SetToolTip' (linked to buttons) but
> > they don't show up when the mouse' hover the corresponding widget, what
> > is missing?
> 
> What system is this on, where did you get wxLua, compile it yourself,
> etc? There was a bug in wxWidgets where the tooltips weren't shown,
> but it is fixed now.

I'm gonna recompile it and retry, thanks (BTW: it is on Linux Debian sid,
and I compiled wxLua myself)

-- 
* Overfiend prefers girls who have developed, and DON'T FUCKING **GIGGLE**

On Sat, Oct 23, 2010 at 12:37 PM, Jean-Yves F. Barbier <12...@gm...> wrote:
> Hi list,
>
> I've got a difference between a wxLua and python display aspect: an empty
> LictCtrl has its columns headers displayed under python but not under
> wxLua, is this normal?

Perhaps, different versions of wxWidgets may behave a little
differently, unless you compiled them both yourself. I assume that
once the wxListCtrl is populated it works as expected?

> In a wxLua frame, I've got some 'SetToolTip' (linked to buttons) but they
> don't show up when the mouse' hover the corresponding widget, what is
> missing?

What system is this on, where did you get wxLua, compile it yourself,
etc? There was a bug in wxWidgets where the tooltips weren't shown,
but it is fixed now.

Regards,
    John

> On Wed, Nov 3, 2010 at 1:02 PM, Ryan Pusztai <rpu...@gm...> wrote:
>>
>> Hi,
>>
>> I have downloaded the latest release of wxLua and built it using the
>> documented method from the wxLua website (./configure, make, sudo make
>> install). After I 'sudo make install' and I try to just simply 'require(
>> "wx" )' and call wx.wxMessageBox("Hello") I get a Segmentation fault. It is
>> building wxLua v2.8.10 with wxWidgets version 2.8.11. Any thoughts?
>> Terminal output:
>>   $ lua
>>   Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
>>   > require( "wx" )
>>   > wx.wxMessageBox("hi")
>>   Segmentation fault
>
> Any ideas about this? I sent it quite a while ago and not sure if anyone has
> an idea. Thanks.

Sorry no ideas. I would guess that you have mismatched versions of
Lua. Maybe you have a system Lua installed or two versions of
wxWidgets on your system? I would try running ldd on the wxlua libs
and make sure that everything is in order. You can also try to execute
the program using the lua executable that wxLua compiles, i.e. don't
install it, but run everything from the directory you built it in, use
$export LD_LIBRARY_PATH=/path/to/wxlua/libs to force it to find the
proper ones.

Regards,
    John

On Sat, Nov 20, 2010 at 4:55 PM, Andre Arpin <ar...@ki...> wrote:
> The following modification allow wx.dll to work on window 7 / 64 bits.
> Without it you get a warning specifiying that comctl32.dll is not loaded.
> Why this suddenly happen is unknowned and will probably remain this way.
>
> // Override the base class virtual functions
> bool wxLuaModuleApp::OnInit()
> {
> #ifdef __WXMSW__
>        wxDynamicLibrary comctl32(_T("comctl32.dll"), wxDL_NOW);
> #endif
>    return true;
> }

What compiler and version are you using?

Regards,
    John

Bugs item #3115785, was opened at 2010-11-22 14:06
Message generated for change (Tracker Item Submitted) made by andrearpin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3115785&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: Andre Arpin (andrearpin)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxluafreeze.cpp

Initial Comment:
In the function wxFindAppFullName
then line
fileName.SetExt("exe");
should read
fileName.SetExt(_T("exe"));


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3115785&group_id=140042

Bugs item #3115780, was opened at 2010-11-22 13:59
Message generated for change (Tracker Item Submitted) made by andrearpin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3115780&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: Interface (example)
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andre Arpin (andrearpin)
Assigned to: Nobody/Anonymous (nobody)
Summary: minor fix to editor.lua

Initial Comment:
A file with the first line starting with the character # will not compile (it will compile with luac and run with lua)
The following code added to the CompileFunction solves the problem
    local firstLine = editor:GetTextRange(0, editor:PositionFromLine(1))
    if string.sub(firstLine, 1,1) == '#' then
        editorText = '--' .. string.sub(editorText, #firstLine)
    end


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=745324&aid=3115780&group_id=140042

Hi

After restarting the chnage does not work you have to do it explicitly which 
is a bind. 

This is ridiculous and probably a bug in system 7.

// Override the base class virtual functions
bool wxLuaModuleApp::OnInit()
{
#ifdef __WXMSW__
    ::LoadLibrary(_T("comctl32.dll"));
#endif
    return true;
}

Andre

The following modification allow wx.dll to work on window 7 / 64 bits.
Without it you get a warning specifiying that comctl32.dll is not loaded.
Why this suddenly happen is unknowned and will probably remain this way.

// Override the base class virtual functions
bool wxLuaModuleApp::OnInit()
{
#ifdef __WXMSW__
	wxDynamicLibrary comctl32(_T("comctl32.dll"), wxDL_NOW);
#endif
    return true;
}

Andre

---------- Forwarded message ----------
From: starwing <wea...@gm...>
Date: 2010/11/19
Subject: wxLua crashes when mouse hover on the frame window :-(
To: lua-l <lu...@li...>


the same dll file, and the same script, but my wxlua program crashes when
the mouse hover on the *any* window that shows on screen :-(.

but the script acts great on other guys computer.

hope anybody knows how this happened...  I use Windows XP and Lua For
WIndows 5.1..

btw, how to debug thus crash in windows?

the script:

require "wx"

frame = nil
function main()
    frame = wx.wxFrame( wx.NULL, wx.wxID_ANY, "wxLua",
                        wx.wxDefaultPosition, wx.wxSize(450, 450),
                        wx.wxDEFAULT_FRAME_STYLE )

    panel = wx.wxPanel(frame, wx.wxID_ANY)
    frame:Show(true)
end

main()

wx.wxGetApp():MainLoop()

On Wed, Nov 3, 2010 at 1:02 PM, Ryan Pusztai <rpu...@gm...> wrote:

> Hi,
>
> I have downloaded the latest release of wxLua and built it using the
> documented method from the wxLua website (./configure, make, sudo make
> install). After I 'sudo make install' and I try to just simply 'require(
> "wx" )' and call wx.wxMessageBox("Hello") I get a Segmentation fault. It is
> building wxLua v2.8.10 with wxWidgets version 2.8.11. Any thoughts?
>
> Terminal output:
>   $ lua
>   Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
>   > require( "wx" )
>   > wx.wxMessageBox("hi")
>   Segmentation fault
>

Any ideas about this? I sent it quite a while ago and not sure if anyone has
an idea. Thanks.
-- 
Regards,
Ryan

On Sun, 7 Nov 2010 18:16:57 -0500, John Labenski <jla...@gm...>
wrote:



> On Fri, Nov 5, 2010 at 8:18 PM, Jean-Yves F. Barbier <12...@gm...>
> wrote:
> > Hi list,
> >
> > I just discovered that SetItemCount doesn't exist into a LC, what
> > should I use, knowing I'm building a LC with a virtual list?
> 
> Unfortunately wxLua doesn't currently support virtual list controls
> right now. Is it possible to break your data into smaller chunks that
> that control could manage itself? or maybe use the wxGrid control?

Arrrgghhhh, I was suspected such an issue :(

I intended to use it to present db data in a tabular manner (I could break
data in chunk, but I'm quite sure users would be upset if the scroll button
don't reflect row number.)

I don't know very much wxGrid, does it have a functional virtual list
system and is it able to just allow line selection instead of cell?

JY
-- 
Man that scratch his butt at night awake with sticking fingers - Unkown

On Fri, Nov 5, 2010 at 8:18 PM, Jean-Yves F. Barbier <12...@gm...> wrote:
> Hi list,
>
> I just discovered that SetItemCount doesn't exist into a LC, what should I
> use, knowing I'm building a LC with a virtual list?

Unfortunately wxLua doesn't currently support virtual list controls
right now. Is it possible to break your data into smaller chunks that
that control could manage itself? or maybe use the wxGrid control?

Regards,
    John

Hi list,

I just discovered that SetItemCount doesn't exist into a LC, what should I
use, knowing I'm building a LC with a virtual list?

JY
-- 
A man who cannot seduce men cannot save them either.
		-- Soren Kierkegaard

On 4 November 2010 16:45, John Labenski <jla...@gm...> wrote:
>
> On Thu, Nov 4, 2010 at 10:41 AM, Eric Rosenquist <er...@ro...> wrote:
> > Has anyone succeeded in building wxLua if wxWidgets has been built with
> > --disable-gui?
>
> I have not tried that and it's not really supported since there would
> have to be quite a bit of extra logic to detect that and not build and
> link to the GUI bindings, which are most of them. In the worst case
> you can simply compile it with the GUI and simply not use those
> functions.

That works OK on a platform like Windows where you've always got the
GUI APIs present, but on *nix it causes your application to have
dependencies on the X11 and GTK shared libraries (assuming you build
wxWidgets for GTK). That's a problem since a lot of
Linux/Solaris/AIX/HP-UX/etc. admins don't want any GUI libraries
installed.

> You may have better luck modifying the Makefiles located in the src/
> dirs. I assume that you want the loadable wxlua module? You can also
> use wxLuaFreeze since that doesn't have a GUI either and can be used
> as a replacement for the Lua executable. You will have to hack away at
> these Makefiles and perhaps modify the
> wxLua/build/Makefile_wx-config.* files too.

I don't need the loadable wxlua module or wxLuaFreeze - all I really
need is wxLuaState plus the compile and run-time stuff that supports
the nice C++ binding generator. I've got a wxWidgets console app that
embeds a Lua interpreter for extensions/scripting, and those wxLua
items greatly simplify code vs. the plain old Lua C interface. In a
pinch that's what I'll have to fall back to, but I'll take a look at
the Makefiles and see if I can figure out a way to make it work.

I wanted to check with the mailing list first to see if anyone else
had been down that road just in case it's a waste of time :-)

On Thu, Nov 4, 2010 at 10:41 AM, Eric Rosenquist <er...@ro...> wrote:
> Has anyone succeeded in building wxLua if wxWidgets has been built with
> --disable-gui?

I have not tried that and it's not really supported since there would
have to be quite a bit of extra logic to detect that and not build and
link to the GUI bindings, which are most of them. In the worst case
you can simply compile it with the GUI and simply not use those
functions.

> The wxLua build doesn't get past the "configure" stage since configure tries
> to determine which wxWidgets port is in use and fails. The command
> "wx-config --selected-config" returns "base-ansi-release-2.8", which doesn't
> match any of the configurations that it checks for, so it bails with an
> error message:
>
> ...
> checking for wx-config... /home/.../bin/wx-config
>
> I'd like to be able to build and use wxLua with a non-GUI wxWidgets app,
> mainly to take advantage of the binding generator in wxLua since obviously
> I'm not using any of the GUI capabilities.

You may have better luck modifying the Makefiles located in the src/
dirs. I assume that you want the loadable wxlua module? You can also
use wxLuaFreeze since that doesn't have a GUI either and can be used
as a replacement for the Lua executable. You will have to hack away at
these Makefiles and perhaps modify the
wxLua/build/Makefile_wx-config.* files too.

Regards,
    John

Has anyone succeeded in building wxLua if wxWidgets has been built with
--disable-gui?

The wxLua build doesn't get past the "configure" stage since configure tries
to determine which wxWidgets port is in use and fails. The command
"wx-config --selected-config" returns "base-ansi-release-2.8", which doesn't
match any of the configurations that it checks for, so it bails with an
error message:

...
checking for wx-config... /home/.../bin/wx-config
checking for wxWidgets version >= 2.8.0... yes (version 2.8.11)
checking for wxWidgets static library... no
checking if wxWidgets was built with UNICODE enabled... no
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... no
checking which wxWidgets toolkit was selected... configure: error:
        Cannot detect the currently installed wxWidgets port !
        Please check your 'wx-config --cxxflags'...


I'd like to be able to build and use wxLua with a non-GUI wxWidgets app,
mainly to take advantage of the binding generator in wxLua since obviously
I'm not using any of the GUI capabilities.

Thanks in advance for any ideas,
Eric