Bug 114634 - [DND] [ViewMgmt] Moving view with keyboard: some drop areas too small
Summary: [DND] [ViewMgmt] Moving view with keyboard: some drop areas too small
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-01 15:29 EST by Boris Bokowski CLA
Modified: 2021-12-15 10:55 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2005-11-01 15:29:00 EST
Use a fresh workspace (ie fast view bar at the bottom). Reset the Java
perspective, and try to move the package explorer to the right so that it fills
the entire height (the cursor when you drop is an arrow pointing left). Note
that the target area for dropping with an arrow pointing left is very small,
maybe five pixels. Sometimes, you don't see the left arrow at all because the
area is smaller than the distance moved by each keypress.
Comment 1 Boris Bokowski CLA 2005-11-01 15:33:56 EST
The original bug report was bug 73597, most of which is fixed.
Comment 2 Boris Bokowski CLA 2009-11-11 17:31:36 EST
Remy is now responsible for watching the [ViewMgmt] category.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:10 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 4 Eclipse Genie CLA 2021-12-15 10:55:06 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.