I have just tracked the bug down I believe, and pushed a fix for the case where the user has selected the "Default" profile. What happens is that a scheme script is run to initialize things for the users choice of profile. We stopped trying to maintain different profiles in releases but it seems that the windows build was using Default profile while the linux build uses Arranger (I think).
If you look at the ~/.denemo-1.1.1/denemorc file under <profile> you will see which .scm file is being run. Whatever that is it should end with a (d-SetSaved #t) to make the newly loaded file clean again. If you have some custom code being run, that file too needs to end with a cleaning call. I'll change this behavior so that it is not needed inside these initialization files. Richard On Wed, 2014-01-15 at 10:53 +0100, Andreas Schneider wrote: > Am 15.01.2014 10:47, schrieb Richard Shann: > > I have found a bug in this that is not present in the GNU/Linux build: > > when you do File->New the new file is already marked as needing saving. > > This means you cannot switch the input without saving it the empty score > > under some dummy file name (or executing (d-SetSaved #f) in the scheme > > window). > > I'm experiencing this behaviour under Linux also (my own build under > Debian). > > Andreas > > _______________________________________________ > Denemo-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
