-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orientation Modes - prevent Landscape? #25
Comments
The issue you're having doesn't have anything to do with this Module. You set your supported orientation modes in your tiapp.xml file like so - http://d.pr/i/jtvC Please read the appcelerator documentation - http://docs.appcelerator.com/titanium/3.0/#!/guide/Orientation - they're extensive and very helpful. |
Thanks for the link, but I tried that already, of course ;) Removing
from tiapp.xml does not prevent the drawer and its contents from switching to a landscape mode. My use case is the following: I want to prevent any landscape mode for everything inside the Drawer (center window and sidebars). But I also want to be able to open a new window (e.g. a videoplayer) and allow landscape modes for this specific window. Is this possible using this module? |
Well, removing those from your tiapp file should inhibit your app from rotating to either of those orientations completely. Have you tried cleaning your build after updating your tiapp file? |
Yes, I ran |
After some digging into the module's source code I noticed that there is an undocumented parameter orientationModes that can be used inside createDrawer(). There is also a setter method. |
Nice find! Put in a pull request with an updated readme and or example app.js and I'm sure @viezel would consider accepting it. |
super! |
Is there a way to prevent the app from going into Titanium.UI.LANDSCAPE_LEFT and Titanium.UI.LANDSCAPE_RIGHT mode? Unfortunately, assigning orientationModes = [Titanium.UI.PORTRAIT, Titanium.UI.UPSIDE_PORTRAIT] to leftWindow, centerWindow, rightWindow does not lead to success.
The text was updated successfully, but these errors were encountered: