Bug 3935 - Blinking cursor disappears
Summary: Blinking cursor disappears
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.8.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-03-16 12:07 UTC by Todd
Modified: 2012-03-19 03:17 UTC (History)
1 user (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 NOT_REPRODUCIBLE

Description Todd 2012-03-16 12:07:15 UTC
Description of Problem:
Blinking cursor does not appear when clicking on the document.
It happens fairly often and it doesn't seem to have a pattern that I can tell.

Steps to reproduce the problem:
1. Click on document to start typing.

Actual Results:
When you click to place the blinking cursor some place in an open document, it does not show. You can still type, but the blinking cursor is not visible.

Expected Results:
Clicking in an open document causes the cursor to be placed at that location and start blinking immediately every time.

How often does this happen? 
About 25% - 30%.

Additional Information:
MonoDevelop that ships with Unity3D ver. 3.5.
Comment 1 Mike Krüger 2012-03-19 03:17:55 UTC
Can't repro, but it may be the unity version of monodevelop that has this problem.