Bug 24725 - [Presentations] Provide API for querying for physical view bounds
Summary: [Presentations] Provide API for querying for physical view bounds
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2002-10-12 01:43 EDT by Max Rydahl Andersen CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Max Rydahl Andersen CLA 2002-10-12 01:43:23 EDT 
In some cases it would be nice to have an API for finding which view is to the left, right, north, 
south position of a certain other view. (The information seem to be used when dragging and 
dropping views in order to render the correct arrows and dropping the views correctly)

I have 
not been able to find the physical view bounds through the API, only by down-casting views to their 
concrete class and then find their "viewpart"'s window boundaries - not a good thing :(

My 
particular use case is for providing "geographical" navigation actions, so the user can just 
navigate in the direction of the view instead of through Ctrl-F7/Ctrl-F6 like functionallity.
Comment 1 Paul Webster CLA 2006-09-28 10:58:36 EDT 
There are currently no plans to work on this feature.

PW
Comment 2 Denis Roy CLA 2007-06-22 09:32:28 EDT 
Changes requested on bug 193523
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:15:47 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.