I've implemented the new Navigation Drawer pattern in an Android app and for some reason it will stick with the 20dp tab preview probably close to 10% of the time.
I've implemented it with a complete copy paste of the demo app so I was surprised not to find anyone else having this issue on SO. Is nobody else seeing this? It happens on both my test devices and I cannot recreate it at all on any of the google apps that have a drawer.
Any ideas of what might cause this? I can paste my code but it's the same as the demo app. The only difference is what I have in my drawer layout (two ListViews and a spinner, but I'm only populating one of the ListViews like the demo app does).
EDIT: This can be recreated consistently in the official demo app.
A video demonstration: http://youtu.be/aEVHannoYvQ
There is a open issue on the Android issue Tracker , Star it ;)
Android Issue Tracker(NavigationDrawer)
hopefully it gets fixed :)
EDIT: Seems there is a fix, read this: ClickMe
Related
I have implemented bottom navigation with Navigation component but some how it's not working as expected. It doesn't load fragment UI and also it doesn't change UI when we click on another tab. If we click on same tab again, It's crashing. Please take a look this at video to get better understanding here.
It's having too many file, So i uploaded complete example project with above mentioned issue here.
I have cross verified my implementation with NavigationAdvancedSample app of Android Architecture Component Samples and Android-Extension project as well.
Find their repo here:
NavigationAdvancedSample.
Android-Extension.
Let me know if you need anything else from my end. I stuck at this point and already spent few hours but didn't found any solution.
Thanks.
I'd like an example of a step-by-step implementation of this type of menu on Android Wear.
I can not understand the concept of this implementation
It can be in Xamarin or Java.
Documentation:
https://developer.android.com/training/wearables/ui/ui-nav-actions#java
Expectancy:
ndroid
Glad you are enjoying Xamarin!
There's multiple ways of navigating between fragments, regardless if it's a Watch. One of them is using ViewPagers. If you look into the Android documentation, you will find details of how to make it look really cool and fancy with small changes to the ViewPager code.
As far as examples to the Google Wear app that uses ViewPagers, you can take a look at this and some of the other examples of Android wear applications. Let me know if that helps. Btw, you might have more success simply implementing that code (layout/activity_main.xml, SimpleGridPagerAdapter.cs and MainActivity.cs) in your project, than making those projects works since they're old.
Since you are looking for the usage of the android.support.wear.widget.drawer.WearableDrawerLayout, you can take a look at this, particularly at the activity_main.xml. For implementing the WearableDrawerLayout, you have the following
WearableNavigationDrawerView that acts as the top navigation drawer
FrameLayout that contains your fragment
WearableActionDrawerView that acts as your bottom action drawer
PS: I noticed you are looking for Java examples too, this one seems very simple example to follow. You just have to check the Planets.java, MainActivity.java, and activity_main.xml files in that repo
I want to create an app that uses a tab layout with sliding views (something like this):
Here's the issue:
I searched all over the web for a guide that could explain how to do this kind of thing but all I tried didn't work for me. I read somewhere that tabs layout is deprecated with Lollipop, so I tried to find an alternative way to do what I wanted to do, but nothing. Every tab layout app I try to create ends up with a crash while testing and I think it's due to something about the ActionBar, always because of the ActionBar Tabs are deprecated in Lollipop. I'm not going to post any code because I created so many projects that I lost their count, and also because they are quite the same.
So, anyone could please link me a guide or explain a working method that allows to do what I explained?
All I can say is that the app has to be used on Lollipop, so I'd like to know the compile settings to put in the gradle files.
Another important thing is that i use Android Studio, even if most of the tutorials i find on web are about Eclipse.
I hope to have explained in detail my problem and what i want to do and i thank you all in advance.
Here is a detailled description of how to use the SlidingTabLayout like Google uses it in the Store:
https://github.com/codepath/android_guides/wiki/Google-Play-Style-Tabs-using-SlidingTabLayout
Like Hugo already mentioned: it works with viewpager
I want to make a moving list appear from the left of the screen of the activity in the android app.
Something like the facebook app shown below :
,,
how can I make something like that in an android app.
Thanks.
This is a very popular UI pattern called a sliding menu / slider. You can search for open source libraries / projects which implement this for you.
Here is the first one I found on google.
This one is useful if you want to support old (pre holo) android devices too. It's an addon to the excellent holoeverywhere library.
And last but not least, take a look at this official pattern by google which also implements the same behavior. The code for creating it is available here.
The concept behind this is that you are taking a screen grab of the current activity and then loading in the menu. Your not actually sliding between activities, your moving the screen shot. Thats a very basic explanation of whats happening.
If you search for slide navigation on github I'm sure you'll find something.
I have been browsing the web for a while now and looking at different examples of how to implement a tab bar.
The problem I am having is deciding the correct approach to creating this feature. The option that seems most used is to have one main activity called MainActivity or something and using fragments as the tabs. This is all well and good and I have created an application like this fine.
The problem I am having is I am in two minds as to whether this is the right way to go about it as coming from an iOS development background it just doesn't seem right due to these tabs having different functions.
Any pointers would be great.
EDIT I have also looked into ActionBarSherlock but couldn't get to use it in a project as it kept coming up with errors and I couldn't find a thread that sorted the problems I was having out.
Disco
You should be using fragments, yes. There is an example of how to do it here: http://developer.android.com/guide/topics/ui/actionbar.html#Tabs
This "only" works with Tabs that are part of your Actionbar, though. Shouldn't be too much of a problem, because they usually should be part of your Actionbar. You can also manually move the tabs if you're not content with their location, or roll your own buttons that look like tabs.
Keep in mind that tabs in Android aren't quite the same beast as the tab bar is in iOS. They look similar and behave similar, but there are subtle conceptual differences in how they are supposed to be used. Don't use them for your basic app navigation, but rather for switching between similar "things".
If you want to employ this on device pre-3.0 though, you will have to use ActionBarSherlock. It does work fine and we're using it in several projects, so if you're having problems integrating it I suggest creating a new question for that, I'll be happy to help.