Bug 7878 - Designer should render custom views using first parent view that it supports
Summary: Designer should render custom views using first parent view that it supports
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.2.x
Hardware: PC Mac OS
: Low enhancement
Target Milestone: ---
Assignee: Jérémie Laval
URL:
Depends on:
Blocks:
 
Reported: 2012-10-16 20:30 UTC by t9mike
Modified: 2017-09-11 11:56 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:
RESOLVED FIXED

Description t9mike 2012-10-16 20:30:43 UTC
As a work around until full custom support is available, the Designer could  render and allow properties to be set for the closest parent view that it supports. For example, if I sub-class FrameLayout, allow me to interact with a FrameLayout in the designer. 

The Android layout system is very powerful and allowing me to be much more productful than equivalent iOS development. But I am having to create a lot of "helper" classes to extend stock views instead of sub-classing since I will lose designer support. I hope that above suggestion is not too difficult and could be given priority consideration. Thanks.
Comment 1 t9mike 2012-10-16 23:43:02 UTC
"full custom support" -> "full custom view support"
Comment 2 Jeremy Kolb 2015-03-25 10:53:56 UTC
This should be higher priority.  It makes the designer useless once you insert any custom controls.
Comment 3 Stephen Shaw 2017-02-10 17:58:36 UTC
With full custom control support this should be fixed now.
Comment 4 Tharkius 2017-09-11 11:56:07 UTC
As of the latest version (7.1) this is still not fixed, at least in VS for MacOS v7.1, widgets like Spinners or custom TextViews are showing up as grey boxes in the Designer, and when using RecyclerViews I get a ClassNotFoundException error.

Is there a fix for this?