Community
Participate
Working Groups
When I submit a bug the display stops updating. Most of the time I switch to another application an the back to eclipse. With this the display usually starts updating again. If I submit again it normally works.
Created attachment 206460 [details] A screenshot of the state after the first submit click In this screenshot you can see the state of the window after I clicked submit (I had to blank some e-mails addresses of our customer).
In this non-updating state one should not click on a tree widget (like the package explorer or the task list). Otherwise eclipse stops responding and must be killed: bug 344818.
Thanks for the bug report. Which Eclipse version is this and which version of Mac OS? Leo have you seen this?
I've seen this with some Eclipse forms in Mac OS Lion (10.7), mainly forms with a table that takes a TableColumnLayout. Can't say I've seen it happening with Mylyn or the Bugzilla editor.
Is there an SWT bug or work-around for this problem?
(In reply to comment #3) > Thanks for the bug report. Which Eclipse version is this and which version of > Mac OS? Leo have you seen this? I have the problem since eclipse 3.7.0. 3.7.1 didn't change the issue. I had the problem with Snow Leopard (latest version, I think) and also with Lion.
This bug describes similar issues with Tree/TableColumnLayouts. 340054: SWT Painting problems in Cocoa https://bugs.eclipse.org/bugs/show_bug.cgi?id=340054
Frank, have you ever seen this?
(In reply to comment #8) > Frank, have you ever seen this? No, but I always use the latest versions. The only problem I see an a Mac is that when I work bootstrapped and in Debug perspective I did not see the value to variables in the tooltip. This is a problem since many months. Actually I work with Eclipse 3.8M5 Mylyn from Head on Mac OS X 10.7.3 with the latest check for updates today. The last update on Mac OS X was yesterday (App Loader 2.5.1)
Peter, are you still seeing this with the latest Indigo or Juno releases of Eclipse?
I am working on 3.7.2 now for almost a week and didn't see this since then. I think it's fixed. Thanks.
Thanks for letting us know. Please reopen if you see this again.