Just to show how ugly this dot-moving problem is, here an example produced by the code in its current state. 3 out of 4 isn’t bad, right?
--Don ============================= 1 1 2 4 2 4 0 0 0 3 20 0 t .\ w4i Ab r8 b43ld+0+1 zc b43ld+0+1 zc r8 / r8 b43ld+0+1 zc / b43ld+0+1 zc r8 / ============================= From: TeX-Music [mailto:[email protected]] On Behalf Of Don Simons Sent: Saturday, January 20, 2018 12:18 PM To: 'Werner Icking Music Archive' <[email protected]> Subject: Re: [Tex-music] PMX : moving dots I’m still working to correct this bug. It’s proving to be insanely complicated, due in part to the complex and different ways I had originally set up PMX to store information about shifted dots on main notes and chord notes. I have so far managed to fix Dieter’s case (the last chord in his example below). But in a closely related, very specific case, my fix breaks down, namely if you don’t move the dot on the B but do move the one on the C. My question for the group is this: Can you think of any real situation where you ever would want to do that? I.e., a case where you have a dotted 2-note chord with an interval of a second, and you want to move the dot on the right-most note from its default position, but leave the dot on the left-most note in its default position (where the dot will probably crash into the other note head)? It would save me some more hair-pulling if I didn’t have to worry about this very particular and very unlikely case. --Don
------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
