Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/13/2018 in all areas

  1. The introduction of parallel, read-only access for DVRs in LabVIEW 2017 adds a great deal of flexibility to using DVRs to monitor values in parallel executions of code. Fo\The downside of this, of course, is the necessity of using the In Place Element (IPE) throughout your code simply to read the value. Having IPEs throughout your code just to read a value both takes up block diagram real estate and also takes more clicks than desirable to insert. Similarly, though less frequently, there are times when you only need to update the value within a DVR without actually performing any logic in
    1 point
  2. Added: Text rendering to hardware accelerated texture Time based animation and physics Race and captain strings in sidebar Three players! (Not really sure if this is sensible as it is going to complicate the AI, just was easy to implement, could actually do N players in current framework) Three-layer parallax scrolling stars Thrust dots Lots of code tidy-ups LabMelee v2 2018_07_13 20_08_11.mp4
    1 point
  3. I can't say I support the use of the Write DVR Value. The point of using a DVR is to protect critical sections of code (ie avoid race conditions). If you are just randomly writing a value to a DVR without doing the Read-Modify-Write protection, you might as well use a Global Variable and get better performance.
    1 point


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.