uml type=ref, for reference in sequence diagram [on hold]
I've checked the option in tikz-uml
to put a umlfragment
of type=ref
so I could get a fragment labelled, in the left up corner, as ref
. Something like this,
But, unfortunately there seem to be all sort of option except this one.
Any idea??
tikz-uml ref
put on hold as unclear what you're asking by Torbjørn T., Sebastiano, Christian Hupfer, Kurt, samcarter 2 days ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
I've checked the option in tikz-uml
to put a umlfragment
of type=ref
so I could get a fragment labelled, in the left up corner, as ref
. Something like this,
But, unfortunately there seem to be all sort of option except this one.
Any idea??
tikz-uml ref
put on hold as unclear what you're asking by Torbjørn T., Sebastiano, Christian Hupfer, Kurt, samcarter 2 days ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?
– manooooh
Dec 9 at 17:52
1
@manooooh , I mean like when you tipe...{umlfragment}[**type**=<option>]
; the options areloop
,opt
,alt
,seq
, and so on. But when I try typingref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.
– Fr3d
Dec 9 at 18:49
1
I tried the code from your other question withtype=ref
in theumlfragment
instead oftype=loop
, and that worked fine. Can you show the code that doesn't work?
– Torbjørn T.
Dec 9 at 19:28
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago
add a comment |
I've checked the option in tikz-uml
to put a umlfragment
of type=ref
so I could get a fragment labelled, in the left up corner, as ref
. Something like this,
But, unfortunately there seem to be all sort of option except this one.
Any idea??
tikz-uml ref
I've checked the option in tikz-uml
to put a umlfragment
of type=ref
so I could get a fragment labelled, in the left up corner, as ref
. Something like this,
But, unfortunately there seem to be all sort of option except this one.
Any idea??
tikz-uml ref
tikz-uml ref
asked Dec 9 at 17:27
Fr3d
156
156
put on hold as unclear what you're asking by Torbjørn T., Sebastiano, Christian Hupfer, Kurt, samcarter 2 days ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as unclear what you're asking by Torbjørn T., Sebastiano, Christian Hupfer, Kurt, samcarter 2 days ago
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?
– manooooh
Dec 9 at 17:52
1
@manooooh , I mean like when you tipe...{umlfragment}[**type**=<option>]
; the options areloop
,opt
,alt
,seq
, and so on. But when I try typingref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.
– Fr3d
Dec 9 at 18:49
1
I tried the code from your other question withtype=ref
in theumlfragment
instead oftype=loop
, and that worked fine. Can you show the code that doesn't work?
– Torbjørn T.
Dec 9 at 19:28
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago
add a comment |
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?
– manooooh
Dec 9 at 17:52
1
@manooooh , I mean like when you tipe...{umlfragment}[**type**=<option>]
; the options areloop
,opt
,alt
,seq
, and so on. But when I try typingref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.
– Fr3d
Dec 9 at 18:49
1
I tried the code from your other question withtype=ref
in theumlfragment
instead oftype=loop
, and that worked fine. Can you show the code that doesn't work?
– Torbjørn T.
Dec 9 at 19:28
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?– manooooh
Dec 9 at 17:52
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?– manooooh
Dec 9 at 17:52
1
1
@manooooh , I mean like when you tipe
...{umlfragment}[**type**=<option>]
; the options are loop
, opt
, alt
, seq
, and so on. But when I try typing ref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.– Fr3d
Dec 9 at 18:49
@manooooh , I mean like when you tipe
...{umlfragment}[**type**=<option>]
; the options are loop
, opt
, alt
, seq
, and so on. But when I try typing ref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.– Fr3d
Dec 9 at 18:49
1
1
I tried the code from your other question with
type=ref
in the umlfragment
instead of type=loop
, and that worked fine. Can you show the code that doesn't work?– Torbjørn T.
Dec 9 at 19:28
I tried the code from your other question with
type=ref
in the umlfragment
instead of type=loop
, and that worked fine. Can you show the code that doesn't work?– Torbjørn T.
Dec 9 at 19:28
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
But, unfortunately there seem to be all sort of option except this one.
could you elaborate this sentence please?– manooooh
Dec 9 at 17:52
1
@manooooh , I mean like when you tipe
...{umlfragment}[**type**=<option>]
; the options areloop
,opt
,alt
,seq
, and so on. But when I try typingref
, all I get is a fatal error. If then I comment this portion of the code, I get, almost, the right output.– Fr3d
Dec 9 at 18:49
1
I tried the code from your other question with
type=ref
in theumlfragment
instead oftype=loop
, and that worked fine. Can you show the code that doesn't work?– Torbjørn T.
Dec 9 at 19:28
@Torbjørn T. WHAT SORCERY IS THIS!! It works fine in my code as well now.... Very, very strange.
– Fr3d
Dec 9 at 19:53
I voted to close as unclear as the problem seems to have gone away on its own, making it hard to work out the cause.
– Torbjørn T.
2 days ago