Re: Access a tie from a slur

2017-01-03 Thread Urs Liska
Hi David, thank you for the clarification. Am 03.01.2017 um 15:07 schrieb David Nalesnik: > Hi Urs, > > On Tue, Jan 3, 2017 at 1:14 AM, Urs Liska wrote: >> Hi David, >> >> thank you for now. This is proof that one can at least *get* to the >> right information, and when the use-case is clearer

Re: Access a tie from a slur

2017-01-03 Thread David Nalesnik
Hi Urs, On Tue, Jan 3, 2017 at 1:14 AM, Urs Liska wrote: > Hi David, > > thank you for now. This is proof that one can at least *get* to the > right information, and when the use-case is clearer one may also find a > more efficient approach if possible. > > Just one more question (a simple "yes"

Re: Access a tie from a slur

2017-01-02 Thread Urs Liska
Hi David, thank you for now. This is proof that one can at least *get* to the right information, and when the use-case is clearer one may also find a more efficient approach if possible. Just one more question (a simple "yes" or "no" or a pointer to a function name will do, no need to write a sol

Re: Access a tie from a slur

2017-01-02 Thread David Nalesnik
Hi Urs, On Mon, Jan 2, 2017 at 6:33 PM, Urs Liska wrote: > Hi all, > > the message title may be misleading, but it names the only idea I have > for my current issue. > > I am asked to create a strange slur configuration similar to the > attached example. The coloring is only for better referencin