Double dispatch does not indent thread block

[GoogleCodeExporter]

I am visualising double dispatch as variation of the visitor pattern. As calls 
are latex environments each, I was expecting thread blocks to be indented the 
way self calls are indented.

For better appreciation of the problem I created a small example. In the lower 
half you see nested self calls which lead to indented thread blocks. I would 
expect the same for the calls of handleStartEvent and handlePauseEvent.

Furthermore, I tried using setthreadbias, however selfcalls are created 
relatively to their initial instance, instead of the thread box they are 
related to.

Original issue reported on code.google.com by jan.erns...@gmail.com on 29 Feb 2012 at 10:38

Attachments:

• double-dispatch-and-self-calls.tex

[GoogleCodeExporter]

For the time being I used a quick and dirty approach to get indentations. I 
included a diff that I beg you *NOT* to include. It is only prelimary work 
around.

Original comment by jan.erns...@gmail.com on 29 Feb 2012 at 1:20

Attachments:

• work-around-for-indented-double-dispatch.diff

[GoogleCodeExporter]

Something probably related: nest a couple callself, a call, and a callself 
again. The innermost callself is out of alignment.

    \newthread{A}{A}
    \newinst[2]{B}{B}
    \begin{callself}{A}{}{}
        \begin{callself}{A}{}{}
            \begin{call}{A}{}{B}{} % arrows of this call should start from the border of the innermost thread rectangle, but instead they start from the outermost
                \begin{callself}{B}{}{} % this is shifted to the right and visually disconnected from B's timeline
                \end{callself}
            \end{call}
        \end{callself}
    \end{callself}

Original comment by damien.p...@gmail.com on 21 Mar 2013 at 10:07