wxlua-users Mailing List for wxLua

Hi all!

I am using a wxListCtrl in my application, and I have some problems on *nix.


When I set wxLC_SORT_ASCENDING to it's properties, it'll sort nicely the
items on Windows, when I push the element to the 0. position. But, on Unix,
it'll appear on the 0. position. Is there any way to make it similar as it
is on Win?

Thanks:

Attila Pázmándi

On Thu, Jun 19, 2008 at 9:37 AM, Matthieu Caron
<car...@gm...> wrote:
> Hi everyone !!
>
> Did someone already used wxPropertyGrid with wxLua?
> Correct me if I'm wrong, but I think that the binding for this control
> doesn't exists...
>
> Does someone has an idea on how I could use it with Lua? Does someone who
> has done the binding could eventually share it?
>

Sorry, I don't think that anyone has wrapped it yet.

Regards,
    John

Hi everyone !!

Did someone already used wxPropertyGrid with wxLua?
Correct me if I'm wrong, but I think that the binding for this control
doesn't exists...

Does someone has an idea on how I could use it with Lua? Does someone who
has done the binding could eventually share it?


Thank you in advance :-)

Regards,
Matthieu

More thoughts:
* Looking at the LSV files, I understand that what is stored is more
or less the whole area of the worksheet. My suggestion would be to
store only those cells which are not empty; and do that for example by
storing columns, then in each column only those ranges of cells which
compose just of non-empty cells. Or something else, that's just my
suggestion. And I understand you might have wanted just to do it the
simplest way for start :)
* one small "bug report": on my Windows, the status bar does not show
the value of a cell, as is suggested by the screenshot.

But then, this list is probably not the best place for bugreports etc.
Do you use the SF.net ticket tracking system for your project?

greetz
Mateusz Czaplinski

On 6/17/08, Mateusz Czaplinski <cza...@gm...> wrote:
> ah, one small thing as for now: you should probably update the SVN
> checkout instructions on the webpage according to the new SVN access
> scheme on SF.net - that is, URL should be:
>   https://luacalc.svn.sourceforge.net/svnroot/luacalc
> You might also want to add the information about downloading from the
> "Experimental" directory there. And I think that setting up the
> classical trunk-branches-tags structure might not be a bad idea -
> that's probably what you meant as "cleaning up"? :)
>
> greetz
> Mateusz Czaplinski
>

ah, one small thing as for now: you should probably update the SVN
checkout instructions on the webpage according to the new SVN access
scheme on SF.net - that is, URL should be:
  https://luacalc.svn.sourceforge.net/svnroot/luacalc
You might also want to add the information about downloading from the
"Experimental" directory there. And I think that setting up the
classical trunk-branches-tags structure might not be a bad idea -
that's probably what you meant as "cleaning up"? :)

greetz
Mateusz Czaplinski

On 4/18/08, LuaCalc Dev <tec...@ya...> wrote:
> As a great fan of lua ( and wx of course ), i joined a wxlua based project.
>
> It's called luacalc and is hosted on sourceforge.
>
> Basically luacalc is an interface between a (excel alike) sheet and wx.
[...]
> Try it,any suggestions are welcome.(even negative as long as they can be
> used in
> a positive way).
[...]
> Thank you for your time.
>
> The Luacalc dev team.

Heh, how cool - I've just thought about something similar a day or two
ago :) and then what - I look into my mail - and voila! :)))
I must get it immediately and play for a moment :)

see you, and keep up funny work :)
Mateusz Czaplinski

On 5/13/08, John Labenski <jla...@gm...> wrote:
> On Thu, May 8, 2008 at 5:30 PM, Mateusz Czaplinski <cza...@gm...>
> wrote:
>> I'm trying to play with wxSocket, but have strange results. The
>>  fragment of code which I attached works perfectly well when run from
>>  wxluaedit.exe (2.8.7.0-MSW-bin) but hangs after displaying the first
>>  message ("connect: true") when run from any other tool (wxlua,
>>  wxluafreeze, also embedded using wxluafreeze).
>
> That is strange, what happens if you add a menu item (see minimal
> sample or even a button) so that you have to click it before
> connecting? I just tried it in Linux and you code works fine for all
> three programs. Maybe it's a MSW thing with initializing?
>
> wxLua and wxLuaFreeze, like typical C++ apps, run the Lua code to
> create the GUI in the wxApp::OnInit() function which is called before
> the mainloop is run. I wonder if this is why wxSocket works in
> wxLuaEdit and not the others.
>
> Let me know

You're right, it worked when made to run from an event handler of a
button - thanks a lot! It appears it never occured to me to think
about when the Lua code is actually run... and what you write about
that sounds possible, so maybe my problem was because some things in
Wx were not properly initialized yet during this OnInit() method.
And then, if I still want to connect immediately after starting the
program, I suppose I should probably look for some timer or something
similar (sounding like SwingUtils.invokeLater() ;)

thanks very much again! and sorry for my response being so late.
greetings
Mateusz Czaplinski

PS. Ah, I've also attached the file after applying the changes you
described; who knows, it may even help someone else in a similar
situation in future
greetz - MC

On Wed, Jun 4, 2008 at 5:58 PM, Eero Pajarre <epa...@gm...> wrote:
>
> I will let you know when I find out what was the problem.
>

(I promised to tell, so here it comes)

Actually I lied earlier, but I didn't do it on purpose...

I said that I had changed my code to look like the
code from Piotr. Actually my code looked like this:

local tim=wx.wxTimer(frame);
frame:Connect(wx.wxEVT_TIMER,
	      Tick);

tim:Start(200);

And the problem is.... the word "local".

When the code file is executed if the
timer is not stored somewhere (like the globals
table) it can be garbage collected.

The difference between my application and the
official wxLua application was that my application
calls lua_gc after executing the lua file, and thus
triggers the problem immediately. with wxLua
the problem just remains hidden (for a while).


  Eero

On Wed, Jun 4, 2008 at 5:58 PM, Eero Pajarre <epa...@gm...> wrote:
>
> I will let you know when I find out what was the problem.
>

(I promised to tell, so here it comes)

Actually I lied earlier, but I didn't do it on purpose...

I said that I had changed my code to look like the
code from Piotr. Actually my code looked like this:

local tim=wx.wxTimer(frame);
frame:Connect(wx.wxEVT_TIMER,
	      Tick);

tim:Start(200);

And the problem is.... the word "local".

When the code file is executed if the
timer is not stored somewhere (like the globals
table) it can be garbage collected.

The difference between my application and the
official wxLua application was that my application
calls lua_gc after executing the lua file, and thus
triggers the problem immediately. with wxLua
the problem just remains hidden (for a while).


  Eero

Hi all, I have a problem again :)

Previously John helped me find out what was wrong - the secondary thread  
wanted to access the GUI, which is forbidden under GTK. So I've rewritten  
my application, now it works on both OS, just I have a problem again.  
Exactly two.
1. The application is _very_ slow now
2. In this way, the program isn't punctual

This application uses luasocket, and reads the data from there, then it  
parses it, and adds some data to a ListCtrl. But. If I except (and get)  
500 lines on the socket, just about 200 appears in the list. I tried both  
wx.wxPostEvent() and MyApp:AddPendingEvent(), the result is the same. I  
made some debugs too, and I saw the data on the socket, but not on the  
connected function...

So, I've decided to check wxWidgets manual, maybe it has some tricks to  
fix this problem. I find a 'function(?)', called wxMutexGuiEnter() and  
wxMutexGuiLeave(), which provides the possibility to modify the GUI from  
the secondary threads. The only problem that wxLUA doesn't wrap wxThread.

My question(s):
- Will be that wrapped in the closer-future?
- Is there any other way to reach the GUI w/o any data get lost and the  
GUI itself freeze?

Thanks for the replyes:
Attila Pázmándi

On Wed, Jun 4, 2008 at 5:47 PM, John Labenski <jla...@gm...> wrote:
>
> I don't know how "old" your version is, but if it's more than a year
> old, the implementation is actually quite different. If I were you, I
> would upgrade it since the Lua code has changed very little, but the
> internal C/C++ has changed a lot, hopefully for the better.

I seem to have some code lines from year 2002 ....
Here I mean my wxLuaStandaloneApp code parts, for wxLua
I am using rather recent version from CVS.

Of course I must have updated my code a lot, otherwise it would not
even compile with the current wxLua.

I will let you know when I find out what was the problem.

   Eero

On Wed, Jun 4, 2008 at 5:50 AM, Eero Pajarre <epa...@gm...> wrote:
> On Wed, Jun 4, 2008 at 12:29 PM, Eero Pajarre <epa...@gm...> wrote:
>
>>
>> I have to do some more tests, my wxLua base application is not
>> from the current wxLua distribution (instead it was originally
>> based on version from long time ago, and I have updated it
>> where I have noticed it necessary).
>>
>
> Ok, thanks for you help Piotr.
>
> It looks like the problem is specific to my wxLua based application,
> now I just have to find out what is wrong there. :-(  On the first look
> I did not notice "essential" differences, when comparing the the
> current official wxLua.

I don't know how "old" your version is, but if it's more than a year
old, the implementation is actually quite different. If I were you, I
would upgrade it since the Lua code has changed very little, but the
internal C/C++ has changed a lot, hopefully for the better.

Regards,
    John

On Wed, Jun 4, 2008 at 12:29 PM, Eero Pajarre <epa...@gm...> wrote:

>
> I have to do some more tests, my wxLua base application is not
> from the current wxLua distribution (instead it was originally
> based on version from long time ago, and I have updated it
> where I have noticed it necessary).
>

Ok, thanks for you help Piotr.

It looks like the problem is specific to my wxLua based application,
now I just have to find out what is wrong there. :-(  On the first look
I did not notice "essential" differences, when comparing the the
current official wxLua.

  Eero

On Wed, Jun 4, 2008 at 11:45 AM, Piotr Strzelczyk <pi...@ep...> wrote:
>
>> I still don't get my Tick function called...
>> (my timer seems to be ok, it returns correct value for
>> GetInterval and IsRunning.)
>>
> Strange, I have no problems with it.
> But I'll try to ask some silly questions which may help you:
> I what part of program timer should work? All events work when the
> program is in main loop (e.g. initialization is ended).
> Do you have multithread program (corutine)? Events has to be processed
> in `main' thread.
>

I start the timer while initializing, and my program "ends" into the main
loop, the GUI is otherwise active, so I the main loop must be running.
(This is for testing purposes, I added the timer stuff to an
existing application)

My Tick function currently just prints a message (which is redirected to
a texty box in application). The message appears if I directly call the tick
function, but not from the timer.

No coroutines.

I have to do some more tests, my wxLua base application is not
from the current wxLua distribution (instead it was originally
based on version from long time ago, and I have updated it
where I have noticed it necessary).


   Eero

> I still don't get my Tick function called...
> (my timer seems to be ok, it returns correct value for
> GetInterval and IsRunning.)
>   
Strange, I have no problems with it.
But I'll try to ask some silly questions which may help you:
I what part of program timer should work? All events work when the 
program is in main loop (e.g. initialization is ended).
Do you have multithread program (corutine)? Events has to be processed 
in `main' thread.

> Is your experience from Linux or Windows or some other platform?
I compiled/tested my project ( http://psview.sf.net/ ) under Linux (gcc) 
and Windows (mingw or VC++)
in both cases timer works fine.

Best regards

Piotr Strzelczyk

-- 
Piotr Strzelczyk
Sopot, Poland
e-mail: pi...@ep...; skype: piotrstrz

On Wed, Jun 4, 2008 at 12:18 AM, Piotr Strzelczyk <pi...@ep...> wrote:

> Maybe this fragments of code will be useful for you:
>
> gstimer = wx.wxTimer(frame)
> frame:Connect(wx.wxEVT_TIMER, TimerTick)
>
> gstimer:Start(20)
>

Thanks,

Your code wasn't much different from my experiment,
and I changed my version to match yours.

I still don't get my Tick function called...
(my timer seems to be ok, it returns correct value for
GetInterval and IsRunning.)

Is your experience from Linux or Windows or some other platform?

I am trying this on Windows (XP).


   Eero

On Thu, May 29, 2008 at 11:30 AM, Matthieu Caron
<car...@gm...> wrote:
> Hi everyone.
>
> I think my problem is really simple, but I need some help to understand how
> it works.
>
> I created a wxwidget project (wxApp) which display a Dialog window with a
> file picker to let the users select and load their own script. Then, I close
> the Dialog window and I run the script chosen thanks to the Runfile().
> Everything is Ok for this part. The Script works well and my frame coded in
> Lua appears.
>
> Then, when I want to finish my application, I click on the "close button" of
> my scripted frame. The frame desappears as well, but I still have a process
> running (the process of my wxApp) and I can't end it (no more wxFrame). The
> only solution is to "kill" the process with the task manager.
>
> I looked at the wxLua application in the sources, but I can't understand how
> the process wxApp is ended...

The wxApp class calls your wxApp::OnInit() which then calls
wxApp::MainLoop() where the program "hangs" in the event loop. By
default the mainloop will exit when there are no more top level
windows. Do you call  wxApp::SetExitOnFrameDelete(false)?

http://docs.wxwidgets.org/stable/wx_wxapp.html#wxappsetexitonframedelete

Since you show a dialog, close it, then run a program that presumedly
creates a new dialog/frame you may need to set
SetExitOnFrameDelete(false) then close the dialog, load the script,
set it back to true, and then run the script.

Hope this helps,
    John

On Fri, May 23, 2008 at 5:33 PM, Dennis Sacks <den...@gm...> wrote:
> I created an xrc file using wxFormBuilder and have been looking at
> calculator.wx.lua for guidance but I'm still struggling. :)
>
> I can load my frame and it displays, which made me very happy, but I am
> trying to access the menubar that is specified in my xrc file, and I'm not
> sure how to.
>
> I've tried frame:FindWindow(xmlResource.GetXRCID("mbMain")) as well as just
> frame:FindWindow("mbMain") but I am getting nil from both. mbMain is the
> name of the menubar - I've verified that.

The wxMenubar might not be searched by wxWindow::FindWindow() since
it's not really a window, but if you can get the frame then just call
frame:GetMenuBar().

Hope this helps,
    John

Hello,

> Has anybody used wxTimer in wxLua (lua-side) programming?

Yes, I've used it.

> I can create the wxTimer, but I am not sure what
> I am missing when I try to bind it to an event handler.

Maybe this fragments of code will be useful for you:

gstimer = wx.wxTimer(frame)
frame:Connect(wx.wxEVT_TIMER, TimerTick) 

gstimer:Start(20)

the TimerTick() function is called 50 times per second
(variable frame point main window of application).

near the end of program (or when needed) you should use:

gstimer:Stop()

Best regards

Piotr Strzelczyk

Has anybody used wxTimer in wxLua (lua-side) programming?
The only related example I found, was the wxluacan program,
and it seems to use timer events from the C/C++ side.

I can create the wxTimer, but I am not sure what
I am missing when I try to bind it to an event handler.



   Eero