Aahh.
MacOSX give real head ache to me.
I don't know why it doesn't want to work as Linux and Windows.
I try to investigate this at bug cleaning session, before next release.
Thanks for reporting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't fix the issue indeed. But will use wx2.8 on next release.
So it will be work. Indeed I chose wx2.9 for "Cocoa" API for OSX, I thought it's not buggy as wx Carbon implementation since it fixes wxMessageBox issue with "Find" dialog, but it looks it generates more problem than it solves.
Now I coded new OSX Message Box of mine, which doesn't make OSX stall. So could revert back to wx2.8 for OSX...
Your issue will be fixed on next release since I use wx2.8.
But that bug is still true for wx2.9 OSX library. So I tag this as "postponed".
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Aahh.
MacOSX give real head ache to me.
I don't know why it doesn't want to work as Linux and Windows.
I try to investigate this at bug cleaning session, before next release.
Thanks for reporting.
I found the issue.
It's due wx 2.9.4 library.
On Windows and Linux, I use still 2.8.12 so not aware from bug.
I don't fix the issue indeed. But will use wx2.8 on next release.
So it will be work. Indeed I chose wx2.9 for "Cocoa" API for OSX, I thought it's not buggy as wx Carbon implementation since it fixes wxMessageBox issue with "Find" dialog, but it looks it generates more problem than it solves.
Now I coded new OSX Message Box of mine, which doesn't make OSX stall. So could revert back to wx2.8 for OSX...
Your issue will be fixed on next release since I use wx2.8.
But that bug is still true for wx2.9 OSX library. So I tag this as "postponed".
Thanks.