Bug 10383 - renaming a @variable set the selection at the wrong offset
Summary: renaming a @variable set the selection at the wrong offset
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Linux
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-02-18 12:19 UTC by Peter Hultqvist
Modified: 2013-03-11 04:41 UTC (History)
1 user (show)

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:

Description Peter Hultqvist 2013-02-18 12:19:22 UTC
After pressing F2 to rename the variable @event the green special selection for renaming is skewed one character to the left.

Example code, <sel></sel> marks the selection being used
        protected override void OnCloseEvent(QCloseEvent<sel> @even</sel>t)

when "@event" should be selected either " @even" or "(@even" get selected depending on the variable location the cursor was at.

The other occurrence of the variable then get the same skewed selection and is immediately replaced with the content of the selected variable. Although I believe this won't be an issue once the selection is fixed

This was tested on the current master branch: 
commit abfc6268191fefb56c2d3076f76513b0e55ce709
Date:   Wed Jan 30 16:10:56 2013 +0000
Comment 1 Peter Hultqvist 2013-03-11 04:25:10 UTC
Works in 4.0.2
Comment 2 Mike Krüger 2013-03-11 04:41:45 UTC
I just forgot to close that bug :/