Re: hideNotes in tablature
Am 15.04.2012 12:06, schrieb Federico Bruni: Il 15/04/2012 11:00, James ha scritto: Federico, it seems you have the ability (and knowledge) to create a tracker yourself so I suggest that if issue 1459 is fixed you change the label to fixed - someone else will verify - and then create a new tracker for the enhancement - whatever it is. Else whoever comes back to the old tracker has to puzzle their way through and often this puts people off (unless you yourself are going to work and create the patch). Yes, issue 1459 is fixed. How can I change the label to fixed in the tracker? The patch itself is very easy and I could create it, but I think that I'd better just create the issue in the tracker. Here it is: http://code.google.com/p/lilypond/issues/detail?id=2480 Hey Federico, if you create a patch, I think you can remove the Stem #'transparent = ##t in the definition of TabVoice in ly/engraver-init.ly, because the stems have now length zero, so this is superfluous (and will be reverted by the first call of \unHideNotes anyway). Regards, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Il 16/04/2012 12:24, Marc Hohl ha scritto: if you create a patch, I think you can remove the Stem #'transparent = ##t in the definition of TabVoice in ly/engraver-init.ly, because the stems have now length zero, so this is superfluous (and will be reverted by the first call of \unHideNotes anyway). Mmmmh, in that file I can read that stems in TabVoice are made as short as possible, but they are still there: %% make the Stems as short as possible to minimize their influence %% on the slur::calc-control-points routine \override Stem #'no-stem-extend = ##t \override Flag #'style = #'no-flag \override Stem #'details = #'((lengths 0 0 0 0 0 0) (beamed-lengths 0 0 0) (beamed-minimum-free-lengths 0 0 0) (beamed-extreme-minimum-free-lengths 0 0) (stem-shorten 0 0)) %% after all, the stubs of the stems may still be visible, so ... \override Stem #'stencil = ##f I found just the override above (can't find Stem #'transparent = ##t). If I comment it, stems are displayed in TabStaff. BTW, there's no more need to override the whiteout property, right? I can see that hideNotes hide the whiteout even if no specific override is included. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Am 16.04.2012 23:25, schrieb Federico Bruni: Il 16/04/2012 12:24, Marc Hohl ha scritto: if you create a patch, I think you can remove the Stem #'transparent = ##t in the definition of TabVoice in ly/engraver-init.ly, because the stems have now length zero, so this is superfluous (and will be reverted by the first call of \unHideNotes anyway). Mmmmh, in that file I can read that stems in TabVoice are made as short as possible, but they are still there: %% make the Stems as short as possible to minimize their influence %% on the slur::calc-control-points routine \override Stem #'no-stem-extend = ##t \override Flag #'style = #'no-flag \override Stem #'details = #'((lengths 0 0 0 0 0 0) (beamed-lengths 0 0 0) (beamed-minimum-free-lengths 0 0 0) (beamed-extreme-minimum-free-lengths 0 0) (stem-shorten 0 0)) %% after all, the stubs of the stems may still be visible, so ... \override Stem #'stencil = ##f I found just the override above (can't find Stem #'transparent = ##t). If I comment it, stems are displayed in TabStaff. Oh, sorry, you are right - I stay corrected. BTW, there's no more need to override the whiteout property, right? I can see that hideNotes hide the whiteout even if no specific override is included. That's right, when a grob is set transparent, the whiteout is removed automatically. Regards, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Il 14/04/2012 21:09, James ha scritto: Hello, On 14 April 2012 15:47, Marc Hohlm...@hohlart.de wrote: Am 14.04.2012 11:57, schrieb Federico Bruni: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 I'll verify that if no one else has. I am building a latest version at the moment of 2.15.x I've tested it now on latest version of lilypond/translation branch. It works fine. However reading the tracker again just now, are the comments from this morning a 'new' issue or an 'enhancement' if so, we need a new tracker. Could Federico or Marc clarify please? It's an enhancement, which has already been discussed before (see links I pasted in the tracker) but never recorded in the tracker. If the change is accepted, the following snippet should be removed (I think): http://lsr.dsi.unimi.it/LSR/Snippet?id=633 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Hello, On 15 April 2012 07:13, Federico Bruni fedel...@gmail.com wrote: Il 14/04/2012 21:09, James ha scritto: Hello, On 14 April 2012 15:47, Marc Hohlm...@hohlart.de wrote: Am 14.04.2012 11:57, schrieb Federico Bruni: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 I'll verify that if no one else has. I am building a latest version at the moment of 2.15.x I've tested it now on latest version of lilypond/translation branch. It works fine. Right so Issue 1459 is fixed? However reading the tracker again just now, are the comments from this morning a 'new' issue or an 'enhancement' if so, we need a new tracker. Could Federico or Marc clarify please? It's an enhancement, which has already been discussed before (see links I pasted in the tracker) but never recorded in the tracker. You don't really make it easy for the bug squad - who are generally non-technical people who have enough to do without having to pick apart/read through long threads, threads I might add that have never been reported to the bug list (or dev list - that was me). Federico, it seems you have the ability (and knowledge) to create a tracker yourself so I suggest that if issue 1459 is fixed you change the label to fixed - someone else will verify - and then create a new tracker for the enhancement - whatever it is. Else whoever comes back to the old tracker has to puzzle their way through and often this puts people off (unless you yourself are going to work and create the patch). If the change is accepted, the following snippet should be removed (I think): http://lsr.dsi.unimi.it/LSR/Snippet?id=633 Add this to the same (new?) Tracker as well. We're desperately trying to make it as easy as possible for the bug squad (and developers) to workout what a tracker is for and if/when it is fixed and more importantly how to know what they are looking at. I hope you understand. james ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Il 15/04/2012 11:00, James ha scritto: Federico, it seems you have the ability (and knowledge) to create a tracker yourself so I suggest that if issue 1459 is fixed you change the label to fixed - someone else will verify - and then create a new tracker for the enhancement - whatever it is. Else whoever comes back to the old tracker has to puzzle their way through and often this puts people off (unless you yourself are going to work and create the patch). Yes, issue 1459 is fixed. How can I change the label to fixed in the tracker? The patch itself is very easy and I could create it, but I think that I'd better just create the issue in the tracker. Here it is: http://code.google.com/p/lilypond/issues/detail?id=2480 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Il 15/04/2012 12:06, Federico Bruni ha scritto: Yes, issue 1459 is fixed. How can I change the label to fixed in the tracker? I guess I can't: Only project owners and committers can edit issue metadata. These users see additional fields when entering a new issue or adding a comment. The drop-down auto-complete menu for each field will help you enter commonly used values. However, for the labels, you are free to enter new or uncommon labels simply by typing them. http://code.google.com/p/support/wiki/IssueTrackerFAQ#Edit_issue_labels__metadata Can you add me to the members? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
- Original Message - From: Federico Bruni fedel...@gmail.com To: James pkx1...@gmail.com Cc: Devel lilypond-devel@gnu.org; lilypond-u...@gnu.org Sent: Sunday, April 15, 2012 2:13 PM Subject: Re: hideNotes in tablature Il 15/04/2012 12:06, Federico Bruni ha scritto: Yes, issue 1459 is fixed. How can I change the label to fixed in the tracker? I guess I can't: Only project owners and committers can edit issue metadata. These users see additional fields when entering a new issue or adding a comment. The drop-down auto-complete menu for each field will help you enter commonly used values. However, for the labels, you are free to enter new or uncommon labels simply by typing them. http://code.google.com/p/support/wiki/IssueTrackerFAQ#Edit_issue_labels__metadata Can you add me to the members? Done. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Federico, On 14 April 2012 10:57, Federico Bruni fedel...@gmail.com wrote: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 As hideNotes/unHideNotes work fine in TabStaff now, I'm thinking that it would be nice to add a TabNoteHead override/revert in their definitions in property-init.ly Two years ago Marc expressed some concern about including TabNoteHead inside hideNotes/unHideNotes, because unHideNotes reverts the transparency of objects (such as stems and dots) that shouldn't be displayed in TabStaff: http://lists.gnu.org/archive/html/lilypond-user/2010-01/msg00634.html I've made some tests and I think that there's no reason for such a concern. Everything looks fine to me (see the attached snippet). Sure, I'm missing something :) I believe that we don't need a specific command for hiding TabNoteHead. I always use Staff and TabStaff: both should display (or hide) the same music, I can't imagine a situation where I'd like to hide a note in Staff and not in TabStaff. What do you think about it? I think 'user' isn't the email list you really need to send this to but dev. Also I see have already updated the Tracker. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: hideNotes in tablature
Hello, On 14 April 2012 15:47, Marc Hohl m...@hohlart.de wrote: Am 14.04.2012 11:57, schrieb Federico Bruni: Hi, I started using version 2.13.56 and I realized that this bug seems fixed: http://code.google.com/p/lilypond/issues/detail?id=1459 I'll verify that if no one else has. I am building a latest version at the moment of 2.15.x However reading the tracker again just now, are the comments from this morning a 'new' issue or an 'enhancement' if so, we need a new tracker. Could Federico or Marc clarify please? James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
