Google| Subject | Re: Ping Owl: More examples of "window 1" |
| From | Octavian W. Lagrange |
| Date | 09/22/2016 05:43 (09/22/2016 03:43) |
| Message-ID | <ahjdgu003.ag4@perch.invalid> |
| Client | |
| Newsgroups | comp.os.linux.advocacy |
| Follows | Snit |
| Followups | Snit (6m) > Octavian W. Lagrange Marek Novotny (16m) |
Snit <usenet@gallopinginsanity.com>wrote:
SnitLOL!
OK, created / ran some scripts to show you the concept of window 1.
<https://youtu.be/PyKpARhOz4Y>
The scripts reference "window 1".. with the exception of the lines that say "do script" WITHOUT referencing it which create a new window. I have a script simple called "New Windows" that does this.You ridiculous blockhead. Thanks for demonstrating precisely why your code is broken. That behaviour is exactly what you *don't* want such scripts to do. You *don't* want to use "Window 1" as a reference, because it allows a focus change to change the target window.
You can see I run multiple scripts at the same time... each sending instructions to "window 1." They all go there. Does not matter what script sends the message... and I also click on different windows (have my mouse pointer show it by going inverse) and then what window is referenced by "window 1" changes. I also, at the end, close all windows and you can see the scripts that reference "window 1" fail... I have NO error capture or the like in these scripts.
As you have been told: it does not matter what script calls window 1... it is not as if one script owns that window. The window is a window of a different program and it is just accepting commands being sent to it... and when you reference it by "window 1" it just means the top window!
Hopefully this clears things up for you... we shall see.
Not shown: if I referenced the window by ID then then that would NOT be effected by which window was on top.
This is what it *should* do:
https://vid.me/HCwe
Focus changes have no effect whatsoever on which window receives the input.
09/22/2016-
