Bug 10625 - Android designer locks drawable files referenced in displayed layouts
Summary: Android designer locks drawable files referenced in displayed layouts
Status: VERIFIED DUPLICATE of bug 9132
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.6.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-02-24 16:12 UTC by softlion
Modified: 2013-03-20 07:16 UTC (History)
4 users (show)

Tags:
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 DUPLICATE of bug 9132

Description softlion 2013-02-24 16:12:09 UTC
When a layout file is opened in design mode, if this file references a drawable 9 patch image (in a background property for example), the image file is locked and can not be renamed.
Comment 1 Lluis Sanchez 2013-03-13 05:46:13 UTC

*** This bug has been marked as a duplicate of bug 9132 ***
Comment 2 Jatin 2013-03-20 07:16:23 UTC
Today with the latest builds:

XS 4.0.2.22
VS 2012/2010
MFA 4.6.01073
Mono 2.10.12

This issue does not exist, as now the exception does not appear when edit the layout axml file after opening it in the code editor.

Hence, closing this issue.