I use the Ultimate Fullscreen extension for this. I set it to go to full screen and fit to height. Since the object isn't supported by iOS it has no effect on the exported project.
There's also the option to shrink the window size with the window control object at the start, so long as resize display to fit is selected.
DistantJ - Thanks - using the Ultimate Fullscreen extension, seems to do the trick! I seem to only need the Action: Misc>Apply Fullscreen settings to Windowed Mode, and that fits my screen without distortion. Also only required on the first frame of my app. Thanks again!
DistantJ - Looks like I spoke too soon! I use Active System Boxes as my UI Buttons and they can be hit even when mouse as not over them (I assume they still think they're stretched wider?) Might be the same for other objects and clicking. So looks like I'll just have to live with the squashed look on PC and check it looks correct on iOS devices.
Well, even without Ultimate Fullscreen object the Active System Buttons click positions are misaligned if the screen is squashed. So looks like I can't go to 640x960 if my screen height is lower than 960. I'll have to compromise at 512x768 or something!
That's weird. A friend of mine made an app in MMF which was portrait, what he did was he implemented a scrolling system which was PC only - if the mouse went below the bottom of the screen it would scroll down, sort of thing, and this scrolling system disabled itself when on iOS (the best way to do this is to add +[iOS] Device Model is equal to "" to any events you want to be PC only).
DistantJ - Thanks for your help, but using the iOS Object, Device Model="iPhone" on my PC (in theory, somebody could use this name on an actual device!) Not sure if this is something that ClickTeam have changed in a recent update, or should I be using the iOS Get Device Extension: http://community.clickteam.com/showthread.php?t=70953 (this gives rawInfo as "i386" rather than "")
Strange, on mine, device model comes up as "" on PC... Unless they have changed it?
Interesting... I'm running MMF2 build 256.31 (I think it's the latest iOS Export Beta, but difficult to tell with a few updates to MMF2 that supposedly only had HTML5 stuff?)
Why not use a Global String, or better, a Global Value to differentiate between the various runtimes? Just don't forget to update it before building/running.
While poking around in the runtime's code for help with extension development I spotted that the mobile utilities object is supported by iOS, it doesn't do much but the condition "Is mobile" returns YES on iOS, so you could use that and negate it.
Posting Permissions
