Hi, On 26/03/2011 09:52, Mattia Barbon wrote:
On 25/03/11 10.24, Mark Dootson wrote:
Why do you want to? Again: I don't see many of them using trunk, and if I'm doing something wrong (or if there a bug in wxWidgets, as it seems the case) I'd like to be alerted rather than the application randomly failing.
I seemed to get quite a lot with Wx::Demo and 2.9.1. My reading of the docs was that intended usage was to switch off wxASSERT_MSG output in a release build of your application - implemented by a runtime call which appears to give you the best of both worlds - i.e. wxASSERT_MSG on by default in the wxWidgets dlls, but can be switched off with a runtime call to wxDisableAsserts. I could not get it to work though so maybe I misread.
I think the best advice is for users to stick to 2.8 (or be prepared to face random failures); wxWidgets development versions aren't for general user consumption, and the OS X/Cocoa port is much less mature than the other ports.
Indeed. I'm very happy with current 2.8.12 and will be sticking with that for my own projects. I was thinking in terms of my PPM and binary build support and whether it was time to start providing 2.9.x versions. Soon I'll need to add Perl 5.14 support and I ought to make sure all works on Mac OS X Lion. I'll now be sticking with wxWidgets 2.8.12 and a 32 bit Perl on Mac OS X for now.
Thanks for your time and help. Regards Mark
