11-21-2012 10:00 PM
11-21-2012 10:12 PM - edited 11-21-2012 11:42 PM
OK, here's one with a numeric control.
(I also implemented it as a solution with several buttons, but I still think an array of buttons is better)
11-22-2012 09:29 AM
Altenbach solution is a better one mine is not bad but his is more modulare and uses less event so there is not as much overhead. the biuld array can give you a little overhead tht is why I chose the insert into array function rather then the build array function. you could use the reshape array function and it should work like the biuld array function.
11-22-2012 10:03 AM
wow I see... it is a very good job!! thank you collegues. I have no much experience in labview, I'm learning by myself, ythat's why I'm asking you, I was two weeks with this little problem. Thank you so much to both!!
11-22-2012 10:26 AM
@Harold_Timmis wrote:
the biuld array can give you a little overhead tht is why I chose the insert into array function rather then the build array function.
The "insert into array" gives you the same overhead as the "built array" function. Both might force a new array allocation due to a change in array size. The most eficient way would be to initialize the shift register at the full final size with an impossible value (-1, NaN, etc. as suitable), then use "replace array subset" to fill with the real data without ever changing the array size again. 🙂
11-22-2012 10:50 AM
I have a last little problem, when I select a limit number and I finish my array, obvious, it is full, but if I select one more number (of push button) the sequence is erased... how can I avoid it?? I just want to store the sequence 🙂
11-22-2012 10:54 AM - edited 11-22-2012 10:57 AM
Which code are you using? Are you re-running the VI? In this case the shift regsiter gets re-initialzied of course. You could use an uninitialized shift register, for example.
11-22-2012 10:55 AM
the last one you published
11-22-2012 11:02 AM
Try this (of course you would need to increase the max size number before re-running).