Multiple Window Navigation

[Matt Klein]

I am messing around with FileMaker 7/8's multiple window capabilities and have run into a bit of a quandry.

What I am trying to do is gather info about all the open windows. I chose, for lack of a better idea, to select each window in a looping script and populate a global field with an array consisting of the position and size of each window. This works great if all the open windows belong to the file from which the script was run. While the script successfully selects the windows that don't belong to the file from which the script was run, it doesn't gather the info about those windows.

I understand that it's a focus thing and that I would need to run a script in these other files, but I don't see how it can be done dynamically. In otherwords, how can you select the window in a looping script, tell what file it belongs to, and run a script in that file?

Anyone?

[-Queue-]

How about a series of Ifs that test Get(LayoutTableName) and perform the appropriate script based on its result.

[Matt Klein]

How about a series of Ifs that test Get(LayoutTableName) and perform the appropriate script based on its result.

It won't work. Even though the window is selected, no functions will return information on the window if it is not in the same file as the script that is running. What will be returned is the information on the last accessed window in the file from which the script was run.

[-Queue-]

Ah, I see. I guess this is another reason to use a central file, create File References to the others, and create layouts in the central file to display data from the other files. Then you can use the main file to hold all the scripts which only perform well within a single file.

[Matt Klein]

Ah, I see. I guess this is another reason to use a central file, create File References to the others, and create layouts in the central file to display data from the other files. Then you can use the main file to hold all the scripts which only perform well within a single file.

Yup, that is a good idea. I was trying to avoid that in this instance for reasons I don't really need to go into here, but you are right. That would be a better way to do this.

[Matt Klein]

Queue -

Do you know of any performance hits I would take if I were to work from a central file through Table Occurences to the data in a separate file?

[-Queue-]

I am definitely not the right person to ask about that. My company is still running 5.5.

Anyone? Bueller?