Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Mike, apologies that the following description is a bit vague.
Single left-clicking the mouse in the editor often puts the insertion point at the end of the line clicked rather than the correct character point where the mouse was clicked.
Double-clicking on a word in the editor often doesn't work either: it ignores the double-click.
Slowly repeating the click or double-click doesn't make it work either.
It happens for both the laptop touchpad and an external mouse.
This seems to mainly happen when the line in question is one gone to as the first error or warning from a build, but I'm not sure if it happens at other times too.
I seem to have had some success by pressing Esc and then re-trying the click. I don't know if this is taking the editor out of some mode that is swallowing the clicks, or whether simply the act of hitting a key is fixing it.
I've only had this problem since rebuilding the machine from scratch (hard disk died) a few weeks ago. Previously had same OS (Win 7 Pro). I can't remember if 220.127.116.11 was the MD version running before the hard disk died. MD and its prerequisites were all installed clean from the website.
I've fiddled most of the Options settings to see if this problem goes away (tabs, folding, etc.) and it seems to have no effect.
I will try to figure out the exact sequence of steps that causes the problem, but right now it's intermittent and seemingly random.
The problem is an annoyance because text intended to be inserted or replaced in a line ends up at the end of the line.
Hm, I would even tend do close that one as 'works for me'. I've no problems with click/double click.
2.8.x is very old - the I reworked the text editor much the last 6 months - more than the 2 years before :).
Try to grab a 2.9.x alpha release from the website - if the problems persist we try to fix it. (reopen the bug)
Roger. Didn't realise the latest stable is so far behind. Will see how I fare riding the alpha. Thanks.
Sorry Mike, had to get work things done before venturing onto the alpha.
I'm getting the same problem with 2.9.5 from the website.
Will try to add extra information as it occurs.
2.9.5 has another problem with that :(
Maybe you prove that 18.104.22.168 has the same issues.
*** This bug has been marked as a duplicate of bug 4497 ***
Not a dup, this is WIndows, the other is specific to the Mac GTK.
Maybe it's not so specific at all ? I don't see any clicking issues on linux - I've not worked on windows for quite some time, maybe they share the problem.
Can you check the GTK+ version shown in the MD about box?
The latter is a little weird because the GTK# I downloaded from MD download page says it is 2.12.10 (.10 not .0), in the filename as well as the web page text. Or does GTK# have some weird version numbering transformation?
GTK# for .NET 2.12.10 Download
Mike, the alpha is almost unusable. The editor pane frequently doesn't reflect changes until the insertion point is moved somewhere else. It seems to be the case with copying and pasting as well. The appearing and disappearing lines of code are disquieting.
I understand that this is probably the same issue as under 2.8.x. Let me know if you want any other info.
Would be a pity if MD were to abandon Windows altogether. I'm currently constrained by corporate policy to run under Windows 7.
We're not abandoning Windows, it works fine on my machine and this is the first report I've heard of this problem. Unfortunately that makes it very difficult to diagnose.
I was hoping it would be because you had some other version of GTK on your PATH but that doesn't seem to be the case - 2.16.6 is the version of GTK+ that we shipped in the GTK# 2.12.10 installer. The versioning is even more confusing because MD's About Box doesn't report the release version of GTK#, it reports the AssemblyVersionAttribute value, which hasn't changed since 2.12.0.
What version of WIndows are you using? If you're using Vista or later, are you using Aero Glass? Are you using Remote Desktop or similar, or any tools that might interfere with other applications?
Sorry, Michael, it just seemed from the comments in the various similar bug reports that Windows isn't getting much test coverage.
Yes, running Win 7 Pro SP1 with all updates.
Yes, the theme is the default Windows 7 Aero Theme with the only change being a solid blue background instead of a bitmap.
I also frequently use Remote Desktop from the same laptop to connect to a server (i.e. a separate app) but I have just confirmed that the 'delete' delay (bug related to this one) occurs even if Remote Desktop is not running.
The machine is relatively clean because I had to rebuild it from scratch just a few weeks ago. (Hard disk failure made system images suspect, so only data files were restored; Windows and all apps were reinstalled from scratch on a brand new, freshly-formatted disk.) My standard procedure for installing MD:
1. Go to http://monodevelop.com/Download, click Stable or Alpha, click OS (in this case Windows).
2. Click on the ".NET Framework 4.0" link (badly named: actually "Microsoft Windows SDK for Windows 7 and .NET Framework 4"), download and install.
3. Install "GTK# for .NET 2.12.10".
4. Apply the registry hack to make GTK work with touchpads (http://blog.alexou.net/2010/07/30/scrolling-in-gtk-apps-with-synaptics-driver/)
5. Download the MD installer and install.
The strange thing is that I didn't have these problems prior to the rebuild a few weeks ago (i.e. on the machine as built in Sep 2011 with its original hard disk, same OS and theme and same procedure followed). MD had updated itself several times over the six months, and was very stable. (I was running the stable release.)
I'll play some more and see if I can figure out relevant factors.
This one got fixed