turinglife / pgf-umlsd Goto Github PK

1. Create a sdblock with a long description
2. Place a selfcall with a short method name and return value
3. Observe that the frame enclosing the block is not wide enough to fit the 
description.

It should either create a frame wide enough for the box description or 
hyphenate the description in order to fit inside the frame.

Observed in version 0.6

I would like to draw additional stuff in the sdl diagram. therefor I need to 
reference the points where a message starts and ends.

It could be solved something like this (untested):
# Usage: \sdnode{reference of instance}{level}
\newcommand{\sdnode}[2]{$(#1)+(0,2*\unitfactor-0.7*\unitfactor)$}

Then you could call something like:
\draw (\sdnode{inst1}{2}) rectangle (\sdnode{inst3}{5})};

I am using the diagram without a thread. Nevertheless sequencediagram wants to 
paint on layer background from start to end of thread1.

I attached a patch, that fixes this behavior. This allows empty sequencediagram 
without insts or threads.

Could you please include an option parameter to influence whether shadows are 
used for the inststyle similar to rounded corners or underline;
such as : [shadows=false]

Moreover, nice and easy-to-use package ;)


Regards,
Martin

What steps will reproduce the problem?
1. Download source
2. Compile Demo

What is the expected output? What do you see instead?

The demo doesn't compile.

What version of the product are you using? On what operating system?

0.5 

Please provide any additional information below.

josiah@VAIO-OF-DOOOM:~/Projects/Mashbot/doc/design$ pdflatex pgf-umlsd-
demo.tex This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
(./pgf-umlsd-demo.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, 
noh
yphenation, croatian, ukrainian, russian, bulgarian, czech, slovak, danish, 
dut
ch, finnish, basque, french, german, ngerman, ibycus, greek, monogreek, 
ancient
greek, hungarian, italian, latin, mongolian, norsk, icelandic, interlingua, 
tur
kish, coptic, romanian, welsh, serbian, slovenian, estonian, esperanto, 
upperso
rbian, indonesian, polish, portuguese, spanish, catalan, galician, swedish, 
loa
ded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo))
(/usr/share/texmf/tex/latex/pgf/frontendlayer/tikz.sty
(/usr/share/texmf/tex/latex/pgf/basiclayer/pgf.sty
(/usr/share/texmf/tex/latex/pgf/utilities/pgfrcs.sty
(/usr/share/texmf/tex/generic/pgf/utilities/pgfutil-common.tex)
(/usr/share/texmf/tex/generic/pgf/utilities/pgfutil-latex.def)
(/usr/share/texmf/tex/generic/pgf/utilities/pgfrcs.code.tex))
(/usr/share/texmf/tex/latex/pgf/basiclayer/pgfcore.sty
(/usr/share/texmf-texlive/tex/latex/graphics/graphicx.sty
(/usr/share/texmf-texlive/tex/latex/graphics/keyval.sty)
(/usr/share/texmf-texlive/tex/latex/graphics/graphics.sty
(/usr/share/texmf-texlive/tex/latex/graphics/trig.sty)
(/etc/texmf/tex/latex/config/graphics.cfg)
(/usr/share/texmf-texlive/tex/latex/pdftex-def/pdftex.def)))
(/usr/share/texmf/tex/latex/pgf/systemlayer/pgfsys.sty
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys.code.tex
(/usr/share/texmf/tex/generic/pgf/utilities/pgfkeys.code.tex)
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgf.cfg)
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys-pdftex.def
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsys-common-pdf.def)))
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsyssoftpath.code.tex)
(/usr/share/texmf/tex/generic/pgf/systemlayer/pgfsysprotocol.code.tex))
(/usr/share/texmf/tex/latex/xcolor/xcolor.sty
(/etc/texmf/tex/latex/config/color.cfg))
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcore.code.tex
(/usr/share/texmf/tex/generic/pgf/math/pgfmath.code.tex
(/usr/share/texmf/tex/generic/pgf/math/pgfmathcalc.code.tex
(/usr/share/texmf/tex/generic/pgf/math/pgfmathutil.code.tex)
(/usr/share/texmf/tex/generic/pgf/math/pgfmathparser.code.tex)
(/usr/share/texmf/tex/generic/pgf/math/pgfmathoperations.code.tex
(/usr/share/texmf/tex/generic/pgf/math/pgfmathtrig.code.tex)
(/usr/share/texmf/tex/generic/pgf/math/pgfmathrnd.code.tex))
(/usr/share/texmf/tex/generic/pgf/math/pgfmathbase.code.tex)))
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathconstruct.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathusage.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorescopes.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoregraphicstate.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoretransformations.code.te
x)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorequick.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoreobjects.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepathprocessing.code.tex
)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorearrows.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoreshade.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoreimage.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorelayers.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcoretransparency.code.tex)
(/usr/share/texmf/tex/generic/pgf/basiclayer/pgfcorepatterns.code.tex)))
(/usr/share/texmf/tex/generic/pgf/modules/pgfmoduleshapes.code.tex)
(/usr/share/texmf/tex/generic/pgf/modules/pgfmoduleplot.code.tex)
(/usr/share/texmf/tex/latex/pgf/compatibility/pgfcomp-version-0-65.sty)
(/usr/share/texmf/tex/latex/pgf/compatibility/pgfcomp-version-1-18.sty))
(/usr/share/texmf/tex/latex/pgf/utilities/pgffor.sty
(/usr/share/texmf/tex/generic/pgf/utilities/pgffor.code.tex))
(/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz/tikz.code.tex
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibraryplothandlers.code.tex
)
(/usr/share/texmf/tex/generic/pgf/modules/pgfmodulematrix.code.tex)
(/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryt
opat
hs.code.tex)))
(/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibrarya
rrow
s.code.tex
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibraryarrows.code.tex))
(/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibrarys
hado
ws.code.tex
(/usr/share/texmf/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryf
adin
gs.code.tex
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibraryfadings.code.tex)))
(./pgf-umlsd.sty)
No file pgf-umlsd-demo.aux.
! Use of \t doesn't match its definition.
\tikz@scan@no@calculator ...\edef \tikz@temp {(#2)
                                                  }\expandafter 
\tikz@@scan@...
l.46   \end{sequencediagram}

It would be great to have a "create" message command which creates a new 
instance but places the box at the message arrow's vertical position instead of 
at the very top of the diagram.

What steps will reproduce the problem?
1. Create a thread and and instance
2. Put a call self in the thread
3. Embed a call to the instance in the previously defined call self

What is the expected output? What do you see instead?
I expect lines and arrows to start from the callself block. Arrows and lines 
start from the thread and there is a vertical space between thread and callself 
block.

What version of the product are you using? On what operating system?
I am using the texlive-pictures package (2013.20130722-1) on Ubuntu 13.10.

Please provide any additional information below.
I really like your package.

Here is an example code (output attached):

\documentclass{article}

\usepackage{tikz}
\usetikzlibrary{arrows,shadows}
\usepackage{pgf-umlsd}

\begin{document}

\begin{sequencediagram}
\newthread{thread}{Thread}
\newinst[1]{instance}{Instance}

\begin{callself}{thread}{foo(\ldots)}{return}
    \begin{call}{thread}{bar(\ldots)}{instance}{return}
    \end{call}
\end{callself}

\end{sequencediagram}

\end{document}

I want achieve a result similar to Figure 2 at 
http://www.ibm.com/developerworks/rational/library/3101.html. A caption in a 
sequence diagram is useful for referring to it from other sequence diagrams. It 
should appear as if the sequence diagram is inside a block.

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.

What steps will reproduce the problem?
1. Create a sequence diagram with some calls
2. Add a sdblock with label and description
3. Compile and only the block will be visible. All other elements (calls and 
instances) disappear.
A block without calls is useful when referring to other sequence diagrams. I 
would expect to show a block containing only the label and caption. If I add a 
self call, everything appear fine but I do not want to put that self call.
I am using version 0.6.

Find attached a sequence diagram that demonstrates the problem. Comment out the 
callself environment and recompile.

The demo file should be updated to reflect the changes in the number of 
arguments in "callself" introduced in R13. Please see the attached patch

What steps will reproduce the problem?
1. What are the dependencies
2. How to install it

For example if I download and unpack it and run latexmk on one of the 
examples, I get this error:


s.code.tex
(/usr/share/texmf/tex/generic/pgf/libraries/pgflibraryfadings.code.tex

Package pgf Warning: Your graphic driver pgfsys-dvips.def does not support 
fadi
ngs. This warning is given only once on input line 31.

))) (./pgf-umlsd.sty)
No file pgf-umlsd-demo.aux.
! Use of \t doesn't match its definition.
\tikz@scan@no@calculator ...\edef \tikz@temp {(#2)
                                                  }\expandafter 
\tikz@@scan@...
l.46   \end{sequencediagram}

? x
No pages of output.
Transcript written on pgf-umlsd-demo.log.
Latexmk: restoring last pgf-umlsd-demo.aux file

------------
Latexmk: Latex encountered an error.
-- Use the -f option to force complete processing.

Hi!

Is there a way to layout alternative blocks? As far as I know they are normally 
done with a dotted line and [condition] statements.


Example:

___________________
Block|             |
_____/             |
                   |
[condition]        |
                   |
                   |
-------------------|
[other condition]  |
                   |
                   |
                   |
-------------------|
[else]             |
                   |
                   |
                   |
___________________|


Please excuse the bad ASCII art :). Any ideas how to achieve that in pgf-umlsd?

Why is there no possibility to create diagrams only with instances?
If i try it i get the following error:

! Package pgf Error: No shape named thread1 is known.

What steps will reproduce the problem?
1. Add two sdloop environments
2. Compile
3. Outer loop label is hidden by the inner loop label

What is the expected output? What do you see instead?
The inner loop should be placed below the inner loop.

What version of the product are you using? On what operating system?
pgf-2.00

Please provide any additional information below.
Patch for improved spacing with sdloop.

If you use externalization library, it looks for \end{tikzpicture}, which is 
not explicitly present in case of sequencediagram environment. That's why it 
would be useful to be able to create sequence diagrams within tikzpicture 
environment directly.

My proposal for names of the new commands would be: \sdinit, \sdbegin and 
\sdend.

sequencediagram would be redefined then as follows:

% the environment of sequence diagram
\newenvironment{sequencediagram}
{\sdinit\begin{tikzpicture}\sdbegin}
{\sdend\end{tikzpicture}}

You may see also:
http://tex.stackexchange.com/q/98525/5264

What steps will reproduce the problem?
1. put in the preamble:
\usepackage{tikz}
\usepackage{pgf-umlsd}
\usepackage{pgf-umlcd}

The pfg-umlsd doen't work properly. Vertical bars of the threads in the 
sequence diagrams aren't drawed or painted.

2. put in the preamble:
\usepackage{tikz}
\usepackage{pgf-umlcd}
\usepackage{pgf-umlsd}

The pfg-umlcd doen't work properly. The inherited lines aren't drawed or 
painted.

What version of the product are you using? On what operating system?
tikz version 1.76
pgf-umlcd version 0.2.1
pgf-umlsd version 0.6

Ubuntu Linux 11.10 (KDE, kate and texlive)

Using Windows (MiKTeX 2.8)...

What steps will reproduce the problem?
1. Create a diagram with MetaUML and build with metapost
2. Add to a latex document using \includegraphics
3. Add the pgf-umlsd example from version 0.2 also
4. Build using pdflatex

Expected: Fonts and graphics are smooth when zoomed out (as before).
Actual: Fonts and graphics look pixelated and "jagged" (due to pgf-umlsd).

Dear editor,
is it possible to have an outside call beein implemented?

For my class i need an instance to be activated from an unknown invisible 
object from the outside. This means the Diagramm starts with objectA receiving 
a call and then gets active, finishing its tasks and sending a return to the 
outside again.

Thanks :)

Is there a possibility to disable the shadows like the underlining?
underline=false is working, but i can figure out how to disable the shadows.

What steps will reproduce the problem?
1. usepackage[luximono] in the same document as pgf-umlsd package

The command should be renamed to something less generic.

it would be nice if pgf-umlsd had parallel messages.
like the paid version of websequencediagrams.com
https://www.websequencediagrams.com/examples.html

Is it possible to specify newlines in either function or return value? I'd like 
to describe the method calls in more detail. 

Steps to reproduce:

\documentclass{article}

\usepackage{pgf-umlsd}

\begin{document}

\begin{sequencediagram}

    \newinst[5]{A}{Alice}
    \newinst[5]{B}{Bob}

    \mess[1]{A}{)}{B}
    % Coming from:
    % \mess[1]{A}{Enc(M)}{B}

\end{sequencediagram}
\end{document}


What I see:
! Package tikz Error: A node must have a (possibly empty) label text.

See the tikz package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              

l.31    \mess[1]{A}{)}{B}

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on p2ppki_validation_test.log.


I'm using pgf-umlsd version 0.7 on Arch Linux from texlive-core 2014.34872.

define the edge distance for threads too and not only for instances.