03-09-2010 04:36 AM
DianeS wrote:
To the best of my knowledge, there is no way to fix that directly. What you can do, though, is stick your cluster constant inside a sub-VI, and use the output of that sub-VI to attach to the wire leading into your state machine. Yes, I know it's a bit of a hack, but I do find that it comes in useful for setting initialization values of the cluster and keeping the block diagram looking nice and tidy.
This is exactly what I found a while ago here (Ben's Nugget 5th March 2007) :
Type Definitions Let You See Your Application in a Different Way
http://forums.ni.com/ni/board/message?board.id=170&message.id=233257&query.id=1039466#M233257
@ Nickerbocker :
Talking about LVOOP class, I haven't used them yet but it looks very interesting. I would suggest you to write something about it (Nugget, tutorial, sorry i don't know how you would call it...). I am sure that there are many Kudos to be won
03-09-2010 06:03 AM
You've just created an Action Engine or Global Functional Engine. 🙂
Stick a cluster in a VI and create functions to read and write elements.
They are a great tool and can be read about in LabVIEWs help.
/Y