Vision Assistant 7.1 & LabVIEW Code Generation

[DonRoth]

I have been playing a little with Vision Assistant and would like to make some suggestions regarding the automatic code VI generation feature. I would like to receive comments regarding these suggestions.

First, I think that a control rather than a constant should be generated for individual functions. For a simple example, say I perform a rotation in Vision assistant on a specific image and then perform the code generation. A rotation angle constant is generated for the rotate VI. It would be much better if a rotation control was generated since more than likely you would want to use this VI for different images that would need to be rotated differently.

Second, I believe it would be better to generate code for multi-s
tep scripts that is in a state machine format with case structures for each individual step. Better yet, it would utilize an event-structure based state machine with event cases.

Third, I noticed that code based on region-of-interest draw functions resulted in external windows as image containers to operate on rather than the new front panel image control as the image container, I would rather see the latter.

Maybe future versions of the code generator tool will allow some configuration choices so that the above can be accomplished.

Sincerely,

Don

[BruceAmmons]

Don,

I think the constant is fine. That is how it is set up in Vision Assistant, and it can't tell if you are going to be changing it later. It really isn't that difficult to right click on a constant and select "Change to Control".

I like the idea of the state machine format. It would make the code much more compact, and it would be a lot easier to add/remove cases as well as reorder the steps.

Using the new image control would be nice also.

Bruce

[DonRoth]

Hello Bruce:

Well it is true that it is not difficult to change a constant to a control but why not just have it as a control with the default value set to your constant? One less step to have to manually perform (after all it is supposed to be generating code for us)...

Sincerely,

Don

[BruceAmmons]

If it generated a control for each input, there would be a huge mess of controls on the front panel. It would be difficult to figure out which ones to change and which ones should be constant. Much better to convert the two or three inputs you want from a constant to a control instead of converting the rest from controls to constants.

Bruce

[Cabman]

The Vision Builder 6.0 LabVIEW code generation wizard had the option to specify whether each parameter would be a constant or control. I wonder why they ommited this useful option from VA.