On 8/24/07, Anders F Björklund <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]:/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 ------------------------------------------------------------------------- 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 wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
