Am Mo., 10. Feb. 2020 um 22:15 Uhr schrieb Michael Käppler :
>
> Am 10.02.2020 um 20:51 schrieb Thomas Morley:
> > Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler
> > :
> >>
> >> Hi Harm,
> >>
> >>> Fine with me, I already updated the LSR-code, for now unapproved.
> >>> Please have a lo
Am 10.02.2020 um 20:51 schrieb Thomas Morley:
Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler :
Hi Harm,
Fine with me, I already updated the LSR-code, for now unapproved.
Please have a look whether all is ok, snippet-description and the like.
Everything ok now, please approve if y
Am Mo., 10. Feb. 2020 um 20:43 Uhr schrieb Michael Käppler :
>
> Am 10.02.2020 um 10:10 schrieb Michael Käppler:
> >
> >
> > Do you have any idea how to preserve indentation within blocks?
> > Inserting or the like seems hacky, inline-css-styling too...
> Ok, found out that the combination of a
Am Mo., 10. Feb. 2020 um 10:11 Uhr schrieb Michael Käppler :
>
>
> Hi Harm,
>
> > Fine with me, I already updated the LSR-code, for now unapproved.
> > Please have a look whether all is ok, snippet-description and the like.
> Thank you for updating!
> Will update the description this evening.
> Do
Am 10.02.2020 um 10:10 schrieb Michael Käppler:
Do you have any idea how to preserve indentation within blocks?
Inserting or the like seems hacky, inline-css-styling too...
Ok, found out that the combination of and tags does work
well for that purpose.
Probably one suggestion:
How abou
Hi Harm,
Fine with me, I already updated the LSR-code, for now unapproved.
Please have a look whether all is ok, snippet-description and the like.
Thank you for updating!
Will update the description this evening.
Do you have any idea how to preserve indentation within blocks?
Inserting or
Hi Michael,
Am Mi., 5. Feb. 2020 um 14:54 Uhr schrieb Michael Käppler :
>
> Hi Harm,
> sorry that I did not respond for over one month... Many other things had
> to be done.
Same here...
> Now I would like to finish this snippet to be free for new interesting
> things. ;)
>
> I did substantially
Hi Harm,
sorry that I did not respond for over one month... Many other things had
to be done.
Now I would like to finish this snippet to be free for new interesting
things. ;)
I did substantially rework some parts of the engraver, namely switching
to a list-processing-way of dealing with current/
Am So., 29. Dez. 2019 um 12:11 Uhr schrieb Thomas Morley
:
> Some other remarks:
[...]
And a general one.
If a note is last in previous interval and first in a new one, then
the color from the new one is done, leaving the first of the previous
interval with the for it set color:
\score {
<<
Hi Michael,
Am Fr., 27. Dez. 2019 um 16:12 Uhr schrieb Michael Käppler :
>
> Hi Harm,
> thanks for your comments and this inspiring discussion!
me too!
> I would like to discuss a couple of things further.
> My current version is attached.
> > Along with it, I added a basic check for the user p
Hi Harm,
thanks for your comments and this inspiring discussion!
I would like to discuss a couple of things further.
My current version is attached.
You try to give the user always meaningful warning-messages.
That's great, putting out really helpful messages is hard work...
Alas, speaking only
Am Sa., 21. Dez. 2019 um 00:35 Uhr schrieb Michael Käppler :
>
> Hi Harm et al.,
> attached is my updated version.
> I decided to split up the validity checks from the actual engraver,
> because otherwise in case of invalid parameters the engraver would
> only be instantiated to do nothing and neve
Btw. what I do not understand is why (process-acknowledged) is called
multiple times
after one grob has been acknowledged, it is even called >before< any
grob has been
acknowledged.
You can notice this clearly in
input/regression/scheme-engraver.ly
Cheers,
Michael
Am 16.12.2019 um 01:50 schrieb
Hi Harm et al.,
attached is my updated version.
I decided to split up the validity checks from the actual engraver,
because otherwise in case of invalid parameters the engraver would
only be instantiated to do nothing and nevertheless have its
acknowledger called every time.
The code is much more
Hi Harm,
many thanks for your comments and for the time you spent
with doing work that I should have been done.
I already thought about adjusting the engraver to take several intervals
into account,
but left it for simplicity (of the engraver, not of the examples ;)) But
you are absolutely right
t
Am So., 15. Dez. 2019 um 21:47 Uhr schrieb Thomas Morley
:
>
> Am So., 15. Dez. 2019 um 21:17 Uhr schrieb Michael Käppler
> :
> >
> > Hi all,
> > a few days ago I submitted a snippet to the LSR (title "Coloring
> > successive intervals"). I can see it in the snippet database,
> > but not in the we
Am So., 15. Dez. 2019 um 21:17 Uhr schrieb Michael Käppler :
>
> Hi all,
> a few days ago I submitted a snippet to the LSR (title "Coloring
> successive intervals"). I can see it in the snippet database,
> but not in the webpage. The "Contributing" section of LSR states, that:
>
> "Once the snippet
Hi Michael,
Here it is: http://lsr.di.unimi.it/LSR/Item?id=1100
Cheers,
Pierre
Le dim. 15 déc. 2019 à 21:18, Michael Käppler a écrit :
> Hi all,
> a few days ago I submitted a snippet to the LSR (title "Coloring
> successive intervals"). I can see it in the snippet database,
> but not in the web
18 matches
Mail list logo
