wxlua-users Mailing List for wxLua

I hate to ask this because I am a developer of other open-source project and
know what a pain this type of question can introduce;

When are the build problems going to be fixed? I need to use wxLua in a
project but I can't build it because of the OpenGL dependency problem in the
BakeFiles. Any update, even if it is "go jump in a lake", is ok. I am just
trying to see if I need to find another solution for my project. Thanks so
much for all your effort.
-- 
Regards,
Ryan
RJP Computing

On 8/27/07, ah...@ar... <ah...@ar...> wrote:
> Hi!
>
> I have a program that uses wxLua by running the executable of
> wxLuaFreeze with a script as a parameter, like so:
>
> wxLuaFreeze.app/Contents/MacOS/wxluafreeze JOF.lua &> /dev/null &
>
> JOF.lua is, of course, the name of my script. In version 2.8.0.0 this
> worked fine, but in version 2.8.4.1 the application shows its main
> window, but it is not selectable (it wont get focus by cliking on it),
> and no icon is shown in the dock. If I run the wxLuaFreeze app by
> launching the bundle directly the icon of the app flashes in the dock
> before the app closes (almost immediately). But if I pass arguments to
> the program no icon is shown in the dock.
>
> Is there a problem with the new wxLuaFreeze or am I missing something?
> Also, is there a better way to pass args to wxLuaFreeze in OSX, than
> opening up the bundle and passing the args directly to the executable?

The problem with the program not accepting any input is a
"bug/feature" of OSX. This happens when you try to directly run an
executable. You need to run a program as a "bundle" with a specific
directory structure and a few extra files to help the OS do the right
thing.

Apparently there is some code you can stick into a programs
initialization to get around the need for the directory structure of
the bundle. I will look into that.

I can't test now, but on the command line I believe that you can run a
bundle (actually a directory) using the "open" command. I wonder if
that allows for command line args?

Hopefully Anders can shed some light on this.

Regards,
    John Labenski

T24gOC8yOC8wNywgyWpqZWxpINVyauFyYXQgPGVqamVsaW9yamFyYXRAZ21haWwuY29tPiB3cm90
ZToKPiBIaSBhbGwKPiBJIG5lZWQgc29tZSBoZWxwIHdpdGggaWNvbnM6IGhvdyB3eC53eEljb25C
dWRsZSgpIHdvcmtzPyBEb2VzIGl0IGFjY2VwdCBhCj4gZmlsZSBsaWtlIHRoaXM6IGh0dHA6Ly9k
Y3BwLmV4dHJhLmh1L3Rvb2xiYXIuYm1wIGFuZCBjYW4KPiBjdXQgdGhlIGVhY2ggaW1hZ2VzIGZy
b20gaXQ/IElmIHllcywgaG93PyAoSSB0cmllZCwgYnV0IG5vdCB3aXRoIHN1Y2Nlc3MuLgoKTm8s
IHRoZSB3eEljb25CdW5kbGUoKSBpcyBqdXN0IGZvciBhIDE2eDE2IGFuZCAzMngzMiBpY29uLCB0
eXBpY2FsbHkuCmh0dHA6Ly93d3cud3h3aWRnZXRzLm9yZy9tYW51YWxzL3N0YWJsZS93eF93eHRv
cGxldmVsd2luZG93Lmh0bWwjd3h0b3BsZXZlbHdpbmRvd3NldGljb25zCgpUbyBjdXQgb3V0IHRo
ZSBpbWFnZXMgeW91IHdvdWxkIGRvLiAodW50ZXN0ZWQgYW5kIHlvdSdkIHByb2JhYmx5IHVzZSBh
IGZvciBsb29wKQpiID0gd3gud3hCaXRtYXAoIm15aW1hZ2VzLnBuZyIpCmIxID0gYjpHZXRTdWJC
aXRtYXAod3gud3hSZWN0KDAsIDAsIDE2LCAxNikpCmljb24gPSB3eC53eEljb24oKTsgaWNvbjpD
b3B5RnJvbUJpdG1hcChiMSkKLi4uCgotLSBJZiB5b3Ugd29uJ3QgdXNlIHRoZXNlIGFnYWluIGFu
ZCB3aWxsIGdlbmVyYXRlIGEgbG90IG9mIHRoZW0sIGRlbGV0ZSB0aGVtCmljb246ZGVsZXRlKCkK
YjE6ZGVsZXRlKCkKYjpkZWxldGUoKQoKPiA6LS8pIEFuZCBhbiBhbm90aGVyIHF1ZXN0aW9uOiBp
cyBzb21ld2hlcmUgYSBob21lcGFnZSB3aGVyZSBjYW4gSSBmaW5kCj4gYXBwbGljYXRpb25zLCB3
cml0dGVuIGluIHd4TFVBPyBNYW55IHRpbWVzIEkgbmVlZCBzb21lIGlkZWEgYW5kIHN1Z2dlc3Rp
b24sCj4gYW5kIHRoZSBzYW1wbGUgaXMgdG9vIGZldyBmb3IgaXQuLi4gVGhhbmtzIHRoZSBhbnN3
ZXJzLgoKU29ycnksIG5vbmUgdGhhdCBJIGtub3cgb2YuIEhvcGVmdWxseSBzb21lIG90aGVycyB3
aWxsIHB1dCB0aGVtIG9uIHRoZQp3ZWIgZXZlbnR1YWxseS4KClJlZ2FyZHMsCiAgICBKb2huIExh
YmVuc2tpCg==

Hi all
I need some help with icons: how wx.wxIconBudle() works? Does it accept a
file like this: http://dcpp.extra.hu/toolbar.bmp and can cut the each images
from it? If yes, how? (I tried, but not with success.. :-/) And an another
question: is somewhere a homepage where can I find applications, written in
wxLUA? Many times I need some idea and suggestion, and the sample is too few
for it... Thanks the answers.

Hi!

I have a program that uses wxLua by running the executable of =20
wxLuaFreeze with a script as a parameter, like so:

wxLuaFreeze.app/Contents/MacOS/wxluafreeze JOF.lua &> /dev/null &

JOF.lua is, of course, the name of my script. In version 2.8.0.0 this =20
worked fine, but in version 2.8.4.1 the application shows its main =20
window, but it is not selectable (it wont get focus by cliking on it), =20
and no icon is shown in the dock. If I run the wxLuaFreeze app by =20
launching the bundle directly the icon of the app flashes in the dock =20
before the app closes (almost immediately). But if I pass arguments to =20
the program no icon is shown in the dock.

Is there a problem with the new wxLuaFreeze or am I missing something? =20
Also, is there a better way to pass args to wxLuaFreeze in OSX, than =20
opening up the bundle and passing the args directly to the executable?

Sebastian Ahlman

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

John Labenski <jlabenski@...> writes:

> 
> No, we use a version modified by Francesco. You can get it here.
> 
> http://wxlua.sourceforge.net/bakefile/
> 

Thank you it works

for any who want to know out to it here a simple recipe:

install version 0.2.2 of bakefile
untar Francesco version into the default directory (frm-bakefile)
rename frm-bakefile directory to Bakefile
copy this directory over Bakefile directory (drag and drop)
change to wxLua\build\bakefiles director 
run: bakefile_gen

ps: You could also copy without renaming but this is really simple
ps: This generates all the files using a parm to limit generation would speeds 
things up

On 8/24/07, Mario <ma...@ya...> wrote:
> I'd like to stop the execution of my program for some seconds, allowing
> the user to read a message.
> If nothing happens during this time, the program just waits n seconds
> and then goes on, but if the user want to speed things, he may just
> touch a key or move the mouse.
>
> Is it possible to do this with wxLua ?
>
> I found the function wxSleep()
> It stops the program execution, "Sleeps", for the specified number of
> seconds.
> But you cannot speed things by touching a key or the mouse.

Here's a few code snippits that should get you on the right path. I
don't believe that ShowModal() will work since that usually means that
a new event loop is created, but you should try it. You may also
simulate the behavior below using a wxTimer, which is probably a
better way.

tracker_var = false
MyDialog = wx.wxDialog(...)
myDialog:Connect(ID_OK, wx.wxEVT_LEFT_DOWN,
    function(event) tracker_var = true end)
myDialog:Show()

for i = 1, 20 do
    wx.wxMilliSleep(500)
    wx.wxYield()
    if tracker_var == true then break end
end

dialog:Destroy()

Hope this helps,
    John Labenski

On 8/24/07, Andre Arpin <ar...@ki...> wrote:
> I just try bakefile_gen on window and it does not work.
> Is the standard version 0.2.2 expected to work?
>

No, we use a version modified by Francesco. You can get it here.

http://wxlua.sourceforge.net/bakefile/

John Labenski

I'd like to stop the execution of my program for some seconds, allowing 
the user to read a message.
If nothing happens during this time, the program just waits n seconds 
and then goes on, but if the user want to speed things, he may just 
touch a key or move the mouse.

Is it possible to do this with wxLua ?

I found the function wxSleep()
It stops the program execution, "Sleeps", for the specified number of 
seconds.
But you cannot speed things by touching a key or the mouse.

Can you help me ?
Thanks,

Mario

I just try bakefile_gen on window and it does not work.
Is the standard version 0.2.2 expected to work?

Andre

John Labenski wrote:

>> I could try the bleeding edge wxwidgets and wxstedit, of course.
>> But I would prefer if it worked OK with 2.8.4 and 1.2.5 as well.
>
> Ok, I have been using the svn of wxWidgets 2.8 since it seems like OSX
> is still being worked on quite a bit.

Sure, but both wxWidgets 2.6.4 and 2.8.4 are fully operational...

>> What I have done is taken the "wxLua" directory, and then added the
>> binaries to "apps" and "bin" by combining the PPC and X86 builds...
>
> I saw that, but didn't have time to understand how or where you put
> the "magic" files/dirs to make it work in OSX. By magic, I mean the
> ones that allow the program to work and not ignore the keyboard and
> mouse input, i.e. what happens if you compile a binary and try to run
> that all by itself without the extras. I'll look into that when I get
> back.

There is a system call* that you can do on start, so Mac OS X notices
that a Carbon program is running. wxWidgets has chosen not to call this,
which means that you either need to add a resource fork or bundle up 
your
application before it will receive any events (second choice suggested)

So as long as you run the bundle, it should be OK. The script called
"copydylibs" includes a copy of all the dynamic libraries and repoints
the "install_name" of the apps to point to them (compare with rpath),
but that's optional and it is _not_ used by the MacPorts port/package.

> I think it may also be nice to make it easy to pull out wxLuaFreeze
> since that's supposed to be the "lean" wxLua executable that you can
> use to run your own programs. The "freezing" part isn't too great
> since it only works on a single file, but I've been meaning to write
> in the docs/FAQ that people with multiple lua parts should feel
> welcome to rename wxLuaFreeze to the name of their program and create
> a script to run it as "MySuperProgram mysuperprogram.wx.lua" Anyway,
> if wxLuaFreeze was a separate dir in the mac binary they could just
> copy it, rename it, add their lua scripts and done - they've got a
> "binary". Or, am I missing something.

Well, I just packaged what it built and didn't remove anything :-)

According to wxWidgets practices, wxLuaFreeze on Mac OS X either
needs to add a resource fork or build a bundle directory instead.
Considering as how the resource fork normally ends up in a separate
file called "._foo" (for file "foo"), there are *no* one-file exes...

I guess it could be educated to build a Mac OS X disk image, but.

>> Think "About" has a similar issue, it's also moved away from Help ?
>
> Oops, yeah I meant wxID_ABOUT. I tried a whole bunch of combinations
> of having >1 items in the help menu (containing wxID_ABOUT), adding
> items later, adding a whole new menu (Help2) and adding items, but in
> every case there was something funny about it. It seemed like the menu
> with wxID_ABOUT in it was hidden even for multiple items and adding a
> menu or menuitem after setting the menu to the frame caused problems.
> I think the worst case was adding a whole extra menu (Help2) which
> caused the handler function to be called multiple times. I'll have to
> revisit that since I just don't remember anymore.

I think the menu briefly disappears (since there are no items), and
then it suddenly remembers it and it reappears when you mouse over it.

Either way it looks funny. But "About" does belong in the app menu...
That it is hidden when it had more than one sounds like a bug, though.

--anders

* http://article.gmane.org/gmane.comp.lib.wxwidgets.devel/83092

On 8/24/07, Anders F Bj=F6rklund <af...@al...> wrote:
>
> I have re-uploaded it, so it should be there again now. (15.87 MB)

Thanks, I posted it.

> >> It seems that wxLuaEdit is crashing on start, will see if it needs a
> >> rewrite or if I missed a patch from the previous Mac build (2.8.0.0)
> >> There is a version of wxlua/wxstedit in MacPorts, if I ever get around
> >> to cleaning it up and submitting (I'm the maintainer for those too...)
> >
> > I have also been able to build this too and I don't get a crash. Could
> > you try the CVS version of wxStEdit? Either that or the problem is
> > with the default fonts in OSX, there was a problem with a recursion
> > between the OSX platform specific function and the common one in
> > wxSystemSettings, but that was fixed a while ago I thought. I use the
> > SVN wxWidgets from the 2.8 branch so it might be fixed there.
>
> It worked OK with wxLua 2.8.4.0 and wxStEdit 1.2.5, so I think the
> problem lies in wxLua - but I haven't pinpointed it down just yet...

Ut oh. I'll look into to when I get back as well.

> > svn checkout
> > http://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH
> > wxWidgets-2.8
> >
> > cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxcode
> > co -P wxCode/components/wxstedit
>
> I could try the bleeding edge wxwidgets and wxstedit, of course.
> But I would prefer if it worked OK with 2.8.4 and 1.2.5 as well.

Ok, I have been using the svn of wxWidgets 2.8 since it seems like OSX
is still being worked on quite a bit.

> > I'm still unsure how to package it the binaries though. So far I've
> > been building and copying the wxWidgets minimal sample's package for
> > my personal testing.
>
> What I have done is taken the "wxLua" directory, and then added the
> binaries to "apps" and "bin" by combining the PPC and X86 builds...

I saw that, but didn't have time to understand how or where you put
the "magic" files/dirs to make it work in OSX. By magic, I mean the
ones that allow the program to work and not ignore the keyboard and
mouse input, i.e. what happens if you compile a binary and try to run
that all by itself without the extras. I'll look into that when I get
back.

I think it may also be nice to make it easy to pull out wxLuaFreeze
since that's supposed to be the "lean" wxLua executable that you can
use to run your own programs. The "freezing" part isn't too great
since it only works on a single file, but I've been meaning to write
in the docs/FAQ that people with multiple lua parts should feel
welcome to rename wxLuaFreeze to the name of their program and create
a script to run it as "MySuperProgram mysuperprogram.wx.lua" Anyway,
if wxLuaFreeze was a separate dir in the mac binary they could just
copy it, rename it, add their lua scripts and done - they've got a
"binary". Or, am I missing something.

> Additionally, I have added the "wxLua" port to MacPorts now so one
> should be able to install all of it by doing "port install wxLua"

Great.

> > There is one problem with wxStEdit however, the help menu item is
> > messed up since wxWidgets tries to move the wxID_HELP item over to the
> > system menu. When I try to add new items in the sample program
> > samples/stedit/wxstedit.cpp they're not shown. I forget the state of
> > how I left it though and can't check now.
>
> Think "About" has a similar issue, it's also moved away from Help ?

Oops, yeah I meant wxID_ABOUT. I tried a whole bunch of combinations
of having >1 items in the help menu (containing wxID_ABOUT), adding
items later, adding a whole new menu (Help2) and adding items, but in
every case there was something funny about it. It seemed like the menu
with wxID_ABOUT in it was hidden even for multiple items and adding a
menu or menuitem after setting the menu to the frame caused problems.
I think the worst case was adding a whole extra menu (Help2) which
caused the handler function to be called multiple times. I'll have to
revisit that since I just don't remember anymore.

> > That's great. Could we go over this in a week when I get back and we
> > can flesh out once and for all what is needed for OSX to work out of
> > the box. I'd really like to learn once and for all how to do it, but
> > since compiling on my old Emac takes at least an hour, I've been
> > putting it off.
>
> Sure, not a problem. If I have anything before then, I'll send patches.

Thanks.
    John Labenski

John Labenski wrote:

>> I made a Mac build of wxLua-2.8.4.1 meanwhile, until the sources are
>> out.
>> I uploaded it to SourceForge's "incoming" area, as
>> wxlua-2.8.4.1-tiger.dmg
>
> I'm sorry that I missed this and SF has already deleted it. Could you
> upload it again and I'll post it at sourceforge. I'll be away at a
> conference this coming week, but I should have internet access.

I have re-uploaded it, so it should be there again now. (15.87 MB)

>> It seems that wxLuaEdit is crashing on start, will see if it needs a
>> rewrite or if I missed a patch from the previous Mac build (2.8.0.0)
>> There is a version of wxlua/wxstedit in MacPorts, if I ever get around
>> to cleaning it up and submitting (I'm the maintainer for those too...)
>
> I have also been able to build this too and I don't get a crash. Could
> you try the CVS version of wxStEdit? Either that or the problem is
> with the default fonts in OSX, there was a problem with a recursion
> between the OSX platform specific function and the common one in
> wxSystemSettings, but that was fixed a while ago I thought. I use the
> SVN wxWidgets from the 2.8 branch so it might be fixed there.

It worked OK with wxLua 2.8.4.0 and wxStEdit 1.2.5, so I think the
problem lies in wxLua - but I haven't pinpointed it down just yet...

> svn checkout 
> http://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRANCH
> wxWidgets-2.8
>
> cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxcode
> co -P wxCode/components/wxstedit

I could try the bleeding edge wxwidgets and wxstedit, of course.
But I would prefer if it worked OK with 2.8.4 and 1.2.5 as well.

> I'm still unsure how to package it the binaries though. So far I've
> been building and copying the wxWidgets minimal sample's package for
> my personal testing.

What I have done is taken the "wxLua" directory, and then added the
binaries to "apps" and "bin" by combining the PPC and X86 builds...

Additionally, I have added the "wxLua" port to MacPorts now so one
should be able to install all of it by doing "port install wxLua"

> There is one problem with wxStEdit however, the help menu item is
> messed up since wxWidgets tries to move the wxID_HELP item over to the
> system menu. When I try to add new items in the sample program
> samples/stedit/wxstedit.cpp they're not shown. I forget the state of
> how I left it though and can't check now.

Think "About" has a similar issue, it's also moved away from Help ?

>> I used wxWidgets 2.8.4 (UNICODE/RELEASE) and wxStEdit 1.2.5, by the 
>> way.
>> It has been compiled as a Universal Binary, i.e. both PowerPC and 
>> Intel.
>
> That's great. Could we go over this in a week when I get back and we
> can flesh out once and for all what is needed for OSX to work out of
> the box. I'd really like to learn once and for all how to do it, but
> since compiling on my old Emac takes at least an hour, I've been
> putting it off.

Sure, not a problem. If I have anything before then, I'll send patches.

--anders, http://sourceforge.net/users/afb

On 8/23/07, Anders F Bj=F6rklund <af...@al...> wrote:
> John Labenski wrote:
>
> > MSW Binary only release for now since the build files do not account
> > for the options to build the wxWidgets binding libs and which ones to
> > link to. Hopefully this will be fixed soon and the source code and (if
> > we're lucky) an OSX binary release will be made too.

Still no success with this, we'll have to get Francesco to help.

> I made a Mac build of wxLua-2.8.4.1 meanwhile, until the sources are
> out.
> I uploaded it to SourceForge's "incoming" area, as
> wxlua-2.8.4.1-tiger.dmg

I'm sorry that I missed this and SF has already deleted it. Could you
upload it again and I'll post it at sourceforge. I'll be away at a
conference this coming week, but I should have internet access.

> Here are the issues that I had to patch, before it would build/compile:
> http://www.algonet.se/~afb/wx/wxlua-macconfigure.patch ("DEBUG=3D0")
> http://www.algonet.se/~afb/wx/wxlua-macnorpath.patch ("-Wl,-rpath,")
> http://www.algonet.se/~afb/wx/wxlua-macglcontext.patch ("SetCurrent")
> Will see if I can re-generate real fixes, against the wxLua CVS...

I have built wxLua 2.8.4.2 on my Mac, after disabling gl in wxWidgets
(--with-opengl=3Dno if I remember correctly) and setting
"wxLUA_USE_wxGLCanvas 0" in modules/wxbind/setup/wxluasetup.h. This
hand editing will be fixed with the above lib fix for the build files
and I'll fix the problem with the different function signatures for
the wxGLCanvas constructor. In fact I should really just disable it by
default since I don't even know if it's usable without a OpenGL
binding as well.

> It seems that wxLuaEdit is crashing on start, will see if it needs a
> rewrite or if I missed a patch from the previous Mac build (2.8.0.0)
> There is a version of wxlua/wxstedit in MacPorts, if I ever get around
> to cleaning it up and submitting (I'm the maintainer for those too...)

I have also been able to build this too and I don't get a crash. Could
you try the CVS version of wxStEdit? Either that or the problem is
with the default fonts in OSX, there was a problem with a recursion
between the OSX platform specific function and the common one in
wxSystemSettings, but that was fixed a while ago I thought. I use the
SVN wxWidgets from the 2.8 branch so it might be fixed there.

svn checkout http://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_8_BRAN=
CH
wxWidgets-2.8

cvs -z3 -d:pserver:ano...@wx...:/cvsroot/wxcode
co -P wxCode/components/wxstedit

I'm still unsure how to package it the binaries though. So far I've
been building and copying the wxWidgets minimal sample's package for
my personal testing.

There is one problem with wxStEdit however, the help menu item is
messed up since wxWidgets tries to move the wxID_HELP item over to the
system menu. When I try to add new items in the sample program
samples/stedit/wxstedit.cpp they're not shown. I forget the state of
how I left it though and can't check now.

> I used wxWidgets 2.8.4 (UNICODE/RELEASE) and wxStEdit 1.2.5, by the way.
> It has been compiled as a Universal Binary, i.e. both PowerPC and Intel.

That's great. Could we go over this in a week when I get back and we
can flesh out once and for all what is needed for OSX to work out of
the box. I'd really like to learn once and for all how to do it, but
since compiling on my old Emac takes at least an hour, I've been
putting it off.

Thanks and if you wouldn't mind, could you upload the binary again?
    John Labenski

John Labenski wrote:

> MSW Binary only release for now since the build files do not account
> for the options to build the wxWidgets binding libs and which ones to
> link to. Hopefully this will be fixed soon and the source code and (if
> we're lucky) an OSX binary release will be made too.

I made a Mac build of wxLua-2.8.4.1 meanwhile, until the sources are 
out.
I uploaded it to SourceForge's "incoming" area, as 
wxlua-2.8.4.1-tiger.dmg

Here are the issues that I had to patch, before it would build/compile:
http://www.algonet.se/~afb/wx/wxlua-macconfigure.patch ("DEBUG=0")
http://www.algonet.se/~afb/wx/wxlua-macnorpath.patch ("-Wl,-rpath,")
http://www.algonet.se/~afb/wx/wxlua-macglcontext.patch ("SetCurrent")
Will see if I can re-generate real fixes, against the wxLua CVS...

It seems that wxLuaEdit is crashing on start, will see if it needs a
rewrite or if I missed a patch from the previous Mac build (2.8.0.0)
There is a version of wxlua/wxstedit in MacPorts, if I ever get around
to cleaning it up and submitting (I'm the maintainer for those too...)

I used wxWidgets 2.8.4 (UNICODE/RELEASE) and wxStEdit 1.2.5, by the way.
It has been compiled as a Universal Binary, i.e. both PowerPC and Intel.

--anders

Bugs item #1776184, was opened at 2007-08-17 05:13
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=1776184&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: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: wx.wxXmlDocument SetRoot

Initial Comment:
Function SetRoot in wx.wxXmlDocument dont work correct.

Run this code two time (in wxluaedit.exe):

local xml=wx.wxXmlDocument();
local root = wx.wxXmlNode(wx.wxXML_ELEMENT_NODE, "RootNode");
xml:SetRoot(root);

and see exeption.

Version - wxLua-2.8.4.1-MSW_bin.

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

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

John Labenski <jlabenski@...> writes:

> 
> You mean log-off or shutdown the OS? I assume you mean in the
> "function CloseWindow(event)" when it calls
> ConfigSaveFramePosition(frame, "MainFrame")?
> 
> When a wxLuaState is closed the windows are deleted first, then the
> data. Can this be duplicated in a simpler way? What about just killing
> the process (though I've done that a million times without a problem)?
> 

It seems like 'config' exist but when we try to access a method the needed 
logic which makes it a wx-object is not run and it looks like a lua data block 
instead of a wxFileConfig object.

This is similar to the problem you solve before but the cause is different.

Some setup is not done because of the way the program is terminated. I would 
have expected window to use the same code then alt-f4 uses, but alt-f4 works 
perfectly. I will try to narrow it down.

Thanks 

Andre

On 8/16/07, Andre Arpin <ar...@ki...> wrote:
> Hi
>
> There is a problem with accessing widget objects when a program is terminated
> unexpectedly.

There may be, remember that both wxLua and wxWidgets do cleanup when
closing and you can't expect things to exist indefinitely.

> To reproduce simply bring up the editor and log-off or shut down.
> The config object is not reachable.

You mean log-off or shutdown the OS? I assume you mean in the
"function CloseWindow(event)" when it calls
ConfigSaveFramePosition(frame, "MainFrame")?

When a wxLuaState is closed the windows are deleted first, then the
data. Can this be duplicated in a simpler way? What about just killing
the process (though I've done that a million times without a problem)?

Regards,
    John Labenski

Hi

There is a problem with accessing widget objects when a program is terminated
unexpectedly.

To reproduce simply bring up the editor and log-off or shut down. 
The config object is not reachable.

Andre

On 8/15/07, Attila <ejj...@gm...> wrote:
> Hi all!
>
> Last time I was interedsted in - beside some other things - finding an
> external window from WxLUA, and I got this link:
> http://wxlua.sourceforge.net/docs/wxluaref.html#wxProcess I checked it,
> and at home I played with it, but I can't find out how to make it :-/ Can
> somebody help me in it? Everything I know:some letters from the programs
> label, and the program's startuppath. I hope that'll be possible :) Thanks

I really don't believe that this is possible with wxWidgets. This is
fairly low level stuff you're talking about. You will need to find the
OS specific functions to do what you want, create your own *.i
interface files or just push a hand written function into Lua using
wxLuaState::RegisterFunction().

Good luck,
    John Labenski

MSW Binary only release for now since the build files do not account
for the options to build the wxWidgets binding libs and which ones to
link to. Hopefully this will be fixed soon and the source code and (if
we're lucky) an OSX binary release will be made too.

The main thrust of this release is the separation of the libraries and
a cleaner method of creating a wxLuaState from a lua_State* instance,
it should be a little faster too.

 - Separated the wxWidgets bindings into the libraries that wxWidgets
   uses. wxadv, wxaui, wxbase, wxcore, etc...

 - Allow bool = 1/0 and 1/0 = bool in wxlua_getboolean/integer/number.
 - Fix bug in prematurely garbage collecting userdata.
   The userdata was previously keyed on the pointer to the data instead
   of a pointer to the Lua userdata that wraps the data.
 - Moved wxLUA_VERSION... bindings into the 'wxlua' table.
 - Applied patch to lparser.c
   "Too many variables in an assignment may cause a C stack overflow"
 - Streamline creation of a wxLuaState and finding the wxLuaState from
   an existing lua_State,
   See wxlstate.h for changes to the enum WXLUASTATE_ATTACH/SETSTATE
   to be more complete.

Regards,
    John Labenski

Hi all!

Last time I was interedsted in - beside some other things - finding an  
external window from WxLUA, and I got this link:  
http://wxlua.sourceforge.net/docs/wxluaref.html#wxProcess I checked it,  
and at home I played with it, but I can't find out how to make it :-/ Can  
somebody help me in it? Everything I know:some letters from the programs  
label, and the program's startuppath. I hope that'll be possible :) Thanks

Sorry, fixed in CVS now.

Regards,
    John Labenski

On 8/14/07, Andre Arpin <ar...@ki...> wrote:
> using vc7 and the default I have this error
>
>
> cl /c /nologo /TP /Fovcmswd\app_wxluacan_cansim.obj /MDd /DWIN32    /D__WXDEBUG
> __ /D__WXMSW__  /Ic:\Programs\wxW
> idgets\lib\vc_lib\mswd /Ic:\Programs\wxWidgets\include /Od  /Zi /D_DEBUG /Fd..\
> ..\..\bin\vc_lib\wxluacan.pdb  /I..\..\..
> \modules /I.\..\..\.. /I..\..\..\modules\lua\include /D_WINDOWS  /I..\..\..\mod
> ules\wxbind\setup /GR /EHsc   ..\..\wxlua
> can\src\cansim.cpp
> cansim.cpp
> ..\..\wxluacan\src\cansim.cpp(79) : error C2668: 'wxLuaState::wxLuaState' :
> ambiguous call to overloaded function
>         ..\..\..\modules\wxlua\include\wxlstate.h(427): could
> be 'wxLuaState::wxLuaState(lua_State *,int)'
>         ..\..\..\modules\wxlua\include\wxlstate.h(424):
> or       'wxLuaState::wxLuaState(wxEvtHandler *,wxWindowID)'
>         while trying to match the argument list '(int, )'
> NMAKE : fatal error U1077: 'cl' : return code '0x2'
> Stop.
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio .NET 2003
> \VC7\BIN\nmake.exe"' : return code '0x2'
> Stop.
>
> Andre
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

using vc7 and the default I have this error        


cl /c /nologo /TP /Fovcmswd\app_wxluacan_cansim.obj /MDd /DWIN32    /D__WXDEBUG
__ /D__WXMSW__  /Ic:\Programs\wxW
idgets\lib\vc_lib\mswd /Ic:\Programs\wxWidgets\include /Od  /Zi /D_DEBUG /Fd..\
..\..\bin\vc_lib\wxluacan.pdb  /I..\..\..
\modules /I.\..\..\.. /I..\..\..\modules\lua\include /D_WINDOWS  /I..\..\..\mod
ules\wxbind\setup /GR /EHsc   ..\..\wxlua
can\src\cansim.cpp
cansim.cpp
..\..\wxluacan\src\cansim.cpp(79) : error C2668: 'wxLuaState::wxLuaState' : 
ambiguous call to overloaded function
        ..\..\..\modules\wxlua\include\wxlstate.h(427): could 
be 'wxLuaState::wxLuaState(lua_State *,int)'
        ..\..\..\modules\wxlua\include\wxlstate.h(424): 
or       'wxLuaState::wxLuaState(wxEvtHandler *,wxWindowID)'
        while trying to match the argument list '(int, )'
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio .NET 2003
\VC7\BIN\nmake.exe"' : return code '0x2'
Stop.

Andre

On 8/8/07, Scott Morgan <bl...@bl...> wrote:
> As per the subject, what's the safe way of passing a wxDC object into a
> wxLuaState?

Take a look at wxLua/modules/wxbind/src/wxcore_gdi.cpp for examples.

wxLuaState::AddTrackedObject() if you want wxLua to delete it
wxLuaState::RemoveTrackedObject() to delete it
wxLuaState::PushUserDataType() to push it onto the Lua stack.

Get the tag (a number) from the class_tag member
wxLuaBindClass* wxLuaState::GetLuaClass(const char* className) const

Regards,
    John Labenski