Bug 276098 - [GTK/Linux] Another stack's view tab shows up in JUnit's stack temporarily prior to the view being up
Summary: [GTK/Linux] Another stack's view tab shows up in JUnit's stack temporarily pr...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux-GTK
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-13 10:36 EDT by Remy Suen CLA
Modified: 2019-09-06 16:07 EDT (History)
4 users (show)

See Also:


Attachments
Screenshot depicting the problem in question. (19.79 KB, image/jpeg)
2009-05-13 10:36 EDT, Remy Suen CLA
no flags Details
Screenshot depicting the horror in question. (12.04 KB, image/jpeg)
2009-05-14 16:14 EDT, Remy Suen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Suen CLA 2009-05-13 10:36:01 EDT
Created attachment 135585 [details]
Screenshot depicting the problem in question.

Build id: I20090508-2000 (p2'd from 0428 to 0430 to 0508)

1. Have 'Project Explorer' or 'Package Explorer' on the left.
2. Open the 'JUnit' view. Move it to the bottom stack, make sure there are other views there.
3. Close the 'JUnit' view. The stack should still be there with other views per step 2.
4. Run a JUnit test, doesn't matter if it passes or fails.
5. For milliseconds the tab for the explorer will show up in the bottom stack. If you have no views on the left but an editor open, the editor's tab will show up at the bottom.
6. You can also use Ctrl+3 to open the 'JUnit' view, same thing.

I tried a few other views but the same problem does not appear. Please see attached. I have reproduced this on a clean workspace.
Comment 1 Boris Bokowski CLA 2009-05-13 14:55:06 EDT
Paul, does this happen for you as well?
Comment 2 Remy Suen CLA 2009-05-13 15:13:48 EDT
Actually, this seems to happen regardless of whether the stack is there or not.
Comment 3 Eric Moffatt CLA 2009-05-13 22:38:27 EDT
I've never noticed this but I'll look tomorrow.
Comment 4 Eric Moffatt CLA 2009-05-13 23:31:29 EDT
Just tried it on my XP box at home and (unless it's *really* fast) I don't see it...
Comment 5 Remy Suen CLA 2009-05-13 23:41:41 EDT
(In reply to comment #4)
> Just tried it on my XP box at home and (unless it's *really* fast) I don't see
> it...

The problem remains 100% reproducible for me (updated to 0512 a few hours ago) so I guess it is a Linux/gtk+ problem.

Here are some other views that have the same problem:
-Plug-ins
-Plug-in Registry
-Javadoc
-Expressions
-Display

Saw once but can't reproduce again for whatever reasons:
-Debug
-Variables
Comment 6 Paul Webster CLA 2009-05-14 07:51:51 EDT
(In reply to comment #1)
> Paul, does this happen for you as well?

I can reproduce this with the Plug-in Registry view in I20090511-2000

Is this  a symptom of a composite being made visible before it is re-layed out?  My PRV was never in the same stack as the Package Explorer, I wonder why that's the tab that would flash here?

PW


Comment 7 Eric Moffatt CLA 2009-05-14 16:11:09 EDT
Paul, one observation is that the Package Explorer is generally at what would be the window client area's (0,0). It may be worth trying the same tests with the presentation changed to show view tabs on the borrom; if you see part of the package explorer's tree then it may be a BLT painting error with a bogus origin...

Comment 8 Eric Moffatt CLA 2009-05-14 16:12:43 EDT
Remy was nice enough to try this out for me and it appears to be the case...
Comment 9 Remy Suen CLA 2009-05-14 16:14:11 EDT
Created attachment 135855 [details]
Screenshot depicting the horror in question.

Notice how the whole block is gone. My Tree's first item gets copied over to the other side.
Comment 10 Eclipse Webmaster CLA 2019-09-06 16:07:31 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.