Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 1568 [details]
Example of incorrect rendering
Files created using droiddraw that render correctly on the emulator and actual devices are failing to render correctly under the MD designer - widgets are missing from the screen or incorrectly placed.
Example files attached
Created attachment 1569 [details]
Example of incorrect rendering 2
It would be helpful if you could provide the whole Resources directory (you can use a private attachment). Or if not possible, could I see a screenshot of how the views look like in droid draw and the emulator? Thanks.
Sorry about that - screenshots attached :)
Created attachment 1570 [details]
Created attachment 1571 [details]
Are you sure all the image resources are correctly placed in the resources folder? I fear I would need the whole resources directory to track down this issue.
The problem you are having is caused by the resource file names.
Looks like the Android SDK requires resource file names to only have lowercase letters, numbers, underscores or dots. Also, resource lookup is case-sensitive. So a file name like Back_LazyE.png is not a valid resource name. I haven't been able to find a documentation source for this, but if you create an Eclipse project and add your resources to that project, you'll see that Eclipse explicitly complains about this.
Notice that this could be a limitation in the SDK, not in the runtime. This would explain why Mono for Android has no problem loading the resources. But the designer makes extensive use of SDK libraries to render the layout, and those libraries certainly have this limitation.
I'll do more research to find out more about this limitation, but for now the solution is to convert all resource file names to lowercase.