Mr. Banshee

How do i get rid of the toolbars when the patch is in fullscreen presentation mode? Unpinning them makes them still pop up when i scroll by. To my knowledge this never happened in Max 7 or at least my excitement for Max 8 is blocking any memory of it.

Also, when patch goes into fullscreen it doesn't block out the File bar at the top like it used to in Max 7. i like my patches to take up the whole screen w/ no option to see behind them until i exit fullscreen mode. Can i still do this? Hoping all these options are still there.

Loving Max 8, just some tiny stumbling blocks at the moment.

comment

bgcolor

thispatcher

message

number

toggle

How do i get rid of the toolbars when the patch is in fullscreen presentation mode? Unpinning them makes them still pop up when i scroll by.  To my knowledge this never happened in Max 7 or at least my excitement for Max 8 is blocking any memory of it. 

Also, when patch goes into fullscreen it doesn't block out the File bar at the top like it used to in Max 7. i like my patches to take up the whole screen w/ no option to see behind them until i exit fullscreen mode. Can i still do this? Hoping all these options are still there.  

How do i get rid of the toolbars when the patch is in fullscreen presentation mode? Unpinning them makes them still pop up when i scroll by.

max-8-fullscreen-how-to-get-rid-of-toolbars-file-bar

Thanks Andrew, that is very helpful! However, there must've been a way to do this in max 7 w/out the key command & w/out doing every single time i open the patch, since have never used cmd-8 before. Also, any idea how to get rid of the apple file bar at the top and dock when you scroll by them w/ the mouse? Again, neither were a problem in the patch i have been using for years, but i have forgotten what i did to get there.

Thanks Andrew, that is very helpful! However, there must've been a way to do this in max 7 w/out the key command & w/out doing every single time i open the patch, since have never used cmd-8 before.  Also, any idea how to get rid of the apple file bar at the top and dock when you scroll by them w/ the mouse? Again, neither were a problem in the patch i have been using for years, but i have forgotten what i did to get there.  

Ok, I thought that’s all it was because I tried your example patch, and full screen worked as expected after using cmd-8.

The toolbar state is saved with the patch, and set via the patch’s inspector. See “Show Toolbar on Open”. (Edited to correct mistake)

Ok, I thought that’s all it was because I tried your example patch, and full screen worked as expected after using cmd-8. 

#P message 211 169 131 196617 \; max showmenubar;

#P message 70 169 131 196617 \; max hidemenubar;

 Also, any idea how to get rid of the apple file bar at the top and dock when you scroll by them w/ the mouse?

#P window setfont "Sans Serif" 9.;
#P window linecount 2;
#P message 211 169 131 196617 \; max showmenubar;
#N comlet scheduler timing 1 - 20;
#P inlet 70 88 15 0;
#P window linecount 1;
#P newex 70 120 293 196617 select 0 1;
#P window linecount 2;
#P message 70 169 131 196617 \; max hidemenubar;
#P connect 1 1 3 0;
#P connect 1 0 0 0;
#P connect 2 0 1 0;
#P window clipboard copycount 4;

@roman , i am probably doing something wrong or describing my problem poorly, but the Apple File bar & doc still pop up when i have my patch in full screen presentation mode. This never happened in Max 7 so i'm not sure what changed.

@roman , i am probably doing something wrong or describing my problem poorly, but the Apple File bar & doc still pop up when i have my patch in full screen presentation mode.  This never happened in Max 7 so i'm not sure what changed.  

Feel like i am poorly describing my issue, so here is a video

Apple Menu & Doc Invading Max 8

Again, i never had this issue in Max 7 (or prior Max versions). My computer is old, even updated to El Captain to see if that would change anything, but it did not. This is just a minor inconvenience for such a majorly awesome software, so if you know the magic trick to prevent the apple file bar & doc from invading my fullscreen patch that is in presentation mode, i would be grateful. Thanks in advance.

Feel like i am poorly describing my issue, so here is a video 

 Again, i never had this issue in Max 7 (or prior Max versions).   My computer is old, even updated to El Captain to see if that would change anything, but it did not.  This is just a minor inconvenience for such a majorly awesome software, so if you know the magic trick to prevent the apple file bar & doc from invading my fullscreen patch that is in presentation mode, i would be grateful.  Thanks in advance.  

AlienMacInvasion.png

 👽   👽   👽   👽   👽      👽   👽   👽      👽  👽 

this change in behavior is the result of our support for macOS native fullscreen. this change is documented in the "Changes in the Max Environment" reference guide. If you are unhappy with the native fullscreen implementation, Max will use the old implementation if you disable the OS Sytstem Preference "Displays have separate Spaces", found in Apple menu > System Preferences > Mission Control

iu.jpeg

Thanks for this intel Rob! That worked!  

i wonder what happens when you dont use the "built-in" max fullscreen mode but do it on your own, i.e. use "regular" windows which are located at 0 0 or lower.

does the menubar still come down when you use the hide message? or does the hide message stopped working? i mean this new fullscreen stuff it is not really a new feature of macOS, it came at about 10.11 times isnt it

i have always avoided using the "built-in" fullscreen mode to avoid trouble with windows and macos upgrades (or max upgrades for that matter) - but when now even normal windows are beeing invaded by cupertinian occupists...

i wonder what happens when you dont use the "built-in" max fullscreen mode but do it on your own, i.e. use "regular" windows which are located at 0 0 or lower.

does the menubar still come down when you use the hide message? or does the hide message stopped working? i mean this new fullscreen stuff it is not really a new feature of macOS, it came at about 10.11 times isnt it

i have always avoided using the "built-in" fullscreen mode to avoid trouble with windows and macos upgrades (or max upgrades for that matter) -  but when now even normal windows are beeing invaded by cupertinian occupists... 

@roman never tried w/out the max fullscreen command, not sure if i know how to otherwise. What Rob recommended, disabling ""Displays have separate Spaces", at first didn't work for me but then for reasons unbeknowest to me it did. Maybe my computer was just moving very slow with updating the new commands? From the time of my first post on this topic i was on 10.10 Yosemite, once i was informed by Cycling74 that this OS is no longer supported i updated to 10.11, but at first i still got the invasion until Rob gave me the extremely helpful intel. So, now my patch goes true fullscreen, knocking at the invaders all together. Neither dock nor the apple menu bar pop-up anymore.

i am wondering, if i knew what Rob taught me beforehand, if i ever truly needed to upgrade my OS since everything else worked fine. i'm definitely not complaining, but we shall see if my geriatric computer does at some point (it's almost 10 years old...fighting against the planned obsolscence!).

@roman never tried w/out the max fullscreen command, not sure if i know how to otherwise. What Rob recommended, disabling ""Displays have separate Spaces", at first didn't work for me but then for reasons unbeknowest to me it did.  Maybe my computer was just moving very slow with updating the new commands? From the time of my first post on this topic i was on 10.10 Yosemite, once i was informed by Cycling74 that this OS is no longer supported  i updated to 10.11, but at first i still got the invasion until Rob gave me the extremely helpful intel. So, now my patch goes true fullscreen, knocking at the invaders all together.  Neither dock nor the apple menu bar pop-up anymore.  

 i am wondering, if i knew what Rob taught me beforehand, if i ever truly needed to upgrade my OS since everything else worked fine.  i'm definitely not complaining, but we shall see if my geriatric computer does at some point (it's almost 10 years old...fighting against the planned obsolscence!).

changing these macOS settings for sure work, but is not a max-solution, isnt it?

sorry for beeing a bit cryptic, will send you my patch in a sec ... since i have never tested it in 10.11+ it would be great if you do.

sorry for  beeing a bit cryptic, will send you my patch in a sec ... since i have never tested it in 10.11+ it would be great if you do.

 simply creates a blank panel style window while hiding the menubar with a message to max. the third, optional argument is the number of monitors you want to fill, default is 1.

you might want to add the screensize automatically using 

then you have a 100% replacement for "system" fullscreen, except that you cannot use a command/apple key combination to toggle it.

in case you close the window before you went back to normal mode, you should have the max message to re-activate the menubar ready somewhere.

an additional message to max menubar controller will give you the option to use fullscreen but still be able to show the menubar controlled by a certain action.

works in max 410 through 735, mac and win.

customfullscreen.zip

110.thisfullscreens simply creates a blank panel style window while hiding the menubar with a message to max. the third, optional argument is the number of monitors  you want to fill, default is 1.

you might want to add the screensize automatically using jit.desktop or screensize, then you have a 100% replacement for "system" fullscreen, except that you cannot use a command/apple key combination to toggle it.

in case you close the window before you went back to normal mode, you should have the max message to re-activate the menubar ready somewhere.

an additional message to max menubar controller will give you the option to use fullscreen but still be able to show the menubar controlled by a certain action.

works in max 410 through 735, mac and win. 

At first glance it's not working until i change the arguments to 1500 1500 (i have a 15" laptop), only then does it blocks out the menu bar & doc, but the smaller sized window does not do this. Cycling crew alluded to it no longer being an option to do soley in Max anymore... i will have to dwelve into this deeper later since i've been fighting sleep for too long, so now i'm gonna let it win for the moment.

At first glance it's not working until i change the arguments to 1500 1500 (i have a 15" laptop), only then does it blocks out the menu bar & doc, but the smaller sized window does not do this.  Cycling crew alluded to it no longer being an option to do soley in Max anymore... i will have to dwelve into this deeper later since i've been fighting sleep for too long,  so now i'm gonna let it win for the moment.  

aha, so the message to max doesnt work anymore - but if there is a window at 0 pixels height the menubar at least stays in background like we want to?

hidemenubar / showmenubar still work fine in max 8, as does resizing the window to the display dimensions. what i've noticed is that hidemenubar will not prevent the menubar from popping out when the mouse cursor is hovering near it, same for the dock. for this you need to use thispatcher fullscreen in the desktop mode described above.

if this is undesirable behavior please file a support ticket so we can get these logged and determine if a fix is needed.

hidemenubar / showmenubar still work fine in max 8, as does resizing the window to the display dimensions.  what i've noticed is that hidemenubar will not prevent the menubar from popping out when the mouse cursor is hovering near it, same for the dock. for this you need to use thispatcher fullscreen in the desktop mode described above.

i am not able to tell which way would be more "right" or "wrong"; that a fullscreen patch works the same way as it did 10 years ago (i.e. without the need to disable something in a macOS controlpanel) - or that fullscreen in max will do something which attempts to change the usual behaviour of modern macOS.

i´ve always hated that extra window bar in the windows version max4 - mainly because it was different from mac. but one day i just accepted that this is normal on windows...

to control a shell script for changing mission control settings on the fly from "within" a patcher/runtime should do it for most people.

i am not able to tell which way would be more "right" or "wrong"; that a fullscreen patch works the same way as it did 10 years ago (i.e. without the need to disable something in a macOS controlpanel) - or that fullscreen in max will do something which attempts to change the usual behaviour of modern macOS.

i´ve always hated that extra window bar in the windows version max4 - mainly because it was different from mac. but one day i just accepted that this is normal on windows...

to control a shell script for changing mission control settings on the fly from "within" a patcher/runtime should do it for most people.


Max 8 fullscreen; how to get rid of toolbars & file bar?