Forums > MaxMSP

[active] doesn't update when window is closed

April 27, 2007 | 4:00 pm

Hi,

[active] doesn’t output anything when its window is closed. It would be good if it outputs a 0 when its patcher is closed.

try here:

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#N vpatcher 439 451 635 614;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P newex 35 56 32 196617 print;
#P window linecount 0;
#P newex 35 34 38 196617 active;
#P connect 0 0 1 0;
#P pop;
#P newobj 80 75 54 196617 p isactive;
#P window clipboard copytext "p isactive" #E;
#P window clipboard copycount 1;

Mac OS 10.4.8, Max 4.6.2

Mattijs


April 27, 2007 | 4:09 pm

On 27 avr. 07, at 18:00, Mattijs Kneppers wrote:

> [active] doesn’t output anything when its window is closed. It
> would be good if it outputs a 0 when its patcher is closed.

It’s the intended behavior, you’ll have to look at the [closebang]
object, to know when a window is closed.

Cheers,
ej


May 4, 2007 | 12:47 pm

Quote: Emmanuel Jourdan wrote on Fri, 27 April 2007 18:09
—————————————————-
> On 27 avr. 07, at 18:00, Mattijs Kneppers wrote:
>
> > [active] doesn’t output anything when its window is closed. It
> > would be good if it outputs a 0 when its patcher is closed.
>
> It’s the intended behavior, you’ll have to look at the [closebang]
> object, to know when a window is closed.
>
> Cheers,
> ej
>
—————————————————-

Ah, thanks.

Don’t you think it would be more intuitive if the active object outputs a 0 when the window is closed? After all, the window is not active when it is closed..

Mattijs


May 5, 2007 | 11:23 am

Mattijs Kneppers schrieb:
> Don’t you think it would be more intuitive if the active object
> outputs a 0 when the window is closed? After all, the window is not
> active when it is closed..

I don’t agree, though it seems "logical".
Intuition is strongly linked to your knowledge, and might be
counterintuitive from a different perspective…
With a solution using closebang in mind, the existing behavior is much
more flexible, because you can distinguish a window moving to the
background from a window being closed. I prefer the way it is, the
workaround is simple enough…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


May 5, 2007 | 2:04 pm

This reminded me of an issue that I have learned to live with but I would
sure like to see it fixed. If the display windows for things like coll and
buffer~ (probably others) are open and the contents change, you must close
and reopen the windows to see what is actually contained there.

On 5/5/07 7:23 AM, "Stefan Tiedje" wrote:

> Mattijs Kneppers schrieb:
>> Don’t you think it would be more intuitive if the active object
>> outputs a 0 when the window is closed? After all, the window is not
>> active when it is closed..
>
> I don’t agree, though it seems "logical".
> Intuition is strongly linked to your knowledge, and might be
> counterintuitive from a different perspective…
> With a solution using closebang in mind, the existing behavior is much
> more flexible, because you can distinguish a window moving to the
> background from a window being closed. I prefer the way it is, the
> workaround is simple enough…
>
> Stefan

Cheers
Gary Lee Nelson
Oberlin College
http://www.timara.oberlin.edu/GaryLeeNelson


May 5, 2007 | 7:30 pm

yes, that would be a nice wish on the list of fixes.

On 05/05/07, Gary Lee Nelson wrote:
>
> This reminded me of an issue that I have learned to live with but I would
> sure like to see it fixed. If the display windows for things like coll
> and
> buffer~ (probably others) are open and the contents change, you must close
> and reopen the windows to see what is actually contained there.
>
>
> On 5/5/07 7:23 AM, "Stefan Tiedje" wrote:
>
> > Mattijs Kneppers schrieb:
> >> Don’t you think it would be more intuitive if the active object
> >> outputs a 0 when the window is closed? After all, the window is not
> >> active when it is closed..
> >
> > I don’t agree, though it seems "logical".
> > Intuition is strongly linked to your knowledge, and might be
> > counterintuitive from a different perspective…
> > With a solution using closebang in mind, the existing behavior is much
> > more flexible, because you can distinguish a window moving to the
> > background from a window being closed. I prefer the way it is, the
> > workaround is simple enough…
> >
> > Stefan
>
>
> Cheers
> Gary Lee Nelson
> Oberlin College
> http://www.timara.oberlin.edu/GaryLeeNelson
>
>
>


http://www.centuryofnoise.com
http://www.perevillez.com


May 5, 2007 | 8:01 pm

For windows as coll ones and others it could be fine !
For buffer~ , under maxmsp 4.6 content refreshes when "replace" message is sent (window keeping open).


May 5, 2007 | 8:23 pm

Would be nice. But only optional, of course, as it would use a lot of resources.

Mattijs

Quote: Gary Lee Nelson wrote on Sat, 05 May 2007 16:04
—————————————————-
> This reminded me of an issue that I have learned to live with but I would
> sure like to see it fixed. If the display windows for things like coll and
> buffer~ (probably others) are open and the contents change, you must close
> and reopen the windows to see what is actually contained there.
>
>
> On 5/5/07 7:23 AM, "Stefan Tiedje" wrote:
>
> > Mattijs Kneppers schrieb:
> >> Don’t you think it would be more intuitive if the active object
> >> outputs a 0 when the window is closed? After all, the window is not
> >> active when it is closed..
> >
> > I don’t agree, though it seems "logical".
> > Intuition is strongly linked to your knowledge, and might be
> > counterintuitive from a different perspective…
> > With a solution using closebang in mind, the existing behavior is much
> > more flexible, because you can distinguish a window moving to the
> > background from a window being closed. I prefer the way it is, the
> > workaround is simple enough…
> >
> > Stefan
>
>
> Cheers
> Gary Lee Nelson
> Oberlin College
> http://www.timara.oberlin.edu/GaryLeeNelson
>
>
>
—————————————————-


May 7, 2007 | 3:29 pm

Mattijs Kneppers schrieb:
> Would be nice. But only optional, of course, as it would use a lot of
> resources.

Feature request fulfilled (at least as usable workaround), any message
to the coll will close and reopen. Create your own debug modes…

#P toggle 118 76 15 0;
#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#N vpatcher 20 74 236 291;
#P origin 0 -15;
#P inlet 128 19 15 0;
#P window setfont "Sans Serif" 9.;
#P window linecount 0;
#P newex 50 66 50 196617 gate;
#P window linecount 1;
#P newex 50 88 55 196617 delay 100;
#P newex 50 110 69 196617 t open wclose;
#P newex 90 40 39 196617 t b l;
#P inlet 90 20 15 0;
#P outlet 50 137 15 0;
#P fasten 6 0 5 0 133 60 55 60;
#P connect 5 0 4 0;
#P connect 4 0 3 0;
#P fasten 2 1 0 0 124 131 55 131;
#P connect 3 0 0 0;
#P connect 1 0 2 0;
#P connect 2 0 5 1;
#P pop;
#P newobj 41 105 87 196617 p reopen coll;
#P message 60 76 50 196617 1 2 , 3 4;
#P button 41 76 15 0;
#N coll ;
#P newobj 41 139 50 196617 coll;
#P comment 137 76 100 196617 en/disable;
#P connect 5 0 4 1;
#P connect 3 0 4 0;
#P connect 2 0 4 0;
#P connect 4 0 1 0;
#P window clipboard copycount 6;


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


May 7, 2007 | 4:17 pm

Yes, that works, Stefan, but the window jumps back to its original position, and when it’s closed when you enter data, it opens nonetheless (it’s hard to keep track of this, since no output is generated when you open a coll manually).

Oh, and wclose wasn’t connected [/whine].


May 26, 2007 | 11:00 pm

Hi,

I know this is not a genealogical site, but, are you by any chance related to my maternal grandmother, Truuske van der Graaf who moved to England after attending Cheltenham Ladies College in the early 1900s? She came from the Amsterdam area.

Thanks for your time,

Truuske Wright Odde


Viewing 11 posts - 1 through 11 (of 11 total)