| Summary: | Moving a part to a new stack fails, and hides the part instead without a shortcut to activate if it is hidden at all. | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Hitesh <hsoliwal> | ||||||||||
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> | ||||||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | P3 | CC: | remy.suen | ||||||||||
| Version: | unspecified | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Windows XP | ||||||||||||
| Whiteboard: | stalebug | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 179375 [details]
Screenshot
See attached screenshot .
Comment on attachment 179374 [details]
Log File
I don't understand the steps described in the summary.
The bug is randomly reproducible. I do not have specific steps, don't the logs reveal anything ? (In reply to comment #3) > I do not have specific steps, don't the logs > reveal anything ? Half the logs is filled with JDT errors and the last error that seemed to be caused by the workbench seems to be related to a shutdown, which I presume is orthogonal to the problem described on this bug. In any case, I still do not understand what the summary is describing. Based on the screenshot and what you've written, it sounds to me like you tried to drag a part in an existing stack on top of itself to split the stack in two and then said part just disappeared. I don't understand the "without a shortcut to activate if it is hidden at all" part though. (In reply to comment #4) > (In reply to comment #3) > > I do not have specific steps, don't the logs > > reveal anything ? > > Half the logs is filled with JDT errors and the last error that seemed to be > caused by the workbench seems to be related to a shutdown, which I presume is > orthogonal to the problem described on this bug. > > In any case, I still do not understand what the summary is describing. Based on > the screenshot and what you've written, it sounds to me like you tried to drag > a part in an existing stack on top of itself to split the stack in two and then > said part just disappeared. I don't understand the "without a shortcut to > activate if it is hidden at all" part though. I'll leave that upto the person handling that bit of lay-outing. I do not feel strongly this way or that about fixing this one. The screenshot does show the visible layout hint, and a user is likely to assume change after he has dropped a part to that side of the area/window. Hitesh, the issue here is that neither Remy nor I can determine from the steps in your title what to even look for. The screen cap isn't particularly clear on what the issue it's showing is (perhaps the fact that the Console view is completely empty ?). With no steps to reproduce and no idea what the problem we're looking for we're sorta hampered in trying to get a fix for this...;-). Were you trying to drag a view out to create a new stack or dragging the view between two existing stacks? Created attachment 179432 [details] Screenshot after it has worked just fine (In reply to comment #4 & #6) > > Were you trying to drag a view out to create a new stack or dragging the view > between two existing stacks? The same drag and drop actually works fine after a restart. I was trying to drop a view so as to create a new stack for it. See attached screenshot. Created attachment 179433 [details]
Screenshot - A similar glitch while trying to reproduce this.
The entire shared partstack add the parts on it just disappeared. I obeserved this while trying to reproduce this. See screenshot. This one seems like some form of the deltas.xml problem.
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. -- The automated Eclipse Genie. This is a mass change to close all e4 bugs marked with "stalebug" whiteboard. If this bug is still valid, please reopen and remove the "stalebug" keyword. |
Created attachment 179374 [details] Log File See attached log.