get ( windowID )
a script step:
activate window; by ID [ $window_id ]
Why? When would I ever use more than one window? How should this work with card windows?
I used to use multiple windows. Now I rarely do.
If you never use more than 1 Window, maybe others will make it so.
But if anybody uses more than 1 window the only way now is to identify a window by a given name.
Most time it is ok.
But sometimes I change the name of a window everytime on record load to display the current record number with the window name. In those situations I like to have another mechanism to identify a window.
Thank you for bringing up this idea again; I have solutions where multiple windows are highly appreciated. There is a similar post already: Get ( WindowID ) function and related script steps
Could we somehow merge the votes?
I rarely use more than one window, precisely because we don't have a Window ID/window scope...
bigtom, all due respect, and you've had plenty of positive input in this community, but it always bugs me when your response to an idea is "Well I'd never use it so why should it exist" and then you vote it down. This seems to be a pattern with you.
How can you say "when would I ever use more than one window?". FileMaker supports multiple windows. I'd wager of the 2 million FileMaker developers out there (I made that number up but we all know whatever it is it's a big number), all of them but one (you) find multiple windows useful.
I believe the purpose of this voting is to vote up something you like, vote down something you really think is a bad idea and would hurt FileMaker, and for ideas that you just wouldn't use, just leave them alone. Again, all due respect, but that you voted this idea down because you never use multiple windows is frankly ridiculous. How can you be so narrow minded as to actively oppose other people's good ideas just because you don't happen to use the features that they'll benefit?
I'd additionally add to BigTom, IF FileMaker has a feature, like allowing multiple windows, the feature should either be PROPERLY implemented, meaning that maintaining integrity of the process, should be a minimum requirement. The fact that the feature of allowing multiple windows is already in there means this request for Get(WindowID) should be a very understandable request. I've avoided multiple windows for many, many years, but now I have a reason where it's a decided benefit and now I want to be able to use it and NOT depend on naming each window uniquely to be able to reference it. Someday YOU may decide that you have a reason for needing multiple windows and at that point wouldn't it be nice to be able to reference a WindowID?
Additionally, allowing a WindowID follows the methodology FileMaker has already embraced by assigning unique IDs to objects to guarantee unique accessibility to that object. LayoutIDs, TableIDs, RecordIDs, ValueListIDs... these are only some of the objects that this same principle has been applied to. It almost feels like an oversight that WindowID was missed.
We're not asking you to vote it up, but to purposefully vote it down, to me, only serves the purpose of hurting the other developers that have weighed in that correcting this would be beneficial to them.
I do hope someone from FileMaker reads this post, because voted up enough or not, product integrity is always high on the list and finding a place where the integrity has been overlooked should be enough to push the solution, regardless of how many votes it gets.
P.S. Part of the feature of assigning unique Window IDs would be the ability to manipulate and select windows by this ID. Just being clear.
Retrieving data ...