Community
Participate
Working Groups
I2002-12-17 When trying to change a font, Eclipse pops up a new window. After clicking inside the window, Eclipse freezes.
Not sure what you mean by Eclispe freezes. The font dialog is application modal and therefore when it is open, the rest of Eclipse should not respond until the font dialog is closed. You can select a new font and then close the dialog with the buttons in the top left. This functionality works for me. I do not see the bug you are reporting.
About two seconds after bringing up the dialog, the mouse cursors turns into a spinning disc. I cannot change the font's family, typeface or size. In addition, I cannot dismiss the dialog (neither via keyboard nor with the mouse). The only option is to kill eclipse. I have observered this behavior on two OS X 10.2.2 systems (G4 and PowerBook G3) BTW: When bringing up the dialog, the console displays: _NSAutoreleasePool(): Object 0x69cd7c0 of class NSCFArray autorelease with no pool in place - just leaking Please let me know how I can further help to track this down.
Just as addition: it seems that the ui is responsive while there is no spinning disc cursor. (At least I can scroll the font size table for that short moment. When the cursor changes, this immediately stops)
Are you using JDK 1.4?
I've installed 1.4.1DP6. Happens with either of the JDKs as default.
This bug sounds similar to: http://dev.eclipse.org/bugs/show_bug.cgi?id=27997 In both cases we are accessing a Cocoa dialog through a carbon API on JDK 1.4.1. Andre, can you try this on JDK 1.4.1? Is there any known problems with this type of interaction? I remember a posting with regard to the fact that JDK 1.3 and JDK 1.4 don't play well together (even when JDK 1.3 is the default) and you have to get the latest JDK 1.4.1. I am not on the trial for JDK 1.4.1 so I don't know much about it. What is the good version of JDK 1.4.1 that fixes this compatability issue?
This works after installing 1.4.1DP8.
Closing as Wontfix since there is nothing to do on the SWT side. The fix is to upgrade to JDK 1.4.1DP8.
Sorry, but It doesn't work with 1.4.1DP8. [since under NDA, sent more details as private mail to Boris]
Andre, I can not run under JDK 1.4.1 because I have not signed the NDA. Moving to you since you have.
*** This bug has been marked as a duplicate of 30021 ***