2011/6/14 James Lowe :
> [James' reply:] Anything you can give me specifically Keith?
> I've just got back from my travels so am trying to catch up
> the threads that are pertinent to me,
> so if you have done this or it has been resolved I apologise.
I'm not Keith :) but this is rather closed now
with cross-staff
)stems, on lilypond-user)
)
)Janek Warchoł gmail.com> writes:
)
)> The change is almost certainly due to new beam collision algorithm.
)> I'm forwarding this message to the development team so that they will
)> know about this issue.
)> I'm not sure if it&#
2011/6/12 Graham Percival :
> On Sun, Jun 12, 2011 at 02:06:35PM +0200, Janek Warchoł wrote:
>> 2011/6/11 Graham Percival :
>> > Is this problem likely to be unfixed? Or is there a compelling
>> > reason to override our normal doc policy in this specific case?
>> > I am always happy to grant excep
On 10 June 2011 08:05, Keith OHara wrote:
> I think it is a documentation issue. Sometimes we need to turn off the new
> automatic collision avoidance by beams.
>
> \version "2.12"
> <<
> c'2
> \new Staff <<
> %% The cross-staff chord below worked until about 2.13.50,
> %% but now we ne
On Sun, Jun 12, 2011 at 02:06:35PM +0200, Janek Warchoł wrote:
> 2011/6/11 Graham Percival :
> > Is this problem likely to be unfixed? Or is there a compelling
> > reason to override our normal doc policy in this specific case?
> > I am always happy to grant exceptions if there is a good reason.
>
2011/6/11 Graham Percival :
> On Fri, Jun 10, 2011 at 07:05:34AM +, Keith OHara wrote:
>> Janek Warchoł gmail.com> writes:
>>
>> > The change is almost certainly due to new beam collision algorithm.
>> > I'm forwarding this message to the development team so that they will
>> > know about this
On Fri, Jun 10, 2011 at 07:05:34AM +, Keith OHara wrote:
> Janek Warchoł gmail.com> writes:
>
> > The change is almost certainly due to new beam collision algorithm.
> > I'm forwarding this message to the development team so that they will
> > know about this issue.
> > I'm not sure if it's a
Janek Warchoł gmail.com> writes:
> The change is almost certainly due to new beam collision algorithm.
> I'm forwarding this message to the development team so that they will
> know about this issue.
> I'm not sure if it's a bug, though
I think it is a documentation issue. Sometimes we need to
Hi David,
glad it worked :)
The change is almost certainly due to new beam collision algorithm.
I'm forwarding this message to the development team so that they will
know about this issue.
I'm not sure if it's a bug, though - Phil, you are the bugmaster, can
you give us your opinion? :)
cheers,
J
