denemo-devel
[Top][All Lists]
Advanced

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

Re: [Denemo-devel] tablature status (August 2012)


From: Richard Shann
Subject: Re: [Denemo-devel] tablature status (August 2012)
Date: Wed, 08 Aug 2012 18:09:48 +0100

On Wed, 2012-08-08 at 18:43 +0200, Federico Bruni wrote:
> Il 08/08/2012 16:43, Richard Shann ha scritto:
> > On Wed, 2012-08-08 at 10:34 +0200, Federico Bruni wrote:
> >> Il 08/08/2012 09:51, Richard Shann ha scritto:
> >>> Well, with the versions up until 0.9.4 you would have gotten the
> >> last
> >>> bit of the file, the \score {} blocks in bold, and also any Denemo
> >>> directives like rehearsal marks, repeats, trills etc. These are
> >> editable
> >>> with the edits affecting the score (so there is a synchronization
> >>> between the LilyPond view and the Denemo display, quite hairy
> >> really,
> >>> though I have never managed to catch it out).
> >>> With the new score layout stuff only the stuff inside the music is
> >>> editable there, the non-music stuff is editable in the score layout
> >>> window.
> >>
> >> I would prefer to change the \score block in the LilyPond view (it's
> >> easier).
> > Well it is the same as doing convert to LilyPond and then editing it in
> > the score layout view.
> 
> Perfect: that's what I want
> 
> > (Apart from a bug on my system where the editor is not showing the text
> > cursor - if you can see the text cursor in the score layout view
> > LilyPond I would be interested to know that)
> 
> No, I can't see any text cursor: I must "guess" it and click often.
> It would be nice to have it fixed, because this is a really nice feature.
It seems to be a bug in gtk - if I enquire if the cursor is visible it
says it is. If I put the editor in a top level window, it is becomes
actually visible. Somewhere in the hierarchy of widgets a signal is
getting lost I guess. Do you have GTK2 or 3? I am hoping the bug is
fixed in GTK3.

> 
> >> Anyway, I can change the \score block in the score layout window,
> >> click
> >> on typeset and see the changes applied correctly. But when I close
> >> the
> >> window my changes are not saved: if I click on View>LilyPond I see
> >> the
> >> old \score block.
> >>
> >> I'm missing something?
> >
> > Either:
> >      the score allowed you to quit with the changes not saved, that is you
> > can change a score layout and the score fails to become unsaved (I think
> > I fixed all cases of this, please report if not)
> > Or:
> >      it is opening with the default layout as the selected layout, not the
> > one you customized. I think my intention was that the last selected
> > layout should be selected when re-opening a score (so that hitting print
> > without looking at the score layout view will print the last selected
> > layout). If not, you have to select this layout - note that when you
> > re-open a score the custom layout becomes pure LilyPond, the GUI is not
> > saved.
> >
> 
> It's the latter.
Mmm, are you sure, I was checking this afternoon, and it seemed to load
a previously saved file with the last used custom layout as the selected
layout. Perhaps you just meant that you saved while the default layout
was selected? (Mmm, in fact that is a snag - if you save with layout A
selected then select layout B print, etc, then quit without saving again
then on loading it up again, A will print out if you just hit print.
Well, perhaps that is ok).


> Now I understand: if you use File>Export as>PDF, the default layout will 
> be automatically used.
The Export as PDF is old code, it will create large pdfs with point and
click information in them, unless you turn it off. It should probably be
re-engineered to work via the current layout and to avoid point and
click info.
> If you want to print a customized layout, you must use View>Score 
> layout, choose the custom layout and click Typeset. Then print to PDF.
> 
> Anyway, I can see that the main view in Denemo doesn't reflect the changes.
By main view I guess you mean the Denemo display? That is never wysiwyg
- so a rehearsal mark is just represented by the mark A, regardless of
which one it is or which style will print. Of course, it would be
possible to script it to display something else, and even (via the
dynamic flag) to make them display A, B, C, refreshing at some scripted
interval or on some condition such as adding a new rehearsal mark. I am
guessing that is what you refer to below?

> Even if I do a simple change in View>Lilypond, such as:
> \set Score.markFormatter = #format-mark-box-numbers
> 
> The PDF is correct but Denemo keeps showing the letter
the letter A that is?
>  instead of box 
> number.

Richard





reply via email to

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