Modifying Additional Report data

[[To...]]

Using GDT Position from Beta GDT Engine, with MMC on the considered feature with Additional Report data active.  There is a line of data to report the size of the cylinder to calculate MMC, which adds a name that gets truncated because it is too long.  Does the end user have any renaming capabilities? 

_______________________________________________________________________________________________________________________________________

On a related note, the "default" evaluation for ASME shows Maximum Inscribed for the considered feature but reports as LSQ on the report.  You must manually select maximum inscribed in feature's MMC properties within the Position window.  Data is using .0005 dispersion in simulation.

Edited Friday at 12:40 PM

[[An...]]

Good morning Tom, 

As with most things in life, it depends a little bit on what you're willing to compromise on and how much work you're OK putting into it.

There are a handful of tried and true things. Resizing the text or the text box. This works, but if you want uniform font sizes then I wouldn't recommend it. 

The route that I usually take is using the string operations to manipulate my strings into a more manageable format. I have attached a PDF showing the output of a couple of these, as well as the syntax I used. 

A couple of notes:

• PiWeb is Zero-Indexed (as is correct), so when using the Substring Method, 0 indicates the first letter in the string.
• The Trim method specifically only looks at the end of a string, so if you want to take a little off of the start of the string, use the TrimStart method. Because of this, you can't use any variant of Trim to grab something in the middle of the string of interest. Use Substring in that case.
• You can also use Regex to match and extract string but unless you already are familiar with Regex, the juice isn't worth the squeeze in my opinion.  I didn't include an example on my PDF for this reason. If you're familiar with Regex, there are a couple of String Methods that reference it. Your favorite Regex flavor is probably supported to do more or less what you want.

Finally, the last example on my PDF shows a method that is a lot of work, but it technically does the job. It utilizes the Output(Monitor) property that is buried in the Miscellaneous section of the properties of a variety of objects. This controls if an element is displayed in Monitor, dependent on some condition. In my example, I used the following steps:

• Create a new text box and place it directly over top the text box with too long text.
• In the new text box, enter the text you wish to display instead of the long name.
• In the Output(Monitor) property of the new text box, enter: 

  ${Greater(String.Length("${Qdb.Characteristic(2002)}"),6)}

  This checks if the length of the Characteristic name is longer than 6 characters. If it is, then it displays the new text box. The length parameter can obviously be changed.

• In the original text box, enter:

  ${Less(String.Length("${Qdb.Characteristic(2002)}"),6)}

  This will ensure that if the new text box is displayed, the original is hidden. Make sure the length parameter is the same for both, otherwise you may create a situation in which both text boxes are displayed. 

An important thing to note is that none of this is really "renaming" anything. In the database, the name is still "Really Long Characteristic Name", we are just changing how it is displayed. I figure that you know that, but it's worth saying just in case.

 

Hopefully, this was helpful and answered at least some portion of your question. Let me know if I have missed the mark and I'll adapt my thoughts.

Rename Test.pdf

Edited Friday at 03:13 PM

[[To...]]

Andy, I truly appreciate the effort you went through for this.  For me, it would have been fine if you had hit "Submit Reply" after your first sentence...lol

I probably should have added the word "simple" to my question. Although, I have longed to be an expert at PiWeb. Like Calypso, I have learned so much from others because there's no "how to do everything" manual.

Thanks again.

[[An...]]

You're welcome Tom. I've learned a ton from your posts about CALYPSO, so I'll consider posting what I do have a lot of experience with a way of making us even (only 3400 posts to go).