[active] and ***,window exec

Wil's icon

When I change 'title' to 'no title' using thispatcher - the [active] message bangs

probably there are other instances of this happening I haven't traced yet

I use [active] to trigger time sensitive events when I activate a patch

how can I stop thispatcher events from triggering [active] object?

Max Patch
Copy patch and select New From Clipboard in Max.

//

Also, window flags float 1 is causing the previous active patch to reactivate when using closebang on a subsequent patch

--open both patches - select one then select the other one - close the one that is selected and the previous patch becomes active--

If all windows are floating - is there a way to have 'none' [active] when closing any window?

(Or I guess have one 'non-funtional' default window that absorbs the [active] object when any random window is closed or not clicked on?) - that would be that Cadillac of possibilities - [closebang] had an attribute that routed it to [next.active] or [this.active]

is there such an object?

[this.active 1]

[this.active 2]

etc...

then when close one patch - send messages to other patches in order and layered

close_test 2.zip
zip 4.17 KB

//

jeez - thinking while writing - maybe the [closebang] -> [t b b b] 1. disables ALL floating in all patches - 2. performs necessary functions - 3 (with delay?) then re-enables floating ?

//

Ok - closebang - t b 0 - disable float of current patch (stops looking for other patch), then perform tasks with b [delay 10]. no need to refoloat - that happens when patch is loaded. -- not 100%

Roman Thilenius's icon

hm, float causes the window to float, so it is on top... i am afraid you will not come around a gate mechanism.

Wil's icon

its ok. seems I found a different solution

//

but the issue is expressed more clearly here

open 3 patches

if any one of the 3 are closed

the previous selected patch becomes active

someone may want 20 floating floating windows -> but only [active] message when patch is selected NOT when other patch is closed.

close_test 2.zip
zip 6.00 KB


//

Lets set up a performance situation where this would be if interesting usage - for use when macOS27 is released

[very small patches (finger sized) - no toolbars - no tile - just a panel with a color or comment with a word AND a small close button is visible- all internal stuff, messaging is hidden ]

single tap to activate - touch without release to drag around - double (or triple) tap to open and edit

:: open patch 1 - [active] sends messages to a synth

open patch 2 - [active] sends different message to a synth

click back on patch 1

continue opening patches

clicking different patches send different messages

eventually want to close some patches - too many patches open or want change configuration

DONT want previous patch [active]