Bug 5905 - Same name on axml, different package causes wrong xml being edited
Summary: Same name on axml, different package causes wrong xml being edited
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 1.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2012-06-28 08:05 UTC by André Ingar Sørensen
Modified: 2013-10-25 05:30 UTC (History)
4 users (show)

Tags: smfix
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 André Ingar Sørensen 2012-06-28 08:05:21 UTC
Created an axml called Main.axml in Layout folder, and added my main screen items there. Created a package Menu for my menus, and added a Main.axml here for my main menu. When I double clicked the Main.axml in the Menu folder the code and layout from the Main.axml in the Layout folder shows up. Editing here also overwrites the Main.axml in the Layout folder.
Comment 1 Andrew Gaspar 2012-09-18 11:27:47 UTC
This also occurs for layouts with the same name in different Layout folders, which is really frustrating for designing layouts for multiple screen sizes.
Comment 2 Lluis Sanchez 2013-10-25 05:30:17 UTC
Fixed. The fix will be included in Xamarin Studio 4.1.13 and Xamarin.Android 4.10.1.