Forums > MaxMSP

Control + S has stopped saving, any ideas why?

January 12, 2009 | 10:47 am

This has happened on two different computers now, Control + S has stopped saving documents. A small niggle, but still quite inconvenient as I am a regular saver! Control works with all other shortcuts except save. Any ideas?? (on PC)


January 12, 2009 | 10:50 am

On 12 janv. 09, at 11:47, Ivan Redman wrote:

> This has happened on two different computers now, Control + S has
> stopped saving documents. A small niggle, but still quite
> inconvenient as I am a regular saver! Control works with all other
> shortcuts except save. Any ideas??

Platform? Do you have any error message in the Max Window? Make sure
that you have the correct permissions to write the patch.

ej


January 12, 2009 | 12:07 pm


January 12, 2009 | 12:12 pm

It’s on a laptop running Windows XP … When I click Save under the file menu it saves fine, it is just the shortcut that’s stopped working … and as mentioned, the other Ctrl shortcuts work fine. Strange huh?


January 12, 2009 | 3:57 pm

Install Max Toolbox?

Patch with a custom menu bar? (I think not, but just checking).

Customized keycommands.txt in /init/ ?

What else did you change? You seem to be running something in Max that is intercepting your Ctrl-keystrokes.


January 12, 2009 | 4:13 pm

Haven’t actually edited any files, or installed anything new. It is seeming rather odd, the only thing I am changing is the object defaults, but that wouldn’t affect the keyboard shortcuts I wouldn’t have thought… I’ll check the keycommands.txt file.


January 12, 2009 | 6:25 pm

On Jan 12, 2009, at 4:07 AM, Mathieu Chamagne wrote:
> "command + < " (change focus to next windows of current application)
> has stoped working only in max 5 a couple of weeks ago…

Windows that use the built-in web browser eat this key command (at
least they eat the similar CMD-` on the Mac). If you close any windows
that have the web browser in them it might work again. Annoying, but
true.

- C

Chris Muir
cbm@well.com

http://www.xfade.com


January 13, 2009 | 7:30 am

Well it seems to have fixed itself. How strange…


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