Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351474 - [QuickAccess] Quick access menu split between dual monitor setup
Summary: [QuickAccess] Quick access menu split between dual monitor setup
Status: CLOSED DUPLICATE of bug 374058
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Remy Suen CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 12:27 EDT by Curtis Windatt CLA
Modified: 2012-03-22 10:44 EDT (History)
4 users (show)

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 Curtis Windatt CLA 2011-07-07 12:27:11 EDT 
Version: 4.1.0
Build id: I20110620-1631

Using a dual monitor setup, Eclipse is maximized in the left monitor.  The quick access menu (Ctrl-3) is in the top right of the monitor.  When it opens, its contents are split between my two monitors, making it quite difficult to read.
Comment 1 Prasad Sawant CLA 2011-11-07 05:19:35 EST 
(In reply to comment #0)
> Version: 4.1.0
> Build id: I20110620-1631
> 
> Using a dual monitor setup, Eclipse is maximized in the left monitor.  The
> quick access menu (Ctrl-3) is in the top right of the monitor.  When it opens,
> its contents are split between my two monitors, making it quite difficult to
> read.

The same issue is reproducible on AIX with view menu pull down.
Comment 2 Dean Roberts CLA 2011-11-17 09:13:15 EST 
This was either fixed in previous work, or fixed as a side effect of bug 363582
Comment 3 Curtis Windatt CLA 2011-11-17 09:54:56 EST 
So what build is this fixed in?  No milestone is marked on this or bug 363582.
Comment 4 Curtis Windatt CLA 2012-03-22 10:44:06 EDT 
This was never fixed.  The problem is mostly how wide the quick access popup is, so I will mark this as a dupe of that issue.

*** This bug has been marked as a duplicate of bug 374058 ***