When creating a custom Toolkit, why does createFrame fail on OSX?

I havent worked on OSX, but the same problem would occur on Windows too and the reason would be this.

I havent worked on OSX, but the same problem would occur on Windows too and the reason would be this: When you do super.createFrame(), you are essentially creating the native peer which ends up trying to show and hence addNotify methods are called. Now inside there are lot of methods that directly cast the peer to WFramePeer(this is incase of Windows, OSX it may be CWindowPeer or whatever), hence the ClassCastException. In your case, my guess is, the class CWindow is trying to cast your UISpecFramePeer to WFramePeer(or CFramePeer or whatever).

Just check the CWindow code by decompiling and check. Please don't forget to post your findings.

Thanks Suraj, I feared it may have been something like this... It seems to work alright for windows, but the OSX toolkit must be setting some sort of internal flag telling it what to expect. Will try to have a crack at decompiling and checking next week sometime. – Clinton Dec 12 '09 at 2:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.