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

Bug 170033

Summary: [Presentations] editor tab reordering drag and drop affordance
Product: [Eclipse Project] Platform Reporter: Andrée Proulx <aiproulx>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: emoffatt
Version: 3.3Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
OSX cursor affordance on DND of tab none

Description Andrée Proulx CLA 2007-01-09 20:12:02 EST
The new editor tab reordering drag and drop affordance should be refine, to show more clearly the insertion point.
Comment 1 Paul Webster CLA 2007-01-09 21:23:14 EST
What DND affordance?  AFAIK it highlights the tab it would appear in (except for the end of the row case).

PW
Comment 2 Andrée Proulx CLA 2007-01-09 21:54:24 EST
Created attachment 56677 [details]
OSX cursor affordance on DND of tab

The cursor on DND is the stack white folder. In the snap it replaced the stack white folder with a carat. 

Perhaps it be more suitable to use a cursor arrow to point at the insertion point.
Comment 3 Eric Moffatt CLA 2007-01-11 08:39:08 EST
Paul, I'm getting set up to allow dragging into/out of TrimStacks. I'm also looking at the feedback we're currently supplying to see if I can bring it up to date a bit...(XOR has major problems on Vista...).

We should talk...;-).
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:10:45 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.
Comment 5 Eclipse Genie CLA 2022-01-17 14:57:23 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.