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.
For the last few Beta versions of Xamarin develop have been unable to edit existing command line parameters in the Project Options dialog: Project Options -> General -> Parameters field.
When inserting text or backspacing over text in the parameters there is an 1 char offset problem where the wrong characters are deleted (on the i-2th position). The same is true for insertions.
To test, add some parameters to an application project(perhaps enough to require scrolling beyond entry field). Close the options pane. Open options pane and attempt to edit.
I assume you mean Project Options -> Run -> General -> Parameters. I can repro.
So far I'm unable to reproduce. Or maybe I'm misunderstanding something. :/
@Michael: yes. @Cody, let me know if you need more info. Seems like Michael is able to repro.
I could repro on other GtkEntry widgets too.
Jonathan, how often does this happen? Your description makes it sound like it's happening 100% of the time, is that the case? Michael said it doesn't happen to him all the time and he's not sure what triggers it.
All of my argument lists span beyond the visible textentry box (don't know if that is relevant), but for me it is 100% of the time in that scenario.
*** Bug 16510 has been marked as a duplicate of this bug. ***
*** Bug 18032 has been marked as a duplicate of this bug. ***
To improve reproducability:
When editing text in the "Additional mtouch arguments" textbox (on Project
Options/iOS Build), the caret position is incorrectly calculated IF the caret
is positioned after a space character.
For example: enter the text '-gcc_flags "-framework QuartzCore"'
Then click anywhere after the space (any part of "-framework QuartzCore").
The carat will render in the correct position, but any keys typed will operate
on the PREVIOUS character position.
To get text to insert/delete at the position you want, you have to actually
click on character ahead of where you want to make your modification.
*** Bug 18954 has been marked as a duplicate of this bug. ***
*** Bug 19510 has been marked as a duplicate of this bug. ***
*** Bug 19631 has been marked as a duplicate of this bug. ***
*** Bug 20996 has been marked as a duplicate of this bug. ***
*** Bug 16943 has been marked as a duplicate of this bug. ***
*** Bug 13950 has been marked as a duplicate of this bug. ***
This is fixed by disabling Pango ligatures in mono/bockbuild f76c0fc84ed2dd713eae30ddca9fdaeae44e1d6b
*** Bug 22055 has been marked as a duplicate of this bug. ***
*** Bug 22784 has been marked as a duplicate of this bug. ***
I have checked this issue on following builds
Environment Info :
Mac OS X 10.9.5
Xamarin Studio 5.7.2 (build 1)
Mono 3.12.0 ((detached/a813491)
GTK+ 2.24.23 (Raleigh theme)
Xcode 6.1.1 (6611)
Now this issue is working fine, Hence closing this issue.
Screencast : http://www.screencast.com/t/dIGHgR665X