Snit
On 9/23/16, 2:28 PM, in article adhg93g0.gji@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:

Octavian W. Lagrange
Snit <usenet@gallopinginsanity.com>wrote:

Snit
On 9/23/16, 2:08 PM, in article slkabie.atee3@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:

...

Owl's new trolling nonsense is when he spoke of "Script1 inadvertently sends something to Script2's window" he did not mean Script2's window. LOL!

Octavian W. Lagrange
So when you say "the scripts windows are not even the ones beign discussed" you are not referring to whatever window (if any) that the script might have been executed in? If not, then which "script's windows" would *you* be referring to when you said that?

Snit
I am not talking about ANY of the script windows (other than the ones where the scripts are in)...

Octavian W. Lagrange
Oh so you mean those "scripts' windows" that aren't the "scripts' windows" because they "belong to the Terminal"? Is that the ones?

LOL!

Snit
Seriously, the more you talk the more you show how little you know. Some basic facts for you:

* Scripts can run in windows but they need not. Even if they do, though, they are not the ones being controlled, nor do they in any way "own" any of the windows which are being controlled by the scripts.

* The ONLY windows being controlled by these scripts are the ones from the terminal. In these cases the windows can be referenced by ID, index, and more but in NO case are they in a situation where another script cannot control them at ANY time, even in the middle of one script running.

This has been explained to you about a dozen times in a dozen ways... but still you say this:

Owl: ---- Script1 inadvertently sends something to Script2's window" -----

And then when asked what you mean you deny you mean Script2's window.