On 25/03/11 10.24, Mark Dootson wrote:

  Hi,

I've used up all my tuits messing around with 64 bit wxWidgets 2.9.1 on
Mac OS X Snow Leopard - but failed miserably.

<snip>

Both apparently hang during 4th test group. But, all you have to do is
interact with the system anywhere - e.g. move the mouse over the dock or
the menu - not necessarily anything to do with perl instances - and
tests continue. There are several such hangs - and always any
interaction with the desktop allows the tests to continue. There is one
'real' test failure - but I assume that is because Wx::ComboBox is
similar to Wx::ListBox family and should skip that particular test.

If you install Wx anyway, and then go to the samples folder to run
minimal.pl - if you click the top left close X button of the frame - but
ensure that you do not move the mouse - nothing happens. As soon as you
move the mouse, the app exits. If, however, you use the keyboard
shortcut (command Q), the app quits as you would expect. Exactly the
same thing happens with Wx::Demo.

For whatever reason, ExitMainLoop does not Exit until something gives
the event loop a push. I've tried all the obvious workarounds -
WakeUpIdle, ensuring frame set as main window. Ensuring
SetExitOnFrameDelete(1). All produce no effect.

I am using SVN trunk, not 2.9.1, and it seems usable; I wouldn't advise random users to use it though. (Some tests failures are to be expected, I'll try to fix it in wxWidgets itself).

I thought perhaps backporting change r66229 from wxWidgets trunk might
help. Was targeted at windows but seemed similar problem. Made no
difference. So I'll retire defeated on that one.

The second issue was 2.9.1 pushing wxASSERT_MSG to alert dialogs in the
release build !!!. It's a feature. (I can see the point - if only I
understood how to turn them off)

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.

Hope it points someone else in directions that save them time.

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.

Regards,
Mattia

Reply via email to