1
Developing an application saw that on devices with higher resolution the items stay very close together, desire practicality, this is how mobile apps should be, no buttons too small, this makes life difficult for the user, as you can see in the photo nor seems to have little space like this, but using really got tight, already thank you.
<?xml version="1.0" encoding="utf-8"?>.support.v4.widget.DrawerLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:id="@+id/drawer_layout"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:fitsSystemWindows="true"
tools:openDrawer="start">
<include
layout="@layout/app_bar_main"
android:layout_width="match_parent"
android:layout_height="match_parent" />
<android.support.design.widget.NavigationView
android:id="@+id/nav_view"
android:layout_width="wrap_content"
android:layout_height="match_parent"
android:layout_gravity="start"
android:fitsSystemWindows="true"
app:headerLayout="@layout/nav_header_main"
app:itemTextAppearance="@style/NavDrawerTextStyle"
app:menu="@menu/activity_main_drawer"/>.support.v4.widget.DrawerLayout>
<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android">
<group android:checkableBehavior="single">
<item
android:id="@+id/nav_mesa"
android:icon="@drawable/silverware_variant"
android:title="@string/stPedidoMesa"/>
<item
android:id="@+id/nav_entrega"
android:icon="@drawable/delivery"
android:title="@string/stPedidoEntrega" />
<item
android:id="@+id/nav_esperando"
android:icon="@drawable/perm_group_system_clock"
android:title="@string/stPedidoEsperando" />
<item
android:id="@+id/nav_buscar"
android:icon="@drawable/ic_transfer_within_a_station_black"
android:title="@string/stPedidoBuscar" />
<item
android:id="@+id/nav_comer"
android:checkable="false"
android:icon="@drawable/map_marker"
android:title="Comer"/>
</group>
</menu>
Here are the measurements recommended by the Material Design standards for a Navigation Drawer: https://material.io/guidelines/patterns/navigation-drawer.html. Typically the Navigationview component is already a simplification designed to natively meet these standards, then in theory it should not be necessary to alter any measure of it.
– Márcio Oliveira
The colleague @Márciooliveira already quoted correctly, but each case is odd so, the best for it would be to put everything in a layout Constraint, in it Oce has greater control over the measurements and even with the layout of the components in the design
– Armando Marques Sobrinho
Thanks, I’ll see what I’ll do here.
– Wandaymo