But what type of state machine would you put there? Enum? String? etc...? A state machine isn't a structure - it's a design pattern, and NI's current method of giving you design patterns is to list them as templates (the list you get when you select File -> New).
Hmmmm. I wonder if it'd be a better idea to have a category in the palette that simply links to those items - then you'd be able to get access to all of them (state machines, producer/consumer patterns, etc).
btw: I absolutely think it's a good idea to put items that you reuse in the palettes, but IMHO that's what VIPM is for.
I was thinking of a pretty simple SM with an enum. Something that could be dropped down to create a fairly simple program. This would give the novice user a starting point.
This idea is already implemented in a different way. Go to:
File > New > VI > From Template > Frameworks > Design Patterns > Standard State Machines
There are two benefits of the current implementation: it shows the State Machine architecture in the context of several other architectures, and it's far out of the way of people who have their own templates! I would not be opposed a single palette item called "Architectures" or something that links to the "New" screen.
Message Edited by JackDunaway (mechelecengr) on 10-01-2009 10:30 AM
I'd give a negative kudos to this idea if it was possible.
The palette is full enough as it is. As already pointed out: design patterns don't belong here.
The proposed link to the architectural templates sounds reasonable, though.
One additional thing to think about:
There is no simple way to have a template that uses more than one file.
Every enum-based state machine needs a least two files: one VI and one type definition for the enum (using enums that are no type definitions is close to architectual suicide, IMHO).
Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.