Disabling Max Window in built application
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)
Use the standalone object and set the statusvisble attribute to 0,
On 25/01/2009 13:03, "Fabrizio"
> 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)
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".
@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… :(
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?
----------begin_max5_patcher---------- 565.3ocwU0zaaCCC8ryuBA0qYC1dMI6iKa+.1v14gh.EK5DMHSYHJmjsh9ee Rx1s1onIoqYaWjsej9IxmHotcRBekYOPb16Yemkjb6jjjHT.Ho66DdkXegVP Q23Hryr5G7oslbvdWDVBkfUa10anV3J1nv0KsPgqk+rYuNcJK65zviYyCq49 2Y2z8KJYjIO6uJqmlRC5PQEDs7IqRn6sfMUJTCtXTk8.nowcHZfDR8qHIY49 8sEt0S2Oqg13iyY2Drb2jIgkouLAgbBTJzFDXez+tqg1pH0JMvROlFEkkqyh J07zioQKRuHhT5wEIRrEjK86mODWJbNqZUiqshI4dAwyoQaDxUBbcnPP37Y0 .xS3hFoxPM00FqaPrjvKDnqPaHvYp0vVPGEEvRi9cyVvJspsvXR05cJTZ1Qh B2gFaHf.gsXimvMir3Og.jTFb7dL5PZrkHOkFakhHelUpz.MJKpsPY.89SgO K1ylw9pMzU.Xg28dWqTR0PgHBGK4tPEd8GDmtSLM93DUYu4+RqXLAtjsitMJ pqz5jBSdZTRl+tiJL4WDgI+4NiZZbN0ftyNCW8kfoQoIi+gvxUeKrBnrE4OR Uq.hDqgGIqs8erRsXMwPSEfMSYcfvdn3zEgK5j71Qdu8ID6m6EB4+EtPHFXb sBO7ByXxEvGKfjowVzSUeuD6g7SBjeNoeVoAG3T1He1njR.GNm1O+n1nPWWL 7DmlmaHkcFQzh+sgzhyJlxeAwj+i6l7a7P5IsC -----------end_max5_patcher-----------
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
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!
thanks Ben, it solved my problem.
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!
is broke with max 6.1
any suggestion how to remove print window in max 6.1