suspend object broken ?

    May 28 2006 | 4:45 pm
    wouldn't the [suspend] object output "1" when maxmsp (or a build standalone) is brought to the foreground ? and a "0" when it is hidden ? ...
    am i completely missunderstanding the object ? it does not output anything at all for me? broken ?
    cheers, t.

    • May 28 2006 | 5:17 pm
      Perhaps the [active] object is really what you are looking to use here.
      Cheers, Danny
    • May 30 2006 | 7:16 am
      active is about Max windows, suspend is about the application itself - quite a difference. I can confirm, it seems to be broken on OS X 10.4.6 Max 4.5.7....
      -- Stefan Tiedje------------x------- --_____-----------|-------------- --(_|_ ----|-----|-----()------- -- _|_)----|-----()-------------- ----------()
    • May 30 2006 | 7:37 am
      hi danny,
      thanks, for your answer. i know active and it works but suspend is really what i wanted ... but it doesn't work here.
      the helpfile also does - nothing ?
    • Apr 27 2013 | 10:11 pm
      Bringing this question back to the forums. Is there something I don't understand about [suspend]? Like, for example, what *exactly* it means for an applications to be suspended? The object does not seem to work. Yes, [active] works fine. Mac OSx 10.8.3 Max 6.1.2
    • Apr 29 2013 | 11:13 pm
      Sorry to ping this again, but curious whether [suspend] is not a functional object. Maybe it's still included in Max for backwards compatibility as it worked on an older OS? Any update to the documentation or on this forum would be helpful. Thanks!
    • Apr 30 2013 | 10:22 am
      According to its documention, [suspend] reports "Mac OS suspend/resume events. The behavior is emulated on Windows."
      The thing is, Mac OS hasn't been sending suspend or resume events since Mac OS X was introduced. Those events were only in the Classic Mac OS. I've seen some discussion indicating that this sort of thing is considered a security issue under Unix. In addition, an application does't really notice the difference between being frontmost and non-frontmost app under preemptive multi-tasking, not the way it did under the Classic Mac OS cooperative multitasking model.
      I'm not aware if there is even a way for an application to hack into this information under OS X (or, for that matter, any Unix OS).
      Given the discussion here and my own (brief) tests, it seems that [suspend] just sits there doing nothing. Still, that's better than millions of existing patches breaking.
      Nevertheless, it might be nice to have a note about what's (not) going on in the documentation. Gregory?
    • Apr 30 2013 | 3:41 pm
      Thanks for that info Peter! So it seems" Maybe it's still included in Max for backwards compatibility as it worked on an older OS?" was a correct assumption. Does seem like [suspend] documentation needs a facelift.
      For a Max user like me who would like Max to respond (ie by opening/closing a UI window) when it's brought to the front or sent back I guess Apple Script via [tap.applescript] might be useful, but not ideal. I appreciate the insight Pater brings to teh OS environment....