Re: Automatic adjustment of staff heights in display

[Richard Shann]

On Wed, 2021-11-03 at 17:33 +, Richard Shann wrote:
> On Wed, 2021-11-03 at 14:35 +, Richard Shann wrote:
> > Thanks for the feedback.
> > On Wed, 2021-11-03 at 15:20 +0200, Lib Lists wrote:
> > > Hi, everything seems to work here well and smoothly. The
> > > automatic
> > > adjustment creates quite a big gap between staves, making reading
> > > multiple staves slightly uncomfortable to me. Is that done on
> > > purpose
> > > (for example in the future the possibility of giving more space
> > > to
> > > other elements, i.e. dynamics, hairpins etc.)?
> > Perhaps that was the idea (this is ancient code) - putting in a
> > hairpin
> > does not affect the spacing, so if the staffs were much closer by
> > default then things would start clashing when hairpins were added.
> > However, the placing of hairpins under the notes ignores the note
> > positions, so they already easily clash with the note heads
> > themselves.
> > I think it might be work just to have the default spacing rather
> > less,
> > I'll look into it.
> 
> It turns out you can already decrease the minimum distance between
> staffs via 
> Command: Score Properties Editor
> Opens a dialog to edit the score properties.
> Location: Object Menu ▶ Score
> Internal Name: EditScoreProperties
> 
> and choosing Edit Built-in Score Properties.
> 
> However the minimum is still quite large and anyway the choice isn't
> saved with the score. I've now made it possible to reduce this until
> there is only space for one leger line between the staffs and the
> choice is stored with the score.
> 
> I've discovered also that there is a command 
> 
> Command: Taller Staffs
> No Tooltip yet
> Location: Object Menu ▶ Staffs/Voices ▶ Display Effects
> Internal Name: TallerStaffs
> 
> which can be used in a script eg:
> 
> (d-TallerStaffs 850)

hmm, actually d-TallerStaffs doesn't respond to the parameter passed,
it does an increment of half a staff line or some such...

> 
> and a corresponding
> 
> Command: Shorter Staffs
> No Tooltip yet
> Location: Object Menu ▶ Staffs/Voices ▶ Display Effects
> Internal Name: ShorterStaffs
> 
> It would seem they are in the wrong menu as they affect all the
> staffs
> in the movement.

I've moved them to the movement menu now.

Richard

Re: Automatic adjustment of staff heights in display

[Richard Shann]

On Wed, 2021-11-03 at 14:35 +, Richard Shann wrote:
> Thanks for the feedback.
> On Wed, 2021-11-03 at 15:20 +0200, Lib Lists wrote:
> > Hi, everything seems to work here well and smoothly. The automatic
> > adjustment creates quite a big gap between staves, making reading
> > multiple staves slightly uncomfortable to me. Is that done on
> > purpose
> > (for example in the future the possibility of giving more space to
> > other elements, i.e. dynamics, hairpins etc.)?
> Perhaps that was the idea (this is ancient code) - putting in a
> hairpin
> does not affect the spacing, so if the staffs were much closer by
> default then things would start clashing when hairpins were added.
> However, the placing of hairpins under the notes ignores the note
> positions, so they already easily clash with the note heads
> themselves.
> I think it might be work just to have the default spacing rather
> less,
> I'll look into it.

It turns out you can already decrease the minimum distance between
staffs via 
Command: Score Properties Editor
Opens a dialog to edit the score properties.
Location: Object Menu ▶ Score
Internal Name: EditScoreProperties

and choosing Edit Built-in Score Properties.

However the minimum is still quite large and anyway the choice isn't
saved with the score. I've now made it possible to reduce this until
there is only space for one leger line between the staffs and the
choice is stored with the score.

I've discovered also that there is a command 

Command: Taller Staffs
No Tooltip yet
Location: Object Menu ▶ Staffs/Voices ▶ Display Effects
Internal Name: TallerStaffs

which can be used in a script eg:

(d-TallerStaffs 850)

and a corresponding

Command: Shorter Staffs
No Tooltip yet
Location: Object Menu ▶ Staffs/Voices ▶ Display Effects
Internal Name: ShorterStaffs

It would seem they are in the wrong menu as they affect all the staffs
in the movement.

Richard

Re: Automatic adjustment of staff heights in display

[Richard Shann]

Thanks for the feedback.
On Wed, 2021-11-03 at 15:20 +0200, Lib Lists wrote:
> Hi, everything seems to work here well and smoothly. The automatic
> adjustment creates quite a big gap between staves, making reading
> multiple staves slightly uncomfortable to me. Is that done on purpose
> (for example in the future the possibility of giving more space to
> other elements, i.e. dynamics, hairpins etc.)?
Perhaps that was the idea (this is ancient code) - putting in a hairpin
does not affect the spacing, so if the staffs were much closer by
default then things would start clashing when hairpins were added.
However, the placing of hairpins under the notes ignores the note
positions, so they already easily clash with the note heads themselves.
I think it might be work just to have the default spacing rather less,
I'll look into it.

Richard

> 
> Lib
> 
> 
> On Tue, 2 Nov 2021 at 19:57, Richard Shann 
> wrote:
> > 
> > I've overhauled the code controlling how much space is allowed for
> > staffs in the display. Except for the space above the top staff
> > (which
> > can be controlled as before with the mouse wheel or by setting it
> > in
> > the staff properties) the space allowed is now computed while the
> > staffs are drawn.
> > This is quite a radical overhaul of very ancient code - please
> > check
> > that nothing you use is broken by it.
> > 
> > Richard
> > 
> > 
> > 

Re: How to use a custom clef and custom chord symbol font

[Lib Lists]

On Tue, 2 Nov 2021 at 17:15, Richard Shann  wrote:
>
> On Tue, 2021-11-02 at 16:58 +0200, Lib Lists wrote:
> > Hi and thank you as always!
> > Comments below.
> >
> > On Mon, 1 Nov 2021 at 19:40, Richard Shann 
> > wrote:
> > >
> > > On Mon, 2021-11-01 at 18:01 +0200, Lib Lists wrote:
> > > > Hi,
> > > > a couple of questions:
> > > >
> > > > 1. I would like to use a custom G clef in my scores, in
> > > > particular
> > > > this one: http://lilybin.com/vxtdv7/1.
> > >
> > > That example can be done by pasting the text from the top to the
> > > \clefGScore line into the LilyPond Score Prolog:
> > >
> > > Command: LilyPond Score Prolog
> > > Inserts LilyPond syntax for include files etc at head of score.
> > > Location: Object Menu ▶ Score
> > > Internal Name: ScoreProlog
> >
> > In one of my scores (a collection of exercises consisting of many
> > movements) I'm using the Score Prolog to insert a long introductory
> > text between the main title (added via Score->Titles->Simple
> > Titles->Set Titles) and the first movement. I'd like if possible to
> > keep the Score Prolog free from other elements that I might change in
> > the future. Or better, is there another way to place the introductory
> > text, freeing the Score Prolog for the custom G clef?
>
> yes, having created it once you can go into the Score Properties Editor
> and click "Get Script into Scheme Window". Once you have this script
> you can change the tag to a suitable name (avoiding name clashes with
> any other command - prefix with Lib- or something) and while you are
> there reduce the  d-PutDirective ...-display tag "." to
> something shorter (I think the ScoreProlog command should truncate it
> really...). Then you can create a palette button or a command to
> install this and it will no longer be overwritten by a further use of
> ScoreProlog (it's that tag being different that causes it not to be
> overwritten).
> Note that the "Get Script into Scheme Window" makes a script that only
> installs the prolog if it is not already present, so don't be caught
> out if you are trying to write different versions of it as it won't
> overwrite, you would have to go in and delete the old directive. (The
> alternative is the "Create Button for Clone" which creates a script in
> a palette button, that script *will* overwrite).

Thank you so much, I will test this solution.

>
> >
> >
> > >
> > > as I have done in the example score attached.
> > >
> > > You could make the LilyPond syntax less monolithic by creating the
> > > definition of the variable \clefGScore using the command:
> > >
> > > Command: LilyPond Definition
> > > Create a definition at the head of the LilyPond output. This can
> > > then
> > > be referenced in the music. See LilyPond documentation.
> > > Location: Object Menu ▶ Score
> > > Internal Name: LilyPondDefinition
> > >
> > > and you *could* place the first bit which calls the define-markup-
> > > command procedure to the head of the LilyPond syntax but there are
> > > no
> > > ready made commands for that, you would need to write the Scheme
> > > (in
> > > the source code is the "examples" directory that has a Denemo Score
> > > with all the variety of placements that can be done for the
> > > LilyPond
> > > syntax but it would be a bit of a slog for you to sort that out...)
> >
> > I tried to find the Denemo Score you mentioned, but I could find only
> > one called AllFeaturesExplained, but I don't think it's the one you
> > referred to.
>
> http://git.savannah.gnu.org/gitweb/?p=denemo.git;a=blob;f=samples/AllDenemoDirectiveOutputs.denemo;h=af852cd91f02d0fdb55a2b5d0bc6f57799c3ac62;hb=HEAD
>
> is the Denemo score I meant.
>
> >
> > >
> > >
> > > >
> > > > 2. I'd like to use a Roman font family for the chord symbols, as
> > > > in
> > > > here: http://lilybin.com/x9shb7/1
> > >
> > > That's easier you can just use
> > >
> > > Command: Insert Lilypond
> > > Insert or edit a directive in the LilyPond music typesetting
> > > language.
> > > This can be used for extra spacing, transposing or almost anything.
> > > See
> > > LilyPond documentation for ideas.
> > > Location: Object Menu ▶ Directives
> > > Internal Name: InsertStandaloneDirective
> > >
> > > to insert the syntax
> > >
> > > \override ChordName.font-family = #'roman
> > >
> > > before the chords you want to appear in roman or whatever, as in
> > > the
> > > attached. Again there are more elegant ways (for the LilyPond
> > > view),
> > > but if you are not going on to edit the LilyPond you may not care
> > > to
> > > get involved.
> >
> > Thank you for this, it will work for now. However, thinking about the
> > future, I might want to keep all the visual customizations separated,
> > creating a sort of style sheet
> That could be a template or a Scheme script, or even Scheme written
> into the initialization script that is run whenever you open a file.

Thanks, good to know that there are those possibilities available.

Lib

>
> >  that I can change (for ex

Re: Automatic adjustment of staff heights in display

[Lib Lists]

Hi, everything seems to work here well and smoothly. The automatic
adjustment creates quite a big gap between staves, making reading
multiple staves slightly uncomfortable to me. Is that done on purpose
(for example in the future the possibility of giving more space to
other elements, i.e. dynamics, hairpins etc.)?

Lib


On Tue, 2 Nov 2021 at 19:57, Richard Shann  wrote:
>
> I've overhauled the code controlling how much space is allowed for
> staffs in the display. Except for the space above the top staff (which
> can be controlled as before with the mouse wheel or by setting it in
> the staff properties) the space allowed is now computed while the
> staffs are drawn.
> This is quite a radical overhaul of very ancient code - please check
> that nothing you use is broken by it.
>
> Richard
>
>
>

[bug #60898] Hidden staffs with cursor show the same as un-hidden staffs

[Richard Shann]

Update of bug #60898 (project denemo):

  Status:None => Fixed  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

A line of text explains the hidden status when the cursor is on the staff.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/