Are you sure? How are you determining this? What OS? I just tested on Windows 10 by doing the following:
1) Open a score
2) make a change
3) switch to continuous view
4) switch to another program entirely and begin working in
5) open Windows Explorer and navigate to the autosave folder
I waited well over two minutes, and no new autosave file has appeared in the autosave folder (I refreshed to be sure), nor has MuseScore "topped" itself as it generally does if autosave kicks in while in continuous view*. I then turned autosave back on, and sure enough, two minutes later, MuseScore "topped" itself and the autosave file appeared.
*Actually, in the past, it actually caused to window to literally appear on top of whatever I was working on, now it simply flashes the icon at the bottom of the screen to indicate pending activity. Not sure if that is new with 2.1 or if it's been that way a while - I don't use continuous view all that much.
Comments
Are you sure? How are you determining this? What OS? I just tested on Windows 10 by doing the following:
1) Open a score
2) make a change
3) switch to continuous view
4) switch to another program entirely and begin working in
5) open Windows Explorer and navigate to the autosave folder
I waited well over two minutes, and no new autosave file has appeared in the autosave folder (I refreshed to be sure), nor has MuseScore "topped" itself as it generally does if autosave kicks in while in continuous view*. I then turned autosave back on, and sure enough, two minutes later, MuseScore "topped" itself and the autosave file appeared.
*Actually, in the past, it actually caused to window to literally appear on top of whatever I was working on, now it simply flashes the icon at the bottom of the screen to indicate pending activity. Not sure if that is new with 2.1 or if it's been that way a while - I don't use continuous view all that much.