Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/16/2020 in all areas

  1. You're right, this needs an example. How you describe it sounds correct. I've had as many as four update Booleans, I think.
    1 point
  2. It's documented in the DEV Template. I use a feedback timeout that is default 0 ms from every case but the Timeout case (which feeds back -1). This makes the Timeout case execute exactly once after the event queue is empty. Use a "Display needs update" boolean flag to record if the display needs updating in the timeout case. One can do this with Queues as well. With this one is able to look at all incoming data, but do expensive display operations only as often as possible (but as quickly as possible). So you could, for example, have information coming in a 100 a second, a
    1 point
  3. You can use the Flush Event Queue function to clear out old events.
    1 point
  4. A Notifier is only usable is you only have one type of message coming in, and your display doesn't include any history, like a chart. Personally, I keep the data transfer lossless, but just make the actual front panel display update lossy.
    1 point
  5. NI Week was a blast and while there I got to mention a few things I was trying that I'd like to share with the community. One of them is this thing I'm calling a Multi Panel Interface (MPI). The code is rough around the edges, very rough. This is probably the least polished code I've posted in a long time but this code has been sitting in a half working state for a while, and if I took the time to clean it up, it might never be ready. So please be gentle, there's room for improvement but I think the basics are there. Now with that out of the way here's what I got. I wanted to
    1 point


×
×
  • Create New...

Important Information

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