Diane

I am building a standalone for Windows out of a very large patch written on a Mac. It runs just fine on both Mac and Windows (tested with Windows 7 so far) but when you quit the program on a PC the entire screen starts flashing like the computer decided to go start a rave. Has anybody else ever seen this? I have found no mention of screen flashing on the forum. Is there some way I could get around this by using [closebang] to force quit the whole program before the flashing begins? I am on MaxMSP version 5.1.4 (42462), and this behavior persists whether I'm opening the program standalone or in Max. Any suggestions very appreciated, thanks!

Hi List,
I am building a standalone for Windows out of a very large patch written on a Mac.  It runs just fine on both Mac and Windows (tested with Windows 7 so far) but when you quit the program on a PC the entire screen starts flashing like the computer decided to go start a rave. Has anybody else ever seen this?  I have found no mention of screen flashing on the forum.  Is there some way I could get around this by using [closebang] to force quit the whole program before the flashing begins?  I am on MaxMSP version 5.1.4 (42462), and this behavior persists whether I'm opening the program standalone or in Max.  Any suggestions very appreciated, thanks!
-Diane


windows-screen-flashing-on-close

In case anyone else encounters this issue, I figured out that it is caused by jit.displays. Each instance of jit.displays used in Windows causes a screen flash when the object is either deleted or terminated when the program is closed. I am using Windows 7 and Max version 5.1.4 (42462). I made a minute long video documenting this odd behavior.

http://www.youtube.com/watch?v=cVOtvoiAwBg

Hi again,
In case anyone else encounters this issue, I figured out that it is caused by jit.displays.  Each instance of jit.displays used in Windows causes a screen flash when the object is either deleted or terminated when the program is closed.  I am using Windows 7 and Max version 5.1.4 (42462).  I made a minute long video documenting this odd behavior.  

Its a known "issue" with jit.displays, sorry for the inconvenience.

Hi Ben, thanks for the confirmation. No big deal, I found a workaround. However, would you mind advising me on one other Windows port issue? I can't suppress the status window in the standalone. I have only found 2 posts relating to this:

https://cycling74.com/forums/standalone-windows-how-to-suppress-other-windows

https://cycling74.com/forums/suppressing-max-window-display-on-standalones

And I am still having problems. I put in the [standalone] object and unchecked the "Status Window Visible at Startup." I have also deleted any "window flag nomenu" messages from the patch. No luck yet, any suggestions would be very appreciated.

Hi Ben, thanks for the confirmation.  No big deal, I found a workaround.  However, would you mind advising me on one other Windows port issue?  I can't suppress the status window in the standalone.  I have only found 2 posts relating to this:

https://cycling74.com/forums/standalone-windows-how-to-suppress-other-windows
https://cycling74.com/forums/suppressing-max-window-display-on-standalones

And I am still having problems.  I put in the [standalone] object and unchecked the "Status Window Visible at Startup." I have also deleted any "window flag nomenu" messages from the patch.  No luck yet, any suggestions would be very appreciated.


It should work fine, with the exception of the nomenu message issue, which can be worked around by using a deferlow between the loadbang and the message to thispatcher.

Can you strip down to a very simple patch that shows the problem?

It should work fine, with the exception of the nomenu message issue, which can be worked around by using a deferlow between the loadbang and the message to thispatcher.  

Windows Screen Flashing On Close