denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] problems with 1.1.2


From: Richard Shann
Subject: Re: [Denemo-devel] problems with 1.1.2
Date: Wed, 12 Feb 2014 12:52:04 +0000

On Wed, 2014-02-12 at 06:20 -0500, Bric wrote:
> I figured I should move this out to a new thread. (WAS:  "duration, 
> rhythm, metronome, etc., for MIDI-input?")
> 
> I compiled denemo version 1.1.2, seemingly OK.  After updating my glib 
> (downloaded glib 2.39.4 source, compiled and installed it)
> 
> But then there were issues big and small(er):
> 
> (1) Denemo is segfault-ing when edit preferences, although, on first 
> run, I think it was NOT segfault-ing.  I was able to uncheck "Highlight 
> the cursor", click OK, and it didn't segfault at that point.

at which point does it segfault? 

>   (BTW: 
> Hallelujah! end of forced scroll animation!  BIG BIG help.

well, it sounds like you haven't fixed the drawing problem on your
machine - how does it get on running gimp for instance?

>  Thanks)
> 
> (2) Contrary to what I was told in previous threads about copying my 
> .denemo-xxx/actions/actions/Default.commands and 
> .denemo-xxx/actions/Default.shortcuts :   copying just 
> "Default.shortcuts" is not enough to preserve all the laboriously 
> developed shortcuts.  One must apparently copy the Default.commands file 
> as well.  In a previous thread Richard or someone else warns against 
> copying over "Default.commands", saying that would mess up the command 
> set.  But if I don't copy it over I lose my shortcuts!

You should not need to do this any more. When you started the new
version (provided you had not externally created a directory
called .denemo-1.1.2 before launching the new Denemo) you get a dialog
offering to keep your settings.

What you can do in your circumstance is to copy Default.commands from
the new distribution and Default.shortcuts from your
old .denemo-xxx/actions directory. That should make all the commands
available while keeping your shortcuts.

> 
> (3) Typeset music failing to render a file that is rendered fine by my 
> old (current) denemo 1.0.9

This is usually caused by old LilyPond syntax that Denemo used to add
for default beaming that 1.0.9 added to files by default. Execute the
Score->Typesetter->Use Normal Beam Endings command to fix this. (If you
haven't got Default.commands from the distribution, you will need to get
that first as that menu is changed since 1.0.9 I suspect).

> 
> (4) More of a warning than issue, really:  Denemo xml files tend not be 
> backwards-compatible.  So, when I opened in 1.1.2 a pre-existing 
> *.denemo file generated/saved in 1.0.9, and FOOLISHLY re-saved it in 
> 1.1.2, I couldn't open it in 1.0.9 anymore.  Fortunately, apparently, 
> all I had to do was change the line
> 
> <score xmlns="http://denemo.org/xmlns/Denemo"; version="7">
> 
> to
> 
> <score xmlns="http://denemo.org/xmlns/Denemo"; version="6">
> 
> and that appears to have fixed the problem, this particular time.
That would not work in general, but may give you something useful.
Software generally isn't written to open yet-to-be-invented file
formats, for obvious reasons, so 1.0.9 will not read the newer 1.1.2
format.

Richard





reply via email to

[Prev in Thread] Current Thread [Next in Thread]