11-07-2005 01:34 PM
11-07-2005 02:27 PM
11-07-2005 02:45 PM
Hi Paul,
I am 100% in agreement with Tbob's comments.
See reply # 8 & 9 in this thread
http://forums.ni.com/ni/board/message?board.id=170&message.id=112110&requireLogin=False
for more of my comments and thoughts re:the SDE.
The only problems I recall were
1) back in LV7.0 (?) you had to disconnect from the SD if you wanted to build an app from the code.
2) If you upgrade from LV 7.0 to 7.1 the installer had trouble getting the SDE installed.
3) Trying to over-ride the SDE functions (by wiring to any of the SDE enums) would cause an insane object. But I was doing things to confuse the SDE so this makes sense!
THE SDE is great!
Ben
05-19-2006 01:56 AM
While you are in State Diagram it's impossible to change almost anything and if you unlock code from state machine, you can't add state. Is it anything more stupid than these?
With other words, how can you add state and change state of the Enum constant inside State Machine while you are developing your applications.
I'm working with 7.1.
05-19-2006 08:16 AM - edited 05-19-2006 08:16 AM
Unlocking the diagram should only be done if an application needs to be modified and it will NEVER be edited using the SDE ever again.
It is possible to right click on the enum and edit the typedef.
When done save the control and you should be on your way.
Ben
Message Edited by Ben on 05-19-2006 08:17 AM
Message Edited by Ben on 05-19-2006 08:18 AM
05-22-2006 02:27 AM
As I'm se, there is a new Type Def for Enum that is in one State Machine. Is it possible that you (in the same way) edit State Machine that is made before these nice Tools? I mean to change Enum constant to Type Def.
05-22-2006 07:39 AM
If I understand you correctly, you would like to use the SDE to edit VI's that were created without the SDE.
No you can not do that.
The SDE is similar to the Express VI's and the code produced by the Vision Assistant in that it is "one way only".
To go the other way would be the equivalent of "de-compiling" code.
The following is speculation to attempt to explain the above.
THe SDE uses scripting behind the scenes to edit your code as you indicate by interacting the the SDE diagram window.
It appears to save the enum internal to the VI itself.
The SDE does all of the dirty work involved in making the transitions occur they need to but to do so it needs to track a lot of details.
Again the details are saved inside the VI.
For the SDE to be able to import code of a State Diagram and reverse develp it would first of all require that you developed the SD VI in 100% compatability with the SDE.
Done speculating.
I hope this helps.
Ben
06-05-2014 01:41 PM
Good afternoon. Where I can find and download State Diagram Toolkit? My disposal version LabVIEW 2012.
06-05-2014 02:45 PM - edited 06-05-2014 02:53 PM
06-06-2014 12:40 AM
No, they are different.
The State Diagram Editor is no longer supported. I don't know if it works with newer versions but I'm still using it with LV2012.
It was included in the Developer Suite of previous LV versions (up to 8.x ?).
Do you really mean this toolkit ?