Bug 8622 - moving fields around on form can cause errors
Summary: moving fields around on form can cause errors
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Designer ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2012-11-27 16:09 UTC by dave
Modified: 2013-03-13 05:55 UTC (History)
0 users

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 dave 2012-11-27 16:09:56 UTC
I've had several occasions where I'd get error when I ran my solution saying "toRightOf" field name missing (can't recall the exact error).  Other times I'd lose the graphic version of the form saying there were errors.  In any case I have to move fields around in the .axml using a text editor or the Source view.

I also get duplicate fields if I drag a field from on location on the form to another.  Then I have to remove the duplicate in the Source view because Deleting it in the form doesn't delete the Source text.
Comment 1 Lluis Sanchez 2013-03-13 05:55:46 UTC
The field duplication when dragging should be fixed in the latest version of Xamarin.Android.

About the other errors, they could also be fixed in the latest release, but without more information about the error messages it is hard to tell. I'm closing the bug report for now. If you see the error again, feel free to repoen it.