I abandoned the studio for half a year, now I downloaded the latest version and I can’t understand anything. Now CustomView are used in templates, and I cannot add anything to this layout . Teach a teapot how graphic layout editing is now implemented? Those. now it is not possible to drag views to the layout, but only in a separate layout and pick up the include , but this is very inconvenient and binds the hands.

  • Make your layout, what you need from scratch. - pavlofff
  • one
    Better not to use graphic editing at all. It works unpredictably with different nuances. Only xml , only hardcore! - Yuriy SPb ♦
  • Hardcore is nice, but still - somehow you can use these templates ?? - Alexey Burov
  • I will try to repeat - if you do not like the layout of the template, make your own - which one you like. According to your description, nothing at all is clear what you are having and why. There were no differences in the work of the visual editor, from the moment of the first beta to the latest experimental version on the update channel canary chanel - pavlofff
  • Well, well, I will not argue, I’m so noob) But as far as I remember, the basis of templates used to be - RelativeLayout and you could immediately edit any template flexibly, and now they are made up of CustomView, I don’t know anything about them. Tell me where to read how to properly make your templates - I will be grateful! - Alexey Burov

1 answer 1

There are no changes in the visual editor itself that could lead to such "problems" in the general case of its use, however there are nuances in its work.

You had such difficulties, firstly, because you do not fully understand the markup structure in the latest default templates proposed by Google.

The markup activity_main.xml within this template is not intended for placing custom widgets, it serves as the root container and implements only the animated interaction of the FAB and Snakbar - the widgets you need, content, etc. that you consider necessary to display on the screen, according to Google’s idea, you should post markup fragment_main.xml , which generally covers 99% of the needs of fans to write applications using templates.

Secondly, the "glitch" itself about the fact that it is impossible to "throw" the widget in the visual editor assumes that, according to this visual editor, the markup activity_main.xml in this template does not contain containers that could accommodate the widgets. More precisely, the CoordinatorLayout is essentially FrameLayout and, of course, may contain widgets, but the visual editor is not yet able to determine this for containers that are not basic (CustomView). Let's hope that someday it will be fixed, but in the meantime, if you really want to edit activity_main.xml , in spite of Google’s proposed Google Case, you have the following options:

  1. You can solve this problem radically by creating your own markup.
    Right-click on the res/layout folder and follow the New -> Layout resource file . A wizard for creating new markup will appear, where you need to specify its name and the root container, for example, LinearLayout . Then you can work with this markup in the visual editor you like so much.

  2. You can add any base container in manual editing mode (Text). For example, replacing a fragment call ( include @layout/content_main ) with some LinearLayout . After that you can "throw" widgets there in the visual editor.

  3. You can exhale and refuse to use the visual editor, which is mostly useless and sometimes even harmful, and create markup in manual editing mode (Text), using the visual editor only for viewing the result. Then you can add anything and anywhere, in response to the maximum that awaits you, this application will not gather into something working.

  • The third point is 100% correct) - YuriySPb ♦