I have worked around this with a simple copy and paste routine. I don't get the angst. The solution to NOT having this happen has 3 or 4 work arounds.

I'm positive that pg, like most other companies that have software, keep a list of problems that are annoyances, and that get almost NO reports, or just a few.

Programming resources dedicated to a large scale project such as this must be allocated where they have the most impact.

My workflow, when making a change such as you propose, has always included the saving of the piece under a backup name, and then rolling back the change when something goes awry.

This seems to be your personal annoyance, however I'd send an actual letter to Peter Gannon and ask his reply to your particular problem.

As implied, this has happened to me, and I have a workaround, and given that I'm onto the issue, there is no issue. Perhaps the only issue is I have not reported this myself, for the reason as stated above.

John Conley
Musica est vita