@Nige_S and @DanThomas, thanks very much for your posts!
This seems to work quite nicely. I'll continue to test and likely include in Version 3.0 of Scroll to Top or Bottom of Macro.
Group.kmactions (4.0 KB)
The checks are in the mail!
@Nige_S and @DanThomas, thanks very much for your posts!
This seems to work quite nicely. I'll continue to test and likely include in Version 3.0 of Scroll to Top or Bottom of Macro.
Group.kmactions (4.0 KB)
The checks are in the mail!
Cool. As an aside, and I'm no AS expert, but I'd do the long "tell" path like this:
set value of scroll bar 1 of scroll area 3 of splitter group 1 of group 6 of window 1 to 1
I think it's easier to read and digest, although I suppose that's debatable, but it's more concise and easier to pick out the index numbers. But again, I'm a JXA guy, not an AS guy, so take it with a huge grain of salt. I could certainly see arguing the opposite of what I've just said.
And of course, now that I've written this, I'm questioning it, but I'll post it anyway.
If you can combine those into one action you'll save a few ticks from not having to instantiate AS twice.
Erm, me too usually. But @ccstone once suggested I use the "verbose" form to make the UI element nesting clearer to others -- and who am I to argue?
I agree - if the GOAT @ccstone says it, then who am I to argue?