[Rwp] my early work with sfz player using a dedicated process so opening up in another window

[Chris Belle]

If anyone wants to mess with this, here's my auto-hot script I did years 
ago probably around reaper 4 for the sfz player.
I will include source ahk file so spots can be adjusted if necessary.
You do need to run this one with the plug-in opened in a dedicated 
process, ie in a separate window.
I tried to get this to work from the fx window with the sfz window in 
there, but I could not, not sure what all the differences are yet, but I 
know it works with the separate window.
I want to make some comments about what I've noticed working with golden 
cursor as well.
When I was trying to re-produce what I had done with ahk in golden 
cursor, I noticed that even in the separate window, my cordinates were 
way different than what I had with ahk and window-eyes and jaws.
they are reporting on the actual window of the dedicated process I think 
while golden cursor is still using reaper as a reference, so it's almost 
like that window is still in the fx window.
Golden cursor can't get a reading from the bridged window the plug-in 
opens in, but funnily enough, autohotkey can.
Wen I tried to save spots using golden cursor it kept erroring out, once 
it couldn't find the spots file, then it saved it in my old reaper file 
which i made in the first place, another time it did something called 
explorer.
so there is some crazy jiggery pokery going on as Scott says,
ha.
Now maybe autohot doesn't have to search for an actual window but can 
ping in on the title bar,
I know that program is pretty sophisticated, I did pretty good with it 
for my skill level with coding, but the deeper elements of it are beyond 
me, it comes with some sniffer tools,
I have sniffed out controls and such and done some primitive object 
oriented programming, calling control names instead of just clicking on 
a pixel, and calling other executables, I built a little program
to un-mute the sound card which is just a brute force thing that turns 
on your sound card, and pushes volumes up and even runs narrator, just 
to get myself out of trouble, the difference in this thing and others is 
you don't have to install it.
But I am not a serious programmer, but if I can I like to use these 
little helper tools to help myself and others, and I've even sold a few.
but right now
as far as I can tell, the bridged window in separate process is not 
compatible with the non bridged version in the fx window, I'll have to 
poke around to see if some sort of off-set is happening,
becaus when I used golden cursor,
it did actually kick me off in the other window as if I were there.
Even though it can't see the window title if I actually go in there,
and doesn't work, if I stay in reaper, it will kick me off in the other 
window as if it were still in the fx window I hope I haven't confused 
everybody too badly.
This whoe thing is confusing, I'm just trying to figure out what works 
with what, but right now I know this.
My ahk script works if I put sfz in the separate dedicated process window.
And it can trigger on the fact that sfz is in the title name.
I have golden cursor working if i do it standard sfz in the fx window 
way, and then it creates a file called reaper.gc
so it's triggering on reaper itself,
which I suspect is not the top level window name but the main 
application window name,
when I tried to save things in golden cursor while in the bridged window 
in separate process thing, it did weird things, and nothing consistant, 
so there you have it.
Jamie, I do realize now the point you were making, that the plug-in 
window may not have a name, and it is in a wrapper and that is probably
the window name, I hope I got it right now,
you and snow man
understand the programatical elements
a whole lot better than I do, I'm one of these people just trying to 
find out what works,
and go with it, but here's another funny thing I can't figure out why 
it's not working.
I can not make autohotkey work in the non bridged mode at all, even when 
I take out the window criteria,
or put in what's in the title bar in the fx dialogue, or what I can see 
of the sfz window below it,
it won't run.
I can tell because even if I click something with a macro in the wrong 
place, it will tell me something happened, but nothing is happening.
I use jaws or window-eyes
when trying to make cordinates a lot of the time to find out where 
things are because NVDA doesn't have a native mode to tell the pixel 
distance in the window you are in, maybe I need to go grab that old 
mouse movement thing you wrote me a long time back, and see if it can do 
anything golden cursor can't, but
I know that jaws and wineyes will both translate to one another pretty 
well in the active window you are in.
So i tend to flop around from diferent readers to tell what's going on.
When we get a tool which can read from the top left of any given window 
whether child or parent, with NVDA then I won't have to do that anymore, 
but hey, Rome wasn't built in a day.
I was just rying to make some simple spots for peole and here we went 
down a rabbit hole, but I am learning so hey, that's good.
Thanks to both of you Jamie and snowman and your giant brains for all 
you do.