bugDenemo - Bugs: bug #55166, Selecting fret board produces...

 
 

bug #55166: Selecting fret board produces broken lilypond output

Submitter:  None
Submitted:  Wed 05 Dec 2018 10:47:35 AM UTC
   
 
Category:  None Severity:  2 - Minor
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 05 Dec 2018 03:30:46 PM UTC, comment #3: 

A warning is now given on creation of empty single fret diagram staff.

Richard Shann <rshann>
Group administrator
Wed 05 Dec 2018 12:50:19 PM UTC, comment #2: 

Well, you can't have a fret diagram staff with nothing in it and no other staff. So you can start your melody and fill in the fret diagram chords later ok.

Richard Shann <rshann>
Group administrator
Wed 05 Dec 2018 11:07:17 AM UTC, comment #1: 

Ah, this is not as serious as it sounds - the score generates invalid LilyPond until you actually enter a chord. Then it works ok.
That is, you can't have a Fret Diagrams staff with no fret diagrams in it.

But it is very disconcerting, and needs fixing.

Richard Shann <rshann>
Group administrator
Wed 05 Dec 2018 10:47:35 AM UTC, original submission:  

Creating a staff for fret board chords results in an invalid score that cannot be typeset.

Simplest way to reproduce:

1. Create a new score
2. Select staff properties → FretDiagrams → On/Off
3. select guitar
4. Do a preview or export to lilypond

The resulting lilypond file is invalid.


Version:

Denemo 2.2.0 on Debian (2.2.0-1~bpo9+1) with lilypond (2.19.81+really-2.18.2-13~bpo9+1).


Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rshann (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-12-05 rshann StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2018-12-05 rshann Severity3 - Normal 2 - Minor
        StatusNone Confirmed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code