Bug 447 - Intellisense can get cut off
Summary: Intellisense can get cut off
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: 2.8.1
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2011-08-25 16:18 UTC by Jonathan Pobst
Modified: 2011-08-30 10:47 UTC (History)
4 users (show)

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


Attachments
Screenshot (82.73 KB, image/png)
2011-08-25 16:18 UTC, Jonathan Pobst
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 FIXED

Description Jonathan Pobst 2011-08-25 16:18:26 UTC
Created attachment 191 [details]
Screenshot

The measurement for when to display Intellisense above or below the caret seems to be a little off.  There is a range where it will display it below the OSX dock instead of showing it above the caret.

Screenshot attached.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-25 16:22:09 UTC
Yeah, our screen measurement doesn't take the dock and its "always in front" behaviour into account. This would affect tooltips too.
Comment 2 Jeffrey Stedfast 2011-08-29 15:09:28 UTC
Ah, yes, this has been biting me too...
Comment 3 Jeffrey Stedfast 2011-08-30 10:47:21 UTC
SHould now be fixed in MonoDevelop master