AbstractToolkit

i'm trying to get rid of the max window (the window that messages/errors are posted to) in a patch built as application.. but didn't find a way to do it yet.. yes you can disable it from the menu, but i wonder if there's a way to completely get rid of it, or control it from a patch (clearing messages for example or closing it)

Hi
i'm trying to get rid of the max window (the window that messages/errors are posted to) in a patch built as application.. but didn't find a way to do it yet.. yes you can disable it from the menu, but i wonder if there's a way to completely get rid of it, or control it from a patch (clearing messages for example or closing it)
thanks
Fabrizio


disabling-max-window-in-built-application

Use the standalone object and set the statusvisble attribute to 0,

> i'm trying to get rid of the max window (the window that messages/errors are

> posted to) in a patch built as application.. but didn't find a way to do it

> yet.. yes you can disable it from the menu, but i wonder if there's a way to

> completely get rid of it, or control it from a patch (clearing messages for

Use the standalone object and set the statusvisble attribute to 0,
Cheers
Roger

>
> Hi
> i'm trying to get rid of the max window (the window that messages/errors are
> posted to) in a patch built as application.. but didn't find a way to do it
> yet.. yes you can disable it from the menu, but i wonder if there's a way to
> completely get rid of it, or control it from a patch (clearing messages for
> example or closing it)
> thanks
> Fabrizio

On 25 janv. 09, at 14:03, Fabrizio wrote:

> i'm trying to get rid of the max window (the window that messages/ 

> errors are posted to) in a patch built as application.. but didn't 

> find a way to do it yet.. yes you can disable it from the menu, but 

> i wonder if there's a way to completely get rid of it, or control it 

> from a patch (clearing messages for example or closing it)

Add a standalone object, and uncheck "Status Window Visible at Startup".

> Hi
> i'm trying to get rid of the max window (the window that messages/ 
> errors are posted to) in a patch built as application.. but didn't  
> find a way to do it yet.. yes you can disable it from the menu, but  
> i wonder if there's a way to completely get rid of it, or control it  
> from a patch (clearing messages for example or closing it)
> thanks

@emmanuel: I did exactly as you wrote, but while this is perfectly working for Mac .app's it doesn't seem to work at all for Windows (7) .exe's

is there a way to get rid of the status window in Windows' executables?

otherwise I'll have to go hunting for [print] objects for a whole day... :(

is there a way to get rid of the status window in Windows' executables?
otherwise I'll have to go hunting for [print] objects for a whole day... :(

I don't have a windows machine to test it out right now, but to save you a day of hunting, just use the search function, and look for print ;-)

Have you disabled menus (window flags nomenu->thispatcher)? If so, you will need to deferlow a loadbang to this command. Does this patch work when you compile?

This is by design. On Windows, if there is no menu then you cannot do anything. So, when Max is launched if there are no windows that have a menu, Max will always show the Max window to give the user a chance to do something. But you can use the above trick to get around this functionality.

Have you disabled menus (window flags nomenu->thispatcher)?  If so, you will need to deferlow a loadbang to this command.  Does this patch work when you compile?

This is by design.  On Windows, if there is no menu then you cannot do anything. So, when Max is launched if there are no windows that have a menu, Max will always show the Max window to give the user a chance to do something.  But you can use the above trick to get around this functionality.

Thanks Ben, I haven't tried the trick yet but it looks like it's going to fit perfectly in my patcher since, as you guessed, I am indeed sending the "window flags nomenu, window exec" message to [thispatcher].

I'll drop one line in this thread as soon as I can test this precious trick :)

p.s. @EJ: the search function would be an excellent hound, but still I'll have to go picking each prey on my own! or could you suggest some good retrivier too? :D

Thanks Ben, I haven't tried the trick yet but it looks like it's going to fit perfectly in my patcher since, as you guessed, I am indeed sending the "window flags nomenu, window exec" message to [thispatcher].
I'll drop one line in this thread as soon as I can test this precious trick :)

p.s. @EJ: the search function would be an excellent hound, but still I'll have to go picking each prey on my own! or could you suggest some good retrivier too? :D


one other thing is that the print can be found by just double clicking in the line which was printed in the Max window. Might even be faster than typing print with the search feature.

one other thing is that the print can be found by just double clicking in the line which  was printed in the Max window. Might even be faster than typing print with the search feature.


ok, I tried Ben's trick and hereby confirm that it works!

I'm also glad I could keep all of my useful [print]s working in the shade... ;) I need to see their output but I wouldn't like the user to see it!

ok, I tried Ben's trick and hereby confirm that it works!
thanks Ben, it solved my problem.

any suggestion how to remove print window in max 6.1

Disabling Max Window in built application