I have a modal screen with swipe-to-reveal sections. I'd like to move it to a drawer, but the drawer close action steals all the gestures. Is there a way to prevent this?
A crude way could be to have disableCloseGesture. Ideally, it would only respond to touches starting at the opposite edge to the side of the drawer.
Related
Following Android guidelines I have added ActionBarDrawerToggle which brings up a DrawerLayout.
This is fine but I can't help feeling my users will have a hard time noticing it since it's so tiny.
Before that I had several tabs in the ActionBar but there were too many tabs so I did replace them with the DrawerLayout as they say to do when you have more than 3 tabs.
However, are there any techniques to make the Drawer Toggle more prominent without breaking up the Android Design Guidelines. Are there any examples to that?
As detailed in the Navigation Drawer Interaction Design Guidelines:
Introduce the user to the drawer at first use
Upon first launch of your app, introduce the user to the navigation drawer by automatically opening it. This ensures that users know about the navigation drawer and prompts them to learn about the structure of your app by exploring its content. Continue showing the drawer upon subsequent launches until the user actively expands the navigation drawer manually. Once you know that the user understands how to open the drawer, launch the app with the navigation drawer closed.
This ensures that users understand that the Navigation Drawer exists and that they notice the drawer toggle animating as they close/open the drawer.
I want to finish such a demand, in the interface embedded UIWebView control, when the user clicks on a blank area and the area that link, jump to different new interface, but I can't distinguish between the two. Could someone help me?
I try put an transparent NSView over an UIWebView, and overide the touchesDidBegin etc, then send them to your webview. Ex: But the UIWebView can't accept touch events。
I have a midlet which checks some conditions and at some point, when some condition becomes true, I display a pop-up dialog to the user.
If nothing happens for a while, the screen saver kicks in and after that the pop-up is not shown to the user - the screen is simply dark.
Is there way to wake up from the screen saving mode programmatically?
I know I can alert the user by sound and vibration and I do that, but I'd like to be able
to get the screen to react in some way (either to flash the lights, or just turn the light on).
Is there any way to do that?
You can implement showNotify() and hideNotify() from the Canvas class.
I added the SwipeGesture to a View on my Page. If i make a Left Swipe the View switches to another Subview. Same if you do a right swipe.
The Problem is, that on one of my pages is a UISlider and if you change the value of this, the Swipe Gesture Triggers and Navigates to another Subview.
Is it possible to make a Swipe Gesture which triggers if you swipe with 2 Fingers?
Yes, you can use a swipe gesture with two fingers using the numberOfTouchesRequired property. I agree with #Jonathan.Peppers though that if you have conflicting gesture patterns it's bad UX practice to slightly differentiate them by incrementing the touch points.
I would also recommend using this abstraction for using gestures and modify it using some sort of type check for swipe: https://gist.github.com/1453770
if(typeof(T) == typeof(UISwipeGestureRecognizer)) {
((UISwipeGestureRecognizer)fRecognizer).NumberOfTouchesRequired = 2;
}
I have attached a toolbar with a UITextField and UIButton to the keyboard when it becomes the first responder via the user taping inside the textfield
textField.inputAccessoryView = theToolbar;
Problem is, the toolbar disappears when the keyboard is dismissed, thus preventing any further input.
Any ideas on how to make the toolbar go back to the bottom of the screen rather than off it completely?
I'm thinking a delegate method might help but Im really not too sure. It seems once the inputAccessoryView always the inputAccessoryView :(
Cheers
The input accessory view is automatically dismissed with the input view (the keyboard, in this case). Generally you do not want to have an input accessory view in your view hierarchy. Instead, if you want your toolbar to scroll up when the keyboard is shown, you should follow the guidelines for Managing the Keyboard.
You could try using an additional toolbar that is offscreen as the inputAccessoryView, which could "fake" the appearance of what you are trying to do. Alternatively, have you tried adding the toolbar back to the bottom of the screen using
[self.view addSubview:theToolbar];
when the keyboard reaches the bottom of the screen? You can use keyboard notifications for this.