Give developers access to windows' internal IDs and offer the ability to reference the Window ID in Script Steps, e.g. Select Window, Set Window Title, etc.
... and as a repetition number of a variable in order to get a window-oriented variable.
Actually we are forced to use Code ( Get ( WindowName ) ) but it is problematic if multiple windows have the same name.
I've always wanted a window ID separate from the window title/caption in order to manage windows programmatically.
Using the internal ID makes sense to me, though a possibly more idiomatic or beginner-friendly alternative would be a property set by the developer, similar to an object name (though this presents the possibility of duplication).
I think I prefer using the internal ID since it leverages existing window management code, but wanted to mention the alternative.
Code() function is a bad idea. It's just the ASCII number of the first letter of the window name, right?
the full name of window would be better for this.
PS: You can get an unique ID for window via plugin functions.
Code() returns the code for the full string (to a limit).
Code ( "Window Name" ) ≠ Code ( "WindowName" )
I came across this because I need a unique window id to efficiently manage OnTimer scripts. I support!
Would make window-related scripting a lot easier. Full support for this feature!
Totally indispensable and something that's been sorely missed ever since we went from single-window fp5 to multi-window fp7!
As I think I've mentioned in a comment to a related feature request some time ago, we would really also need a new storage scope "window", for both variables and fields, in order to make multi-window solutions work properly.
This feature is sorely missing in one of my current projects!
Retrieving data ...