That would be a question for the AutoIt folks, wouldn't it?
Why not use the built-in script steps to change the window size?
FileMaker cannot change the Windows only application window in which all the other windows open.
Totally correct, I have an inquiry posted at the Autoit forum.
But, there's plenty of FMP people who use Autoit. Thought I'd give it a try.
If FileMaker inc. sticks to its "roadmap", the application window is slated to become a thing of the past.
I don't feel lag when running small autoit script less than 1MB. Do you have the .exe in local hard disk?
If you use container field to provide it to client hard disk, do it on onFirstWindowOpen etc. not the time to run it. And also run it on the trigger may worth to cache it.
Or, it can be the layout take the time to load. If the layout is complex, how about using empty layout that have same size and run autoit on it before go to target layout.
This seems like an interesting idea but I've never tried it and my initial searches haven't turned up anything useful.
Mind my asking if you have any preferred sources on this topic?
Thanks for the suggestion.
I have only help file of autoit.
I made "stay in memory" type auto it script for scanning window name. This can't be applied for your issue, that only changing layout.
For your issue, the autoit script need some sort of trigger to resize FM window, I thought of clipboard but not good, writing a small text file may be better.
AutoIt can listen tcp port but calling it from FM need launching another program (if you write "web server" with autoit, you can use "Insert from URL" in FM script).
How big your compiled script? Windows itself has disk cache, so if it launched once, after that it should be fast enough.
Seems like your point about the disk cache is the best thing I've read about so far. Maybe I'll just not worry about it.
That's an interesting point.
Does that mean that FMP won't be using 'child' windows within a parent application window?
I looked it up here.
Windows user interface update — Supports Single Document Interface (SDI) on the Windows platform instead of Multiple Document Interface. With SDI, all "Windows user interface update — Supports Single Document Interface (SDI) on the Windows platform instead of Multiple Document Interface. With SDI, all document windows are independent of each other."
That could be interesting.