When I open my standalone the max console also launches even if I use the object [standalone @statusvisible 0] Any idea for the console to not open on the standalone?
Your help is much appreciated as I'm trying to figure this out for months.
I have a statusvisible 0 message sent to a standalone object. It was working fine for a while, but the console started to be displayed again after I added a "nomenu' to a message sent to a thispatcher object. I removed the nomenu message and the console is still displayed. Yes, the Status Window Visible option for the standalone object is also de-selected. Definitely a bug here.
You guys will not really get help, because You don't mention
either which max version, nor OS.
This forum is full of threads where things get asked taking it that
everybody else is sitting in front of that computer
and seeing exactly what is going on.
As on Mac there is no such problem,
You must be talking about windows version of Max.
And it has to be solved with messages to thispatcher for the main patcher.
Loadbang all window size, flags etc. message
After 1000 ms delay send :
window flags nomenu, window exec, front via deferlow to thispatcher.
Have a look at this screenshot as example.
I use screensize to get fullscreen, instead of fullscreen message.
This get sent to thispatcher.
toggle to inlet allows to switch between editing and "sealed" mode.
Sorry about that - Win 10 (latest update) and Max 8.1. I've attached a patcher that exhibits this issue. Build an .exe standalone and observe that the maxwindow opens on launch. The maxwindow does not open if I take out the 'nomenu' message being sent to the thispatcher object.
No problem, it is just allways better to include infos.
I don't use max 8.1 and so can't test that patch.
But for me, what I posted works till max 7.3.5.
The key is delay of 1000 ms.
You did not include that in the patch.
I mostly work on Mac, just compile stuff for windows
from time to time.
I prefer not to see menu, titles, status window etc.
Message statusvisible to standalone windows did
not work for me, I think because status
window is not part of mxf file, but part of the executable.
loadbanging that message is allway too late