Re: Forcing hshift not working...

[James Bailey]

The problem wasn't finding the collision. The problem was figuring  
out what's going on in the other voices. There are no measure  
numbers, so I can't see what the other voices are doing at the same  
time (often problems in one voice are caused by something in another  
voice). So, if you can send an example that shows the problem, I'll  
be more than happy to look at it and help you find a solution.

On 30.12.2009, at 21:39, Alberto Simões wrote:

> On 30/12/2009 20:01, James Bailey wrote:
> > If you can show this in a one measure example, I'd more than  
> > willing to
> > help you, but trying to find out where the problem is, amidst all of
> > your voices is a bit more work than I'm willing to put in.
>
> Please check the attachment.
> You can grep for COLISION to find it faster.
>
> THanks
> > On 30.12.2009, at 20:43, Alberto Simões wrote:
> >
> > > Hey
> > >
> > > On 30/12/2009 19:38, Nick Payne wrote:
> > > > On 31/12/09 06:21, Alberto Simões wrote:
> > > > > \once \override NoteColumn #'force-hshift = #-1.0
> > > > I have sometimes come across the same problem and find that adding
> > > >
> > > > \once \override NoteColumn #'force-hshift = #0.01
> > > >
> > > > to the other voice(s) will get the shift to happen.
> > >
> > > Just tried that and it did not happen. Added just to the voice in  
> > > the
> > > collision, then added in all voices, but nothing...
> > >
> > > Thanks
> > > Alberto
> > >
> > > --
> > > Alberto Simões
> > >
> > >
> > > _______________________________________________
> > > lilypond-user mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/lilypond-user
>
> --
> Alberto Simões<foo.ly>