From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
10-04-2017 10:09 AM
wiebe@CARYA wrote:
Turning it on sometimes doesn't seem to be enough to turn it on though.
It might need a recompile to show for the first time after enabling the display. Not sure.
10-04-2017 10:27 AM
Can't make them show whatever I do. Changing, running, shift+run, new VI, nothing. And after a while (hours?) they suddenly appear.
10-04-2017 12:02 PM - edited 10-04-2017 12:04 PM
With 2013 the vi often has too actually run to calculate the folded constant before the constant folding is shown on structures. And, if you separate compiled objects from source there are other times the obj cashe may not update the bd graphics. LESSON: use a modern version
10-04-2017 12:12 PM - edited 10-04-2017 12:16 PM
@JÞB wrote:
With 2013 the vi often has too actually run to calculate the folded constant before the constant folding is shown on structures. And, if you separate compiled objects from source there are other times the obj cashe may not update the bd graphics. LESSON: use a modern version
Running does indeed help, but I'm sure I've seen it in idle VI's as well.
EDIT: Actually, after running continuously for a while, it stays on, even after stopping and editing...
Anyway, it's mostly annoying (to me) to have it on.
I'm getting closer to convince my "sponsors" to switch to 2017. Can't be soon enough. I know I'm going to be measurable more efficient, but that's no evidence...
10-04-2017 01:33 PM
wiebe@CARYA wrote:
I'm getting closer to convince my "sponsors" to switch to 2017. Can't be soon enough. I know I'm going to be measurable more efficient, but that's no evidence...
2017 SP1 should be about ready to release (pure speculation on my part). I tried 2017 but had a horrible experience due to a bug (crashes when using the distribution tools). Assuming that is fixed, I will start the process of migrating to 2017 SP1 purely for the Malleable VI feature.
10-04-2017 02:57 PM
...
I'm getting closer to convince my "sponsors" to switch to 2017. Can't be soon enough. I know I'm going to be measurable more efficient, but that's no evidence...
Embrace the Channels Wiebe. Learn to Channel the force data.
Ben
10-05-2017 02:45 AM - edited 10-05-2017 02:48 AM
@Ben wrote:
Embrace the Channels Wiebe. Learn to Channel the
forcedata.
I'm not sure if I can morally cope with using those channel wires. I made some OO patterns (Queue\Queue Sender\Queue Receiver) that do more or less the same. As a replacement for them it will just save time...
To stay in the Star Wars analogies: they feel like a double bladed sword (a term NI uses when features might encourage bad architectures (usually before declining great ideas))..
Malleable VI's, the drag in\out structure auto-rewiring, start up\shut down\load speed, that will save some time. And RSI.