LAVA 1.0 Content Posted September 29, 2006 Report Share Posted September 29, 2006 Hi, I'd appreciate the following functionality. When initializing the shift register outside the loop, the developers should be able to define if the shift register will be initialized only for the first call or for each call of the containing VI. This way the first call? case strucure inside the loop would be unnecessary. There is also another advantage. In the future there may be labview data types like objects and references that always need initialization. For objects developer defined constructor may need to be called and references naturally need to point to something to be properly initialized. If there would be a possibility to have LV2 style globals that would still always be initialized, then these globals could also be used with data types that require initialization. Compiler could generate an error if developer tries to wire such a type to a normal uninitialized shiftregister. Third, this kind of initialization makes it possible for the compiler to generate a slightly more efficient code. As a summary, loop left side shift registers should have a context menu option to define if the shift register will be initialized from outside the loop for each call or only for the first call. At persent all initialized shift registers are initialized for each call and to initialize only for the first call a separate "first call?" strucure is needed inside the loop. Quote Link to comment
Gary Rubin Posted September 29, 2006 Report Share Posted September 29, 2006 I like that idea! :thumbup: Quote Link to comment
Jacemdom Posted September 29, 2006 Report Share Posted September 29, 2006 loop left side shift registers should have a context menu option to define if the shift register will be initialized from outside the loop for each call or only for the first call. with an appearance change...like NI did with the while loop conditional terminal between version x.x and x.x (don't remember) Quote Link to comment
LAVA 1.0 Content Posted September 29, 2006 Author Report Share Posted September 29, 2006 with an appearance change...like NI did with the while loop conditional terminal between version x.x and x.x (don't remember) How about very irritating blinking and beeping loop terminal, you can't help noticing it. If it would still have a such a black hole effect that it would such the mouse cursor passing by, it would defenitely be noticed. :laugh: :headbang: Seriously, there should defenitely be a visible difference between these two kinds of terminals. And really not blinking... Quote Link to comment
Mike Ashe Posted September 29, 2006 Report Share Posted September 29, 2006 Another option might be to add a terminal point to the left side shift register and if you want it to initialize only the first time you wire in a "First Call?" primitive. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.