02-22-2011 06:09 AM
To force an application into landscape mode, the following must be added to <initialWindow> in your *-app.xml file:
If I create an *-app.xml for my WebWorks project, however, it's discarded by the compiler. To date, I've been opening my .bar file after compilation, extracting the *-app.xml the compiler creates, editing it, and updating the archive, but I suspect this won't be an option when it comes time to sign my applications.
What other options do I have?
Solved! Go to Solution.
02-22-2011 04:29 PM
We've actually been having discussions about this functionality today.. We are looking at a couple of solutions that would be built into the software.
For right now you may be able to try the following... (I haven't tested this one yet)
If you go to the "bbwp\AirAppTemplates\src" directory where you installed the WebWorks for PlayBook SDK you will find a file called WebWorksAppTemplate-app.xml
I believe this is the file we use as a template and then replace specific areas with information from your config.xml file.
Try making these alterations to this file and they may stick for you. Also note that making changes in here will affect all apps that you build with the SDK.
03-11-2011 08:08 AM
03-14-2011 12:42 AM
Has anyone tried to force portrait mode? I get about two thirds of the screen usable with the last third being light grey.
I've been away from development for a few weeks because of an earthquake and was hoping that there had been alot of progress on a few of these bugs. Its quite frustrating when you are already far behind schedual to come across these sorts of issues - of course the extension of the offer was a godsend.
03-14-2011 07:09 AM
I'm assuming you are referring to the PlayBook... If so, the PlayBook simulator does not yet support showing application's in portrait mode only yet.
04-19-2011 03:07 AM
This solution no longer works as of SDK v184.108.40.206. Compiler reports:
[INFO] Packaging the bar file
Error: AIR validation failed
error 103: application.initialWindow.autoOrients is an unexpected element/attribute
04-19-2011 07:44 AM
It is now a supported feature of the config.xml file for your WebWorks application. If you change it in your config.xml it should work fine.