Bug 15787 - Caret position in text entries can get into broken state
Summary: Caret position in text entries can get into broken state
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.14
Hardware: PC Mac OS
: High normal
Target Milestone: master
Assignee: Cody Russell
URL:
: 13950 16510 16943 18032 18954 19510 19631 20996 22055 22784 ()
Depends on:
Blocks:
 
Reported: 2013-10-29 11:24 UTC by Jonathan Shore
Modified: 2015-02-16 05:50 UTC (History)
13 users (show)

Tags: gtk
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:
VERIFIED FIXED

Description Jonathan Shore 2013-10-29 11:24:28 UTC
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.
Comment 1 Mikayla Hutchinson [MSFT] 2013-10-29 15:05:46 UTC
I assume you mean Project Options -> Run -> General -> Parameters. I can repro.
Comment 2 Cody Russell 2013-10-31 17:55:02 UTC
So far I'm unable to reproduce.  Or maybe I'm misunderstanding something. :/
Comment 3 Jonathan Shore 2013-10-31 18:07:22 UTC
@Michael:  yes.  @Cody, let me know if you need more info.  Seems like Michael is able to  repro.
Comment 4 Mikayla Hutchinson [MSFT] 2013-10-31 19:10:16 UTC
I could repro on other GtkEntry widgets too.
Comment 5 Cody Russell 2013-11-01 11:57:14 UTC
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.
Comment 6 Jonathan Shore 2013-11-01 14:12:20 UTC
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.
Comment 7 Mikayla Hutchinson [MSFT] 2013-12-01 20:54:11 UTC
*** Bug 16510 has been marked as a duplicate of this bug. ***
Comment 8 Mikayla Hutchinson [MSFT] 2014-02-26 19:33:06 UTC
*** Bug 18032 has been marked as a duplicate of this bug. ***
Comment 9 Adam 2014-02-26 19:51:14 UTC
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.
Comment 10 Mikayla Hutchinson [MSFT] 2014-04-20 18:50:17 UTC
*** Bug 18954 has been marked as a duplicate of this bug. ***
Comment 11 Mikayla Hutchinson [MSFT] 2014-05-05 17:31:27 UTC
*** Bug 19510 has been marked as a duplicate of this bug. ***
Comment 12 Mikayla Hutchinson [MSFT] 2014-05-09 20:16:24 UTC
*** Bug 19631 has been marked as a duplicate of this bug. ***
Comment 13 Lluis Sanchez 2014-07-01 06:23:42 UTC
*** Bug 20996 has been marked as a duplicate of this bug. ***
Comment 14 Cody Russell 2014-07-07 23:40:32 UTC
*** Bug 16943 has been marked as a duplicate of this bug. ***
Comment 15 Cody Russell 2014-07-07 23:41:30 UTC
*** Bug 13950 has been marked as a duplicate of this bug. ***
Comment 16 Cody Russell 2014-07-08 10:35:41 UTC
This is fixed by disabling Pango ligatures in mono/bockbuild f76c0fc84ed2dd713eae30ddca9fdaeae44e1d6b
Comment 17 Mikayla Hutchinson [MSFT] 2014-08-13 20:06:38 UTC
*** Bug 22055 has been marked as a duplicate of this bug. ***
Comment 18 Mikayla Hutchinson [MSFT] 2014-09-10 11:25:11 UTC
*** Bug 22784 has been marked as a duplicate of this bug. ***
Comment 19 Udham Singh 2015-02-16 05:50:08 UTC
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