Bug 1537 - Context Menu in wrong position on multi-monitor systems.
Summary: Context Menu in wrong position on multi-monitor systems.
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-10-17 15:35 UTC by Nikolai Sander
Modified: 2011-11-15 20:12 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Nikolai Sander 2011-10-17 15:35:50 UTC
Description of Problem:


Steps to reproduce the problem:
1. Rightclick on anything in the editor on a system with 2 monitors. Secondary Monitor is to the *left* of main monitor.
2. 


Actual Results:
Context menu shows up at the left border of the monitor that MonoDevelop is running on.

Expected Results:
Context menu should show up at the current mouse position

How often does this happen? 
Always

Additional Information:
It's worse for hovering over a variable in debug mode. The context "hint" shows up at the right border of the secondary monitor.
Comment 1 Ulrich Hertlein 2011-11-09 21:42:25 UTC
A similar (related?) issue appears on multi-monitor setups with the secondary monitor *above* the primary (built-in) display.

The editor context menu is always empty and positioned at the top of the primary (bottom) display, where MonoDevelop is running.

Steps to reproduce the problem:
1. Setup secondary display *above* primary display.
2. Run MonoDevelop on primary (bottom) display.
3. Right click on any item in the editor.
Comment 2 Ulrich Hertlein 2011-11-09 21:43:37 UTC
Additionally, in a multi-monitor setup with the secondary display *above* the primary display it is not possible to move MonoDevelop to the secondary (topmost) display.
Comment 3 Alan McGovern 2011-11-15 12:21:41 UTC
This should all be fixed in MonoDevelop 2.8.2 so you just need to update to that (or newer) and everything will be fine.
Comment 4 Ulrich Hertlein 2011-11-15 20:12:34 UTC
I am running MonoDevelop 2.8.2.

With the secondary (external) display *above* the primary (build-in) display the context menu is empty and the position is not correct.  The X-position is correct, but the Y-position is not - the context menu is placed at the top of the primary display instead.

With the secondary display to the right of the primary display it's okay.

Should I file a separate bug for this?