I need to disable control center on one key view in case i use "swipe up" gesture for navigation on that view controller
Add the following to your Info.plist:
<key>UIStatusBarHidden</key>
<true/>
<key>UIViewControllerBasedStatusBarAppearance</key>
<false/>
When you "swipe up" it avoid to reveal the control centre. The gestures work normally for your application and it shows only a grabber
Best workaround I've found for this is to present the view controller in full screen. (I'm not talking about the deprecated Full Screen property)
By doing so you force the notification \ control center to be triggered with two swipes instead of one. If the user swipes up or down he'll see a small arrow instead of the all notification\control center. Another swipe on that arrow will open the center view. There's no public way to disable it completely so this is your best bet.
You can't do this. Control Center is a apple implemented feature. This is the same thing as notification center, which you also cannot disable.
You can't do it. But you can warn users that they can disable it from the "Settings" (not that I would suggest you do this, unless you want to make your users mad)
Related
I'm really new to origami and quartz. I've only spent a few hours on it today and am still a little lost.
I'm trying to show some interaction for a website in a web browser. What patch would I use to register a mouse hover on a button or window? More specifically I've attached a link to show what kind of interaction i'm trying to achieve (Living Options section).
Also how do you use the mouse scroll patch?
Thanks
To register a mouse hover, you would use the setup pictured above. First you need to define a Hit Area (the area to be hovered). Plugged into this you need an Interaction patch. Finally, you need to define which kind of mouse interaction you want to track – in this case Mouse Over. You have have a number of options here:
Plug the Mouse Over output port into another patch, e.g. the Text patch.
Create a Wireless Broadcaster (pictured) to send the interaction anywhere else in your composition (via a Wireless Receiver).
Publish the output up one layer. To do this, hover over the desired port and hit 'p'. The output will now be available from the parent patch.
I'm trying to build a Firefox add-on based on their SDK and I wanna use panel for this. The panel is connected to a widget, so every time I click on the widget icon the panel shows up.
My problem is that I want the panel to stay visible even if I click on an area outside the panel and to be able to close only based on a certain situations.
Can this be achieved, or the panel API doesn't support this?
Thanks
It can't be achieved through the SDK API. However, you could actually "hack" the panel in order to be persistent, the problem is that you will face with other issue – basically won't go away, and other small stuff.
You can get additional details on Bugzilla if you're interested: Add a "isPersistent" attribute for panels. Notice that the bug is a WONTFIX, but it will give you an idea about the issue you could face. Also, there are some new widgets that will coming in the future, that could mitigate the needs to have the panel "persistent" (they're mentioned and linked in the bug above).
This is the offical sdk method of doing it:
let myPanel = Panel({.....})
let { getActiveView }=require("sdk/view/core");
getActiveView(myPanel).setAttribute("noautohide", true);
Floating panels are not supported by the SDK
I tried -setFrame:display: and -windowDidMove: but they are not sent while moving window.
If You want to track NSWindow live moving, it's not possible by default You’ll have to do it on your own. It's possible to get notification when NSWindow is started to drag (move) with NSWindowWillMoveNotification or ended dragging (moving) - NSWindowDidMoveNotification.
Take a look at these examples they can help You to solve live window moving problem:
1. Example:
Description: Very short category on NSWindow that makes windows post
NSWindowDidMove notifications continuously during dragging (much like
NSWindowDidResizeNotification behaves). Uses a secondary thread and
behavior can be toggled.
Download link.
2. Example:
Project download link.
You can register an observer for NSWindowDidMoveNotification.
Is there way to change the orientation of the emulator in runtime.
I have some tests for a component which include different layouts based on orientation. It would be great if this is possible.
I'm not sure what you are asking for?
If you just want to change the orientation yourself, then use the mouse - there's some buttons top right on the emulator to change orientation - http://msdn.microsoft.com/en-us/library/ff402568(v=VS.92).aspx
If you want to automate this, then since I'm not sure there's a keyboard shortcut or command line for this, then you could just about do it by modifying the code inside https://github.com/Expensify/WindowsPhoneTestFramework/
Alternatively... it might be quicker/easier to just hack your own code to set the supportedorientation of each page just for one-off testing.
Late response (translated by google), but can be useful for others.
Management guidance on this in the options bar to the right of the emulator:
Detail to know, so that the orientation is done properly and is taken into account, we must re-press the "pause" button if you did previously to use your keyboard. Otherwise, you will feel duty systematic tilt your head to the left or right. :)
I am developing an application for WP7 platform (actually WP7.1 sdk). I have a page with an image and couple textboxes in a Grid encapsulated in scrollviwer, that supports both portrait and landscape orientation. I am facing some odd behaviors that rised my two questions:
Is there a solution or at least explanation why in Portrait mode when I focus on any textbox and SIP comes up I cannot scroll through the page in the rest of viewable area? When I try to scroll it with SIP up it always bounces back to the focused textbox so to select another textbox I have to tap elswere to hide the SIP and select another textbox. (its annoying and user unfriendly) In a landscape mode though, I can scroll through the page easily (without bouncing) and select whatever I want with SIP up. I think it has to do something with a fact that in portrait mode without sip you can see all elements and in landscape you have to scroll down to see some textboxes. But if I look into some system apps I see similar pages and it doesnt bounce to focused textbox with the keyboard up, so I dunno what am I doing wrong.
Is there any workaround to correctly position dropdown from autocompletebox control from toolkit while it is declared inside of scrollviewer? Its position is always messed up, most of the time I tried to solve this it showed up over the textbox itself hiding it.
Thanks for your time.
I already did some research but didnt solve anything :-/
Could you please try my solution ?
https://siphelper.codeplex.com/
I would recommend you to read Alex's article on the subject. I think it should answer your problem just fine.
Not really. And you shouldn't have a AutoCompleteBox in a ScrollViewer.