Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Mathcad Prime 9
Is it possible to define the text for axis or traces annotation/labels as variables?
If I define a variable X_axis_title with the value "Measurement" and try to copy-paste this variable into the title field of the X-axis, it will be handled as plain text "(@LABEL VARIABLE X_axis_title)".
Goal is to show "Measurement" as annotation and have the possibility to change this in multiple diagrams at once.
Solved! Go to Solution.
@Werner_E wrote:
@StuartBruff wrote:
@Werner_E wrote:
@efröhlich wrote:
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
Fully agreed on. The chart component as a whole is a very poor integrated stopgap solution for a better equipped native plot solution.
From time to time insiders here post PTC's plans for improvements in upcoming versions, but while I remember that some improvements (not sure which) for the native plots are in the queue, I can't remember having read anything about label parametrisation. That would certainly be a very welcome thing, though.
The whole API needs to be exposed for the plotting component. In M15, you could get at quite a lot of 3D plot attributes through the components script, including, ISTR, the Title. It's standard in many of the other big "M" applications. So, I expect no less from the Mathcad Prime nn upgraded plot component.
Stuart
Could you be more specific concerning "nn"?
Guess that there may be big differences between the ‘nn’ expected in a maths software, the ‘nn’ hoped for and the ‘nn’ realistically expected in Prime.
😈
All I can say with any certainty is that n is an integer of some kind, maybe, but it may very well be multiplied by 1i for n>m where m may also be a number,. The other n is sort of similar, sharing the same name but not necessarily the same value.
Stuart
Not as far as I know and I'd be delighted to be corrected. However, ...
Note that the Title is just an overlay and isn't attached to the Chart, so you need to select the Title as well as the chart if you want to move, copy or cut the chart.
Stuart
Instead of using the evaluation of a simple string variable (still showing the equal sign) you may use a Text Box with the string variable as its input. We can at least format fore- and background color and text size as well as setting the box read only. I don't think that we can get rid of the border line around the box.
The method of creating labels by overlaying text boxes or math regions sure is suboptimal. Of course we would wish for a better integration of the chart component in Prime - not only by providing labels defined by Prime variables but also by being able to deal with units - IMHO thats mandatory for an add-in to this software. Personally I would prefer getting rid of the slow and clumsy chart component altogether and improve the native plots with grids, labels and all the features provided by the component.
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
@efröhlich wrote:
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
Fully agreed on. The chart component as a whole is a very poor integrated stopgap solution for a better equipped native plot solution.
From time to time insiders here post PTC's plans for improvements in upcoming versions, but while I remember that some improvements (not sure which) for the native plots are in the queue, I can't remember having read anything about label parametrisation. That would certainly be a very welcome thing, though.
@Werner_E wrote:
@efröhlich wrote:
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
Fully agreed on. The chart component as a whole is a very poor integrated stopgap solution for a better equipped native plot solution.
From time to time insiders here post PTC's plans for improvements in upcoming versions, but while I remember that some improvements (not sure which) for the native plots are in the queue, I can't remember having read anything about label parametrisation. That would certainly be a very welcome thing, though.
The whole API needs to be exposed for the plotting component. In M15, you could get at quite a lot of 3D plot attributes through the components script, including, ISTR, the Title. It's standard in many of the other big "M" applications. So, I expect no less from the Mathcad Prime nn upgraded plot component.
Stuart
@StuartBruff wrote:
@Werner_E wrote:
@efröhlich wrote:
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
Fully agreed on. The chart component as a whole is a very poor integrated stopgap solution for a better equipped native plot solution.
From time to time insiders here post PTC's plans for improvements in upcoming versions, but while I remember that some improvements (not sure which) for the native plots are in the queue, I can't remember having read anything about label parametrisation. That would certainly be a very welcome thing, though.
The whole API needs to be exposed for the plotting component. In M15, you could get at quite a lot of 3D plot attributes through the components script, including, ISTR, the Title. It's standard in many of the other big "M" applications. So, I expect no less from the Mathcad Prime nn upgraded plot component.
Stuart
Could you be more specific concerning "nn"?
Guess that there may be big differences between the ‘nn’ expected in a maths software, the ‘nn’ hoped for and the ‘nn’ realistically expected in Prime.
@Werner_E wrote:
@StuartBruff wrote:
@Werner_E wrote:
@efröhlich wrote:
Thanks for the "help".
Placing a text box on the diagram like a post-it sticker is a quite poor workaround, even if this is doing the job more or less.
From a commercial software tool I expect better performance.
In which unknown future will such a label parametrisation be available?
Fully agreed on. The chart component as a whole is a very poor integrated stopgap solution for a better equipped native plot solution.
From time to time insiders here post PTC's plans for improvements in upcoming versions, but while I remember that some improvements (not sure which) for the native plots are in the queue, I can't remember having read anything about label parametrisation. That would certainly be a very welcome thing, though.
The whole API needs to be exposed for the plotting component. In M15, you could get at quite a lot of 3D plot attributes through the components script, including, ISTR, the Title. It's standard in many of the other big "M" applications. So, I expect no less from the Mathcad Prime nn upgraded plot component.
Stuart
Could you be more specific concerning "nn"?
Guess that there may be big differences between the ‘nn’ expected in a maths software, the ‘nn’ hoped for and the ‘nn’ realistically expected in Prime.
😈
All I can say with any certainty is that n is an integer of some kind, maybe, but it may very well be multiplied by 1i for n>m where m may also be a number,. The other n is sort of similar, sharing the same name but not necessarily the same value.
Stuart
Hi @efröhlich,
I wanted to see if you got the help you needed.
If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.
Please note that industry experts also review the replies and may eventually accept one of them as solution on your behalf.
Of course, if you have more to share on your issue, please pursue the conversation.
Thanks,