Abandon Reload?
I'm not sure if there's an actual need for Reload - it can lead to problems like this:
#10632: Part doesn't Reload, also creates .mscz, and empty tab
Do you still have an unanswered question? Please log in first to post your question.
Comments
Version 1. - 3996 XP.
I find a need for reload more often than rarely.
For example. sometimes a chordname will not delete (apparently) until a reload.
There are also style changes that do not take place until after a reload, so I would like to keep this facility.
Regards,
In reply to I use by xavierjazz
OK, thanks.
Maybe in the future these things will improve without the need to reload.
I dont like this function. Its not needed. There is an easy replacement by simply restarting mscore. The "start with last session" is made for this.
On the other side its hard/expensive to implement as there are lots of special cases. I also doubt a casual user knows what "reload" does. Its a low level, very technical concept.
My proposal is also to remove "Reload".
In reply to I dont like this function. by [DELETED] 3
to keep this feature. Rebooting MuseScore takes much longer. Please wait until the issues that cause a need for this feature are fixed.
I am sure there are many features which casual users do not understand, but that is no reason to remove them.
As far as I can tell, this feature is not causing a problem - why remove it?
Regards,
In reply to I ask again by xavierjazz
The original topic links to the issue that prompted this question.
In reply to The original topic links to by chen lung
1. It seems that your stumbling on this was through trying to push MS beyond most normal usage.
2. It seems to me that it would be better to fix the problem rather than remove a useful feature.
Regards,
In reply to Well, 2 points: by xavierjazz
Using the nightly builds, do you still need reload to do things like delete a chord name or for style changes to take effect?
Fixing the issue I reported would indeed be better, yes.
In reply to I dont like this function. by [DELETED] 3
Can you explain the basic programmatic operation of reload? Isn't it supposed to abandon the presently open score & edits and reload the file?
In reply to Explain reload by schepers
but when you invoke reload it gives the option to abandon or save before reload.
Regards,
In reply to It can be used this way, by xavierjazz
That's the part that makes "reload" a strange command, to me in the same league as "Save as copy" - commands I don't see a need for but some do. If you don't save the changes, it will reload the original, but if you do, you don't get the chance to rename (so the changes are saved to another file) and the original is destroyed, negating its usefulness.
To me, the program logic behind Reload should not be that hard, but maybe the implementation inside of MS is different than what I expect. That's why I asked Werner what MS actually does when Reload is invoked (or what it was intended for) and why it is so problematic.
In reply to Explain reload by schepers
Reload allows to abandon all changes made in the current session and "start over" with the copy on disk.
Saving and then reloading makes no sense.
There are some special cases which are possibly not handled right: scores with parts, new created scores and the interaction with the autosave mechanism.
A more sophisticated solution would be to implement a full blown revision system (for which some hooks are already in the code). This would allow to define arbitrary revisions (at least every session would create a new revision) and to go back in history.
In reply to reload by [DELETED] 3
Either I don't do very complex scoringwhich requires revision control (which is likely) or my experience over the past 30 years with many applications has given me a more jaded view of things as I tend to do things very old school. If I need to keep track of file revisions, I will periodically save what I am doing to a new file so I have a logically ordered file chain, properly numbered or dated, etc. If I want to abandon what I am doing, I close without saving and open a previous version. That way _I_ know what is happening and am not leaving things to some multi-facted program command.
I vote to remove it as well.
In reply to Experience by schepers
I have been writing a number of lead sheets.
I have had to use reload at least 15 times because of the score not displaying properly after doing things like:
1. removing a chordname.
2. raising or lowering a note via the up/down keys.
I may be the only one but I NEED this function until these artifacts are fixed.
XP Pro, r3996.
Regards,
In reply to This past week by xavierjazz
How about we keep it until you (and others) agree we don't need it then :)?
In reply to How about we keep it until by chen lung
I agree that, for the time being, due to artefacts (modifications that doesn't show) it is useful to have this commande reload, which I use only as a refresh.
In fact this comande exists in a lot of programms
Anytime you apply something that would require Reload to see it, shouldn't the screen/page update automatically?
In reply to Anytime you apply something by chen lung
but I still have a number of instances where it doesn't.
In reply to It should by xavierjazz
Right - could you list a few examples, or maybe create a report :)?
In reply to Right - could you list a few by chen lung
another example: http://musescore.org/en/node/12633#comment-42789
EDIT: Here's another example: http://musescore.org/en/node/12464
I have mentioned these problems in a number of posts, but never grouped them. I am in the process of making a list of these and also a list of interface improvements I would like to see.
Thanks, and regards,
Regards,
In reply to Here's by xavierjazz
I think most of the things requiring reload that involve text have mostly fixed themselves with the new text handling in 2.0, although I haven't checked that lately.
In reply to I think most of the things by Marc Sabatella
would be great. It is time consuming to constantly have to reload,
Regards,