Dr. Damien's Development - Creating an Enum from a Text Case Structure

[Ben]

That and much more.

It presented a picture control that you could create your states as shown here.

All of teh shift register and eunum editing was all handled by that tool.

You could even watch your state diagram run in exectution highlighting mode so oyu could see which state is was getting stuck in.

Ben

[Vaibhav]

I searched the LabVIEW help before posting the previous message, but ah, didn't search the forum.

Ok, it seems the State Diagram editor is part of an extra tool sold by NI, right? I have LabVIEW full development system (at Univ.) but I think we don't have State Diagram Tool as part of the standard package.

[Ben]

It is not shipped with any packages any more. It was replaced and forgotten.

Ben

[tst]

---

F. Schubert wrote:

You suddenly get 1000 of properties some developer inside NI did need for some very specific thing. 90% you don't need (that's confusion + lost), 9% will crash because you don't know how to use them and it's not documented (lost), 0.9% are the things that give you benefit but the remaining 0.1% will be destructive.

---

I don't think these numbers are anywhere near accurate. First, we should separate the concepts of "scripting" and "private" - scripting features are features which can create, read or edit LabVIEW code. Private features are just features which have not been exposed. There is some overlap between the two, but it's not absolute. Second, most of the scripting features are logical, stable and well thought out. They're also necessary if you want to manipulate LabVIEW code. There is a part which is obscure and which can crash LabVIEW or do bad stuff, but that's a relatively small part. The majority of scripting is reasonably safe.

[Vaibhav]

Thankss Ben!

I quickly started searching the forum after posting in order to avoid notifications that I should look forum first. 😉

and you already replied.

Yes, in the forum I saw people talking about something like Visio and thanks for that image, that I can at least see what is it.

And your post solved several mysteries from the past.

In the book "LabVIEW for Everyone - Graphical Programming Made Easy and Fun," I read the author talks about "the outgoing state /the next state is automatically selected from the enum" and this term "automatic" was still bugging in my mind, because I always have to select the outgoing state manually from the enum constant I creat from that shift register on the right side of the diagram's wall. Now I understand it's from that state machine created from this tool.

Also, when talking with my professor who works with LabVIEW, he told me that previously he has seen a tool which actually "creates" the state machine after we create a state diagram using some graphical tool and we can actually see the highlight while execution.

Thanks!! Now will wait for your release of the new State Diagram Editor... 😉

[Vaibhav]

---

tst wrote:

---

F. Schubert wrote:

You suddenly get 1000 of properties some developer inside NI did need for some very specific thing. 90% you don't need (that's confusion + lost), 9% will crash because you don't know how to use them and it's not documented (lost), 0.9% are the things that give you benefit but the remaining 0.1% will be destructive.

---

I don't think these numbers are anywhere near accurate. First, we should separate the concepts of "scripting" and "private" - scripting features are features which can create, read or edit LabVIEW code. Private features are just features which have not been exposed. There is some overlap between the two, but it's not absolute. Second, most of the scripting features are logical, stable and well thought out. They're also necessary if you want to manipulate LabVIEW code. There is a part which is obscure and which can crash LabVIEW or do bad stuff, but that's a relatively small part. The majority of scripting is reasonably safe.

---

so let me get it correct here.

the scripting is LabVIEW's internal code (something like what makes LabVIEW)?

[tst]

---

Vaibhav wrote:

so let me get it correct here.

the scripting is LabVIEW's internal code (something like what makes LabVIEW)?

---

In a sense. Scripting is a set of features (properties, methods, events, etc.) which allow you to write LabVIEW code which can analyze or edit LabVIEW code.

Here's a simple example of a piece of code which assumes the first object on the diagram is a property node with a cluster property. It creates a control for that cluster and then inserts a BBN on that wire, so that you can select a specific element of the cluster. Generally speaking, if you don't know what scripting is, you don't need it.

[F._Schubert]

Shall we really discuss scripting/private properties here? I for myself don't like it on the public support forum.

Is is still not a public supported product, given by CARs filed by NI employees that say 'this should not have been public' or the other way round 'this should be public under the scripting license'.I am very happy about the support they give as now (dedicatated place to discuss) and the support they gave us before (in the other forum).

Felix