Bug 2985 - debugger tooltips show up in the wrong place on Linux multi-monitor setups
Summary: debugger tooltips show up in the wrong place on Linux multi-monitor setups
Status: RESOLVED DUPLICATE of bug 3556
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-01-20 07:11 UTC by Marek Safar
Modified: 2012-02-21 10:36 UTC (History)
2 users (show)

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


Attachments
test project (7.49 KB, application/zip)
2012-02-03 06:32 UTC, Marek Safar
Details


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 DUPLICATE of bug 3556

Description Marek Safar 2012-01-20 07:11:41 UTC

    
Comment 1 Jeffrey Stedfast 2012-01-26 16:34:29 UTC
Can you provide more details about what isn't working?
Comment 2 Marek Safar 2012-01-27 03:47:36 UTC
Sure, originally I though the pop up window does not every show but it works sometimes (very rarely to be correct). I don't know what's the trigger but most time nothing happens when I hover over any variable/parameter/field, etc.
Comment 3 Jeffrey Stedfast 2012-01-27 15:49:28 UTC
I suspect this might be a resolver issue. Can you attach a sample project?
Comment 4 Marek Safar 2012-02-03 06:31:45 UTC
There is no need for special project, just create default project from MD template.


Enclosing it just in case.
Comment 5 Marek Safar 2012-02-03 06:32:05 UTC
Created attachment 1313 [details]
test project
Comment 6 Jeffrey Stedfast 2012-02-08 14:18:19 UTC
What are you hovering over that doesn't work? 'a' seems to be the only thing worth hovering over and it works every time for me.

Is it a "1 out of 100 times it doesn't work" kind of thing?
Comment 7 Marek Safar 2012-02-08 14:24:04 UTC
It does not for me.

This is on Ubuntu, I'll try to test on Mac tomorrow
Comment 8 Marek Safar 2012-02-09 04:57:23 UTC
I have finally find out what it's.

It happens only on my multi monitor setup. When having MD window on my second monitor the hover tool tip shows at 0,0 on my first screen (left top most screen position) but I cannot move my mouse there because the tooltip disappears. I could possibly make a screen shoot if needed
Comment 9 Jeffrey Stedfast 2012-02-09 08:55:18 UTC
thanks, that is a huge discovery :-)

Probably all the fixes for multi-monitor on Mac broke multi-monitor on Linux or something.
Comment 10 Marek Safar 2012-02-09 10:05:36 UTC
I don't know it's linux problem only, I don't have my multi-monitor setup on other systems available
Comment 11 Jeffrey Stedfast 2012-02-09 10:52:30 UTC
I know this works on Mac because I fixed it a week or so ago :-)
Comment 12 Jeffrey Stedfast 2012-02-21 09:52:31 UTC
*** Bug 3556 has been marked as a duplicate of this bug. ***
Comment 13 Nikita Tsukanov 2012-02-21 10:29:19 UTC
Jeffrey, I have a single-monitor setup, so I think these bugs aren't duplicates. And I fixed my issue by commenting out
 if (y != oldY)
   	 223 	+        Move (x, y);
in main/src/addins/MonoDevelop.SourceEditor2/MonoDevelop.SourceEditor/DebugValueWindow.cs
Comment 14 Jeffrey Stedfast 2012-02-21 10:36:48 UTC

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