Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348940

Summary:

[Trim] [UI] Dragging a stack into the shared area leaves its min/max buttons showing

Product:

[Eclipse Project] Platform

Reporter:

Eric Moffatt <emoffatt>

Component:

Assignee:

Platform UI Triaged <platform-ui-triaged>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

pwebster, remy.suen

Version:

4.1

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
Patch that detects additions of already rendered stacks and adjusts their buttons	none

Description Eric Moffatt

2011-06-09 14:17:29 EDT

To Reproduce:

Start a fresh inner
drag the Outline view into the shared area

Notice that the Outline's stack still has its original min/max buttons

Now we're in another state similar to the one describted in bug 348582 Comment 11 where it's possible to make the editor area go away completely...

Comment 1 Eric Moffatt

2011-06-09 14:19:56 EDT

Created attachment 197717 [details]
Patch that detects additions of already rendered stacks and adjusts their buttons


The addition of the extra code in adjustCTFButtons is to account for the fact that the stack has already been rendered and has buttons which need to be removed...

Comment 2 Eric Moffatt

2011-06-09 14:20:28 EDT

Remy, have a look ?

Comment 3 Remy Suen

2011-06-09 21:32:16 EDT

(In reply to comment #2)
> Remy, have a look ?

Eric, I think you told me this patch was no good? Is that correct?

Comment 4 Eric Moffatt

2011-06-13 08:36:07 EDT

yes, there are still issues even with the patch, it needs a bit more polish...

Comment 5 Paul Webster

2011-11-01 12:12:48 EDT

Eric, should this be polished and considered for 4.1.2?

PW

Comment 6 Lars Vogel

2019-11-27 07:38:15 EST

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.

If the bug is still relevant, please remove the stalebug whiteboard tag.