07-19-2020 08:10 AM
For example:
This is something I put in the description before I put the control in the cluster.
And:
After I dropped it in the cluster. Not very helpful. there's no way to edit the button description, either. Not that I know of.
This is a major disruption to my self-documentation scheme, so much so that I completely stopped my experimental project. For example, let's say I was implementing a message to be sent over TCP/IP. For simplicity, the payload is one byte, and it consists of 8 Booleans. I would have a cluster whatever the corresponding document named the byte, along with whatever the description was. Then the cluster would contain 8 Boolean controls with names and descriptions lifted right out of the document as well, so the developer would know exactly what they were looking at, and could directly correlate everything on the front panel to a paragraph in the document.
So now how am I supposed to convey that information (in a way that's as simple as adding a control with the description already embedded)?
Thanks for your thoughts.
07-19-2020 01:56 PM
Works fine in LV2020. Just another reason I'm not interested in NXG.
07-19-2020 09:27 PM
Eventually you will have to, because LV Classic's days are numbered. That's why I'm trying it out on the side. i want to be ready when it comes of age.
07-20-2020 08:52 AM
@billko wrote:
Eventually you will have to, because LV Classic's days are numbered. That's why I'm trying it out on the side. i want to be ready when it comes of age.
Hopefully that number of days is > the number of days 'til my retirement.
07-20-2020 09:10 AM
@paul_cardinale wrote:
@billko wrote:
Eventually you will have to, because LV Classic's days are numbered. That's why I'm trying it out on the side. i want to be ready when it comes of age.
Hopefully that number of days is > the number of days 'til my retirement.
LOL I have to agree there. 😉