Visualize a variable (print it) at a diagram?

[heba]

Hi all,

is there a chance to print a variable's value on a diagram?  I tried to do that using a hyperlink, or in a note... but the %VAR% is never expanded.

My last idea would be something stereotyped plus a shape script but this sounds a bit too much

Thanks
Heiko

[qwerty]

What do you mean by "a variable's value"? If you set the run state of an object, it's clearly displayed in a compartment.

q.

[heba]

Sorry for the unclear description.

Using "Local directories and paths..." I set a variable e.g. "BASE_DIR" to a certain path.  I want to display these values at the home page (initial diagram) of the model.

-Heiko

[qwerty]

AFAIK there is no way to show that. You could write a script that creates  an appropriate Note or Text element.

q.

[Graham_Moir]

While you may not be able to pick up the value of the variables directly, as a workaround you could set up a dummy element of some sort, call it say "Environment" and then add a number of tagged values for the BASE_DIR and any other ones you're interested in.  Then place this element on the initial diagram and choose the diagram property to show the tagged values compartment.

[heba]

Thanks, I played around a bit.  But I wasn't able to read the path variable in any kind so far.  It's probably only available to some internal functions

-Heiko

[Graham_Moir]

As I said, you won't be able to pick up the value of those variables, but you could create tagged values that present the same values.   This means duplication, but it also meets your requirement of showing the information on the initial diagram, and as the information is largely static the duplication may be tolerable.

[qwerty]

The path variable is stored in %appdata%\sparx...\paths.txt

q.

[Eve]

As I said, you won't be able to pick up the value of those variables, but you could create tagged values that present the same values.   This means duplication, but it also meets your requirement of showing the information on the initial diagram, and as the information is largely static the duplication may be tolerable.

I wouldn't think this would do the job. Yes, the local paths are static. But the point of them is that they can contain different values for different users of the same model. A tagged value can't do that.

[Graham_Moir]

Ah yes, OK, understood.