[active] doesn't update when window is closed


    Apr 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:
    Mac OS 10.4.8, Max 4.6.2
    Mattijs

    • Apr 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 04 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 05 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 05 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
      www.timara.oberlin.edu/GaryLeeNelson
    • May 05 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
      > www.timara.oberlin.edu/GaryLeeNelson
      >
      >
      >
      --
      www.centuryofnoise.com
      www.perevillez.com
    • May 05 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 05 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
      > www.timara.oberlin.edu/GaryLeeNelson
      >
      >
      >
      ----------------------------------------------------
    • May 07 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...
      --
      Stefan Tiedje------------x-------
      --_____-----------|--------------
      --(_|_ ----|-----|-----()-------
      -- _|_)----|-----()--------------
      ----------()--------www.ccmix.com
    • May 07 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