06-05-2008 05:59 PM
06-05-2008 06:14 PM
06-05-2008 06:23 PM
And here's where we told you why to avoid them for the same code: HERE
... for again the same code... 😉
Three threads for the same code and similar comments about the code...
06-05-2008 06:31 PM
RSibagatullin wrote:
This code is an absolute nightmare, with all these stacked sequences. Where did you get these ideas?????
Why is it a nightmare? Is it becuase it does not look pretty? I am in my 3rd week of learning LV. This code works though. The ideas are mine.
Has nothing to do with looking pretty. It's a bad practice.
To repeat myself, this is why you should use a state machine instead of stacked structures:
06-05-2008 06:46 PM
06-05-2008 07:11 PM
06-06-2008 11:15 AM
06-06-2008 11:31 AM
There must be better ways, by my 2 cent quick fix.....is to manage it with Event structure/value change…
And have a case structure in it, so that if new and old values in “disabled” rows/columns are different, you can take the old value instead of the new ones.
About copy and paste...do you want to achieve the action during run-time by the user or do so programmatically/code?
06-06-2008 11:41 AM
06-06-2008 12:02 PM
I do not know how to paste the entire row like excel. But like everything, LabVIEW has a workaround that works (at least for me).
This is a sample code for my
Once you have it, you can have a Boolean and event structure to manage the copying/pasting action of the selected row.
Best,
Santiago