Version 1.3 not opening files created by 1.2
Files created by version 1.2 and described as type 'compressed mscz' will open in version 1.3 but there are a number of files described as 'mscz,file' which will not open and instead open a box indicating 'file extension mscz, not supported', then when exiting another box opens with cannot read etc.. bad file descriptor. This only happened after downloading and installing vs 1.3. Any help would be appreciated.
Comments
mscz, files (with a comma, and a dot) are not supported by MuseScore. You can rename them and delete the comma if you want MuseScore to open them. It's not linked to MuseScore 1.2 or 1.3.
The files with a dot and a comma are backup files and should be hidden. If they are not hidden is because your OS is configured to show hidden files.
In reply to mscz, files (with a comma, by [DELETED] 5
Files with names starting with a dot are not hidden in Windows, like in Linux (and I guess Mac too). And they don't have the hidden attribute set either.
But on Windows is quite common (because it is the default) that "known extensions" are not shown. This is IMHO the main reason why we see people attaching the <.name.mcsz,> files as often as we do see it, they simply don't see a <name.mscz>, just <name>
If these <.name.mcsz,> files should really be hidden, you'd need to turn on the hidden attribute:
FileSetAttr('.filename.ext,', faHidden);
In reply to Not hidden on Windows... by Jojo-Schmitz
Another argument to either make them hidden or change the naming scheme: the default sorting in Windows puts the "." files first, top of the list, and they are not hidden. So when people go searching for the file to upload, the one at the top grabs their attention.
In reply to Another argument to either by schepers
agreed, it seems an unfortunate set of circumstances leads to it being practically inevitable that Windows users will mistake the backup for the real file - it's not hidden, and period comes before letters in alphabetically order. I think the more appropriate thing on Windows would be to ditch the leading period. Then each backup would appear next to the corresponding real file, as opposed to all backups together up front ((which forces you to scroll through a potentially long list of backups just to get to the real files), and the real file would appear first within each pair (real, backup). That is, after all, the way it works in most other programs I've used that create backups.
In reply to agreed, it seems an by Marc Sabatella
I'd rather have them all in one spot, iasier to delete that way ;-)
In reply to I'd rather have them all in by Jojo-Schmitz
You'd still be able to do that, though - just resort your Explorer listing by extension.
In reply to Not hidden on Windows... by Jojo-Schmitz
Seems the place to add this Windows specific stuff (setting the 'hidden' attribute) is in ...libmscore/scorefile.cpp, around line 344, right after it renamed from name to backupName (step 3) and before saving the actual new file (step 4)
In reply to Seems the place to add this by Jojo-Schmitz
If the files are hidden on Windows, can you imagine how hard it would be to tell newbies how to find their backup files??? (Or even more experienced users.)
I don't think they should be hidden, but perhaps they should have some other naming convention to indicate what they are.
One possibility would be to tell Windows what they are, so that instead of being described as "MSCZ, files", they could "MuseScore backup files".
Fifist
In reply to If they're hidden... by Fifist
They are hidden now on Windows, as of 3dfba0a3
In reply to They are hidden now on by Jojo-Schmitz
Now my only concern is that these files will build up as MS doesn't delete them when the original is gone/moved. This feels like a no-win scenario.
In reply to Now my only concern is that by schepers
Not more than on Linux and Mac already. And no more than at most one backup per score.
In reply to Not more than on Linux and by Jojo-Schmitz
A difference is that Linux & Mac users may be more conditioned to expect the presence of such files and go around looking for them and cleaning them up periodicially. Or at least, the day the user does discover the comvention of hidden files prefixed with period scattered throughout his folders, he'll discover lots of programs create these - MuseScore won't strike him as doing something unusual. Although I don't know if many programs really use this convention for backup files - in my old Unix days, i'd have expected these would be configuration files primarily.
Windows of course does have hidden files too, but it doesn't tend to use them the same way or for the same reasons. And I've definitely never heard of a Windows program creating hidden backups. The comvention I a, most familiar with is as I wrote above - a normal file, same basename, no leading period, different extension (eg, foo.mscz woild have backup foo.bak, or foo.msck, or foo.msc$). I rather like "msc$” as it stands out as "weird" plus it will sort *after* the main filename, but still back to back so the user always sees both versions and it's pretty apparent which is which. I also see "Backup of foo.mscz", "foo - backup.mscz" and other variants.
I'd have to imagine there are OS guidelines for this kind of thing?
In reply to A difference is that Linux & by Marc Sabatella
Linux does not hide the extention, like Windows does by default. So now that these files are hidden, it won't happen that users keep uploading their ".mscz," files when being asked for ".mscz" files or otherwise confuse them for the real MuseScore files.
Thanks for your useful replies. Yes, they were the backup files and my daughter had transferred one of these to her pendrive at school, brought it home to work on and a minor panic ensued. Thanks again, we have both learned from this.