Under Mac OS X, AWT/Swing frames (for example the one created in "swing.fan" example file) do not react to any input (clicking, resizing, etc). Mouse pointer has a "waiting" icon when it's over the frame, the frame decorations are grey, and the process is shown as not responding in Activity Monitor. Although the frame is being correctly repainted.
brianThu 11 Jun 2009
Can you get a stack dump to see what might be happening?
I doubt that has anything to do with Fan per se (but you never know)
YelaginThu 11 Jun 2009
Excuse me, stack dump of what thread at what moment? There's no exceptions thrown, or anything. I would give some kind of calls trace if I knew how to get it.
brianThu 11 Jun 2009
On Windows if you do Ctrl+Break it dumps the current state of the threads to stdout.
I assume something like that is available for Mac OS X if you send the right signal. But I don't know how it works.
Yelagin Thu 11 Jun 2009
Under Mac OS X, AWT/Swing frames (for example the one created in "swing.fan" example file) do not react to any input (clicking, resizing, etc). Mouse pointer has a "waiting" icon when it's over the frame, the frame decorations are grey, and the process is shown as not responding in Activity Monitor. Although the frame is being correctly repainted.
brian Thu 11 Jun 2009
Can you get a stack dump to see what might be happening?
I doubt that has anything to do with Fan per se (but you never know)
Yelagin Thu 11 Jun 2009
Excuse me, stack dump of what thread at what moment? There's no exceptions thrown, or anything. I would give some kind of calls trace if I knew how to get it.
brian Thu 11 Jun 2009
On Windows if you do Ctrl+Break it dumps the current state of the threads to stdout.
I assume something like that is available for Mac OS X if you send the right signal. But I don't know how it works.