No, Activity/Fragment Transitions are not possible on pre-Lollipop devices. According to the documentation: Start an activity with additional launch information, if able. In Android 4.1+ additional options were introduced to allow for more control on activity launch animations. Applications can use this method along with ActivityOptionsCompat to use these animations when available. When run on … Read more
For example you can: Use a TreeMap<Date,List<Event>> for splitting elements by date. This will be a collection for keeping your business objects. Of course if you already have a similar structure you can keep it. It’s just important to have something for easily building list of items for populating UI with right elements order. Define … Read more
If you are calling setSupportActionBar() you don’t need to use toolbar.inflateMenu() because the Toolbar is acting as your ActionBar. All menu related callbacks are via the default ones. The only time you need to call toolbar.inflateMenu() is when you are using the Toolbar as a standalone widget. In this case you will also have to … Read more
On the exiting activity, call getWindow().setExitTransition(null); On the entering activity, call getWindow().setEnterTransition(null); It will prevent the fade out of the exiting activity and the fade in of the entering activity, which removes the apparent blinking effect.
With the Material Components Library:. Add the dependency to your build.gradle: dependencies { implementation ‘com.google.android.material:material:1.3.0’ } In this case you can use a MaterialButton in your layout file: <com.google.android.material.button.MaterialButton …. style=”@style/Widget.MaterialComponents.Button” app:cornerRadius=”..” app:strokeColor=”@color/colorPrimary”/> Use app:cornerRadius attribute to change the size of corner radius. This will round off the corners with specified dimensions. You can also … Read more
In your package.json file add this to dependencies “hammerjs”: “^2.0.8”, Or if you want an alternative automatic way just you can type npm i hammerjs –save (or npm i [email protected] –save if you want, since 2.0.8 is the latest version nowdays) in your root project folder and test then, if the problem still occurring try … Read more
Your LinearLayout is wrapping its height, cutting off the shadow of the card at the bottom. Either put some padding on the bottom of the LinearLayout or set it to match_parent on its height. PS that outer RelativeLayout is useless — get rid of it and put all the padding and background on the inner … Read more
You can use the MaterialAlertDialogBuilder provided by the Material Components library which allows the creation of a Material AlertDialog. Just use: new MaterialAlertDialogBuilder(MainActivity.this, R.style.MyThemeOverlay_MaterialComponents_MaterialAlertDialog) .setTitle(“Dialog”) .setMessage(“Lorem ipsum dolor ….”) .setPositiveButton(“Ok”, /* listener = */ null) .setNegativeButton(“Cancel”, /* listener = */ null) .show(); Then define your custom style, using the buttonBarPositiveButtonStyle and buttonBarNegativeButtonStyle attributes: <!– Alert … Read more
<!– Application theme. –> <style name=”AppTheme” parent=”Theme.AppCompat.Light”> <item name=”android:actionBarStyle”>@style/MyActionBar</item> <!– Support library compatibility –> <item name=”actionBarStyle”>@style/MyActionBar</item> </style> <!– ACTION BAR STYLES –> <style name=”MyActionBar” parent=”@style/Widget.AppCompat.ActionBar”> <item name=”android:background”>@drawable/actionbar_background</item> <item name=”android:windowActionBarOverlay”>true</item> <!– Support library compatibility –> <item name=”background”>@drawable/actionbar_background</item> <item name=”windowActionBarOverlay”>true</item> </style>
If you are using a MaterialComponents Theme there is no difference between <Button /> and <com.google.android.material.button.MaterialButton />. There is an auto-inflation enabled which will replace <Button with <com.google.android.material.button.MaterialButton at runtime. The MaterialComponentsViewInflater replaces some framework widgets with Material Components ones at inflation time, provided if a MaterialComponents theme is in use. Something similar happens also … Read more