well, you are generally and ideally right of course...
caveat is, qtractor doesn't have a domain -- never had, never will -- all files are general standard files, be that audio or MIDI files, whatever... none are actually claimed as qtractor's property... they maybe all shared across and to any other application, domain or else... even though you may create some in premises, so to speak, they are just yet another file-system entity, not quite owned by itself or any particular qtractor session, file or directory for that matter.
you actually found a corner case where qtractor may well cause data loss: like naming a .qtz file to an existing directory or folder name in where it will get saved... while opening that archive later may indeed replace that former directory mercilessly... besides, I am thankful for your spotting this potential hazard... it should and will be addressed in a near future, rest assured ;)
well, you are generally and ideally right of course...
caveat is, qtractor doesn't have a domain -- never had, never will -- all files are general standard files, be that audio or MIDI files, whatever... none are actually claimed as qtractor's property... they maybe all shared across and to any other application, domain or else... even though you may create some in premises, so to speak, they are just yet another file-system entity, not quite owned by itself or any particular qtractor session, file or directory for that matter.
you actually found a corner case where qtractor may well cause data loss: like naming a .qtz file to an existing directory or folder name in where it will get saved... while opening that archive later may indeed replace that former directory mercilessly... besides, I am thankful for your spotting this potential hazard... it should and will be addressed in a near future, rest assured ;)
thanks again
cheers