Rolf K. wrote:
> I have looked at the State Machine Toolkit and believe that it is fine
for
> the standard state machines a lot of users usually encounter but my state
> machines usually always tend to be just a tiny little bit more involved
so
> that I would have to hand edit the generated state machine afterwards
> anyhow and once modified manually you can't seem to go back to continue
> with the State Diagram Editor.
The inability to go back to the editor after you manually edit is true of
most computer-aided wizards. The fundamental problem is that the wizard
knows how to maintain a state machine under certain conditions and how to
modify various pieces when you change something in the editor. Once you
introduce a non-standard component, the wizard has no idea how to handle
that component as the system changes. The
once-you-manually-edit-you-can't-go-back-to-automatic problem covers the
State Machine, Express VIs, and a lot of tools built by just about every
piece of helpful software ever written on this planet. It requires either a
sophisticated AI to recognize all the components that can be introduced
into a system by a user or a very restricted set of things the user can
introduce. Notice how HTML editors handle non-standard tags.
Pojundery,
Stephen R. Mercer
-= LabVIEW R&D =-
"I do not believe that Hell is a physical place. I believe that Hell is an
hour of the morning." -- Jan 16, 2004
