Community
Participate
Working Groups
1) Select one or more projects in the workspace 2) Project > Clean... 3) Clean selected projects Result: If you have a lot of projects, the checked projects are buried. We should reveal the first checked project.
https://git.eclipse.org/r/#/c/15667/ Possible fix. Mike, can you give this a quick sanity check?
(In reply to comment #1) > https://git.eclipse.org/r/#/c/15667/ > Possible fix. > > Mike, can you give this a quick sanity check? When using Gerrit, it's better to add the person as reviewer directly there.
I have no time for this, closing.
Dani, can you review this again? I have updated https://git.eclipse.org/r/#/c/15667/.
Reopening as Christian has added a new patch.
(In reply to Christian Georgi from comment #4) > Dani, can you review this again? I have updated > https://git.eclipse.org/r/#/c/15667/. Thanks Christian. Submitted with http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=d7c42382aafc4b9ac02b7994f8add1131dac19f2 Updated copyright notice with: http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=fa5555b206b236a520533375f65f0c1558081ef1
I select a project at the bottom of the package explorer and use Project>Clean... The dialog opens (and I have clean Clean projects selected below chosen) and it doesn't scroll to the only checked project. 4.4.0.I20131209-2000 Linux PW
I could reproduce this on Linux GTK. Table.showItem() doe not seem to work unless called in an asyncExec block. Fix: https://git.eclipse.org/r/19692
(In reply to Christian Georgi from comment #8) > I could reproduce this on Linux GTK. Table.showItem() doe not seem to work > unless called in an asyncExec block. > > Fix: https://git.eclipse.org/r/19692 This rather sounds like an SWT bug or a bug in how the dialog is created. Adding an asyncExec should be avoided.
Ok, then how to get SWT people in the loop?
(In reply to Christian Georgi from comment #10) > Ok, then how to get SWT people in the loop? Well, first you need to figure out whether it is an SWT issue. Try to reproduce the bug in an existing SWT snippet or provide an isolated test case and then move the bug to SWT.
I opened Bug 424173 for SWT, I can reproduce it with a table snippet. PW
(In reply to Paul Webster from comment #12) > I opened Bug 424173 for SWT, I can reproduce it with a table snippet. > > PW Thanks Paul! Marking this one as fixed, since the fix itself seems OK.
It may be fixed but I can't VERIFY it since the SWT side isn't done...
(In reply to Eric Moffatt from comment #14) > It may be fixed but I can't VERIFY it since the SWT side isn't done... It can be verified on any platform but Linux, where the SWT bug kicks in. Verified in I20140530-2000.