Forums > MaxMSP

standalone doesn't seem to be working on windows

April 11, 2013 | 7:34 pm

hello everyone, trying to compile an app I’ve been making. It works fine on OSX but not on Windows. I don’t want the max window to come up so I’ve deselected status window visible at startup within [standalone]‘s inspector, I also want people to be able to close the top level patch so I’ve deselected can't close toplevel patchers. Once compiled, the windows version of my app doesn’t do either of these things, up pops the max window and you are unable to use the close button in the top right hand corner. Any idea where I go from here?

Many thanks in advance! :)


April 11, 2013 | 9:46 pm

try to use thispatcher and set "window flags close" maybe with a loadbang, i remember problems with a forced popping up status window if "window flags nomenu" is used. that was solved by using a deferlow between a loadbang and the window initializing messages to thispatcher.
i don’t know if that fits your problem but try to make the main patcher closeable with thispatcher first. O.


April 11, 2013 | 10:49 pm

Thanks very much for the reply! This has certainly resolved the close button issue. Any other ideas regarding the max window? That is the main issue really, can’t understand why this isn’t working.


April 12, 2013 | 12:16 am

you may have a message to max in your patch somewhere saying maxwindow which will open the max window (;max maxwindow)


April 12, 2013 | 7:22 am

@ Terry McDermott
Thanks for the input, just searched through the patch with `ctrl f’ no sign of that message unfortunately. Could anything else be opening the max window? I am getting a lot of warnings being posted to the window (yellow not red) regarding numbers I am passing to jit.openGL, not sure if those warnings are forcing an open? The warnings are of no detriment to my patch, everything else works perfectly.


Viewing 5 posts - 1 through 5 (of 5 total)