Re: rest collisions warning but no collision

2014-09-05 Thread Werner LEMBERG
> They are effectively colliding, which you've avoided by moving them > as pitched rests. Hmm. `Effectively colliding' isn't user friendly... Is there a way to avoid this warning if pitched rests really don't collide? Werner ___ lilypond-user m

Re: rest collisions warning but no collision

2014-09-05 Thread bart deruyter
emXX > commands, and use voiceOne and voiceTwo for the upper and lower voices. > > -- > Phil Holmes > > > > - Original Message - > *From:* bart deruyter > *To:* lilypond-user@gnu.org > *Sent:* Friday, September 05, 2014 2:53 PM > *Subject:* rest collisions

Re: rest collisions warning but no collision

2014-09-05 Thread Phil Holmes
To: lilypond-user@gnu.org Sent: Friday, September 05, 2014 2:53 PM Subject: rest collisions warning but no collision Hi all, running this code (also in attachment) results in a warning saying there are too many colliding rests. I don't see where the collision could be though, th

rest collisions warning but no collision

2014-09-05 Thread bart deruyter
Hi all, running this code (also in attachment) results in a warning saying there are too many colliding rests. I don't see where the collision could be though, the warning shouldn't be there in my opinion. I know it renders fine, but still, I prefer results without warnings, it makes me worry that