Deleting Variables.

[medelec35]

If you want to delete a variable, you need to find where each variable is place then delete each occurrence, before Variable can be deleted.
Can there be an option, when you delete a variable to tick a box which will enable all the occurrences to be remove.
So you don't keep getting 'Cannot delete this variable because it is used...' etc

Expaning the deleting, How about an option to allow you to select multiple variable's to delete as well

Although the Find/search option will come in vary handy for deleting also.

Martin

[Steve]

I know this is a problem, especially for larger programs. We have a number of new features coming in V5 that will make this easier.

[medelec35]

We have a number of new features coming in V5 that will make this easier.

Thanks Steve.
V5 sounds fantastic!
Can't wait to see the full list of improvements.

Martin

[Brian Walsh]

Another problem with the deletion of variables is that even when you have removed all blatant references to the variable within icons and therefore satisfied the requirements of the nag box, it is still possible for references to the variable to remain as parameters to functions with no warning.

If such a parameter refers to a now 'sucessfully deleted variable', the net result is the dreaded failure message when attempting to compile, with no hint as to where the problem lies.

Would it be possible to extend the variable deletion warning scheme to search within function parameter lists for undeclared variables and generate a warning of remaining instances.

[medelec35]

With reference to deleting variables:
I believe It's a good idea to label every icon 'Display Name' e.g Input 1, Input 2, Decision 1, Decision 2, Calculation 1 Etc. as your creating your flowchart
Then if creating a large program and deleting variable, then the warning message will display:

Deleting1.jpg (134.52 KiB) Viewed 11521 times

[JonnyW]

Hello. In v5 there will be much more checking and association with icons both before and during code generation, so even if problems like this do slip through, it should be easy enough to find them as Flowcode will (hopefully) know which icon(s) caused the error. Until then yeah, I think its a good idea to give each icon a unique name.

Cheers,

Jonny

[medelec35]

Would it be useful suggestion for V5 to have automatically generated unique number every time a new component macro is used. E.g. if added Calculation 1, then if drag, ore paste another, then Calculation 2 could be generated?

[Steve]

In V5, you'll find you won't need this because locating problems will be much easier.