Just opened up my first solution in FMGO 16 and it's returning an error when it tries to run the "Set Allowed Orientations" script step.
Is this feature no longer supported?
Doesn't seem to be (on iPads). My best workaround is to have a script that is locked into a loop when in portrait mode, flashing a dialogue box stating that it will only work in Landscape. I think it has something to do with the iOS multi-tasking features. I've heard that it still works on iPhones.
Nope...it's no longer working on iPhone.
I guess the idea is to develop layouts that suit various screen sizes and styles... In an ideal world, when pulling another app in, your FileMaker layout should adapt to the new half screen, however, that isn't always possible or required.
The staff that I develop for tend to use the app in landscape, but some do flip and then wonder why they cant see half of the screen. Locking it would be a dream.
Yeah, unfortunately this has been in the deprecated list for a while:
Deprecated features being removed from FileMaker Next
I believe this is because Apple are removing this from iOS in general, but could be wrong
Set Allowed Orientations is not supported in iOS 9 | FileMaker
We're an iOS development shop and (while I'm still checking to be sure), the senior iOS devs haven't seen forced orientation on the deprecation list which means it should still be around for a while. It has MAJOR design implications and will change the landscape of app writing. We have some small clients that could never afford the money for the enhanced design to support both orientations and even with our large clients, we're talking a LOT of money to take some of our apps and create the design to support landscape so that it looks correct and polished. It's MUCH more than a matter of stretching auto layout objects.
If this support is truly gone in FileMaker Go, so will my support of iOS for ALL my commercial FileMaker software. I will NOT be developing layouts for portrait orientation and I don't even know how to trap that out in FileMaker if a user rotates their device while looking at a layout.
I would really like someone from FileMaker to weigh in on this thread and give us a detailed update on this subject.
On a iPhone, stretching is really all you need, but there are other options.
script trigger OnLayoutSizeChange and get(WindowOrientation)
I agree with Schamblee - for most layouts on iPhone, stretching does well for portrait and landscape - design for portrait and let it stretch to fill horizontal width if phone held horizontally. Usually need to do this anyway to cater for the various iPhone screen sizes.
For some iPad specific layouts I have either also used auto-sizing, or instead designed for portrait and then let layout sit centred when horizontal. Users quickly learn that it's better in portrait.
Why do you say you will never design for portrait mode? Surely at least on iPhone that is the most used and convenient orientation for the user..? Not many apps I use that are for horizontal - maybe some games and things like GarageBand but not many that's for sure....
Having said that, I do also wish it was still an option to lock either portrait or horizontal for layouts...
The bigger issue for me is users that are trying to view the interface while laying down on their side. It's a major hassle for these users.
In that case users will have to do what I'm sure they have to do for many other apps: turn on Portrait Orientation lock. It's pretty easy to access from the bottom menu.
I design full-scale business solutions that are primarily for desktop screens which are landscape. Certainly for iPhones, I have to design custom layouts, but for iPads the layouts are designed to work the same way as the desktop ones. EVERYTHING has to be changed to switch between the two. As I said, our company has designed some major iOS apps... I know what I'm talking about.
Regardless, none of these comments address the issue.
HOWEVER I design a layout, rotating the device breaks that design, unless you design in square layouts only which is utterly stupid to HAVE to do or unless there is some evaluation method I can use in Filemaker that when the device screen is rotated it will automatically switch the user to a different layout I've specified.
UGH! A Script Trigger (as mentioned above)... sigh... this is going to take so much time to build duplicate layouts for everything... why they wouldn't leave orientation lock in is BEYOND me.
I can understand the frustration to a degree as no one likes to lose a feature they are relying on but this has been in the post for a while:
Deprecation of 'Set Allowed Orientations'?
Set Allowed Orientations is not supported in iOS 9 | FileMaker
Things do not stay the same in the iOS world for long. And that's doubly true when you're relying not only on iOS but on a single app on top of that (FM Go).
If you are already part of an organization that has a native iOS app capability, it might be an idea to develop native apps that can interface with FileMaker databases as required. That way you retain more control over the software. If I had the ability to produce native iOS apps I don't think I would use FileMaker Go much.
So I'm not trying to be the hater in the thread, but while many things don't "stay the same in the iOS world for long," this is exactly my point... THIS has been a part of the iOS world from the very start and has. not. changed. There are a LOT of good reasons for this. Instead of just blindly saying "well they must have a reason," WE... the FileMaker community, needs to tell them, "Hey! FileMaker! It's going to cost us TONS of time to make two versions of every layout now!"
Building native iOS apps that interface with FileMaker is certainly doable... for 10's of thousands of dollars to start. The whole friggin POINT of using FileMaker for these apps is the ease of development. That's the strength of FileMaker. As I don't need to interface with external databases out of my control, really what you're saying here is, don't use FileMaker... all because they took out one really important feature.
PeterLauwers wrote: HOWEVER I design a layout, rotating the device breaks that design, unless you design in square layouts only which is utterly stupid to HAVE to do or unless there is some evaluation method I can use in Filemaker that when the device screen is rotated it will automatically switch the user to a different layout I've specified. UGH! A Script Trigger (as mentioned above)... sigh... this is going to take so much time to build duplicate layouts for everything... why they wouldn't leave orientation lock in is BEYOND me.
I could not agree more. The idea that we are expected to design iPhone layouts that look good in both vertical and horizontal orientations is insane.
alecgregory wrote: I can understand the frustration to a degree as no one likes to lose a feature they are relying on but this has been in the post for a while: Deprecation of 'Set Allowed Orientations'?Set Allowed Orientations is not supported in iOS 9 | FileMaker
I am running many apps on my iPhone that do not rotate...so obviously it is still possible. So what's the problem with FMGO16?
I guess there just wasn't the outcry over deprecation of this feature in the same way there was with, say, runtime deprecation so FMI saw no reason not to let it die after giving notice.
And I can understand the reason for the deprecation. FMI is owned by Apple > Apple make a recommendation > FMI implement it in their app. I think around the time this was done FMI were paying particularly close attention to Apple standards and Human Interface Guidelines (they had some Apple employees speak at DevCon on design, which doesn't happen often), and it could be argued that they were a little overzealous in this case.
Little comfort, I know.
jgalt wrote: alecgregory wrote: I can understand the frustration to a degree as no one likes to lose a feature they are relying on but this has been in the post for a while: Deprecation of 'Set Allowed Orientations'?Set Allowed Orientations is not supported in iOS 9 | FileMakerI am running many apps on my iPhone that do not rotate...so obviously it is still possible. So what's the problem with FMGO16?
Well, native iOS apps can be more flexible because they don't have to implement that particular Apple guideline. FileMaker Go, as a single app, does implement that guideline. You can argue that they shouldn't've done it, but the time for pushback was when it was announced.
In any case, since FileMaker Go is the same app on iPhone and iPad, I don't know how they would've fixed the split screen issue outlined in the second link I posted. Either they couldn't or they decided it wasn't worth the trouble.
Locking orientation is not something Apple has on their deprecation list. We have two developers heading to WWDC and they WILL be asking about this to be sure. It has tremendous ramifications on future development and will cause MANY MANY current apps to crash. Our iOS devs think I'm CRAZY to even suggest they could be considering this.
So as great as self adjusting layouts are, and I've made my share of them, it works MUCH better on small layouts or simple list oriented layouts. Large busy layouts simply do not work in a way this can be done... basically you really can't show more data than fits your shortest device width which means it will likely be inefficiently laid out in landscape.
Retrieving data ...