Jump to content

Darren

NI
  • Content Count

    579
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by Darren

  1. 1 minute ago, Jim Kring said:

    I'm looking for a way to change a visible state of a Case Structure, and (A) not have this show up in the Undo Transaction history and (B) not wipe out the undo history. Right now, if I don't create an undo transaction for the visible frame change, it wipes out the undo history :-(

    I don't know of a way to accomplish this. As discussed above, changing a VI with scripting requires the Transaction methods to preserve Undo history. To my knowledge you can't modify a VI with scripting, have that modification not show up in the Undo history, but preserve the previous Undo history.

  2. 6 minutes ago, hooovahh said:

    So on the topic of weird LabVIEW stuff I had a few today.  I noticed a couple my quick drop functions not dropping what they should be.  Now this might just be a result of my custom quick drop shortcuts, but I don't have any shortcuts for the Copy or Delete functions.  I recorded my oddness here.  Anyone seen anything like this?

    Nope, I've never seen that before. You specify the name of a primitive, the thing that gets put on your cursor looks like a Place VI Contents VI of some kind, but then it drops a constant? Go home LabVIEW, you're drunk.

  3. 4 hours ago, shoneill said:

    How does NI propose we document these problems without sending a complete VM with LabVIEW installed AND complete source code for our project?  Sometimes these problems just get swallowed whole by the inconveneice of trying to demostrate their existence.

    I don't have a good answer for this. I run into the exact same issues, and I work at NI! For a while I would file CARs with a [hard to reproduce] tag on them, but I don't think anything ever came of those. I've heard of customers actually visiting NI and bringing their entire setup to get an AE to spend days troubleshooting issues like this, but I think that's overkill in almost all cases.

    One thing I can say...I've heard customer sentiment that it's not worth the time to submit NIER crash reports, but that's absolutely *not* true. With each LabVIEW release since NIER's debut, we've fixed *several* crashes as a direct result of the crash reports that were sent in. So continue submitting crash reports (and attaching code where possible and appropriate), because improving stability by solving NIER-reported crashes is something we're committed to with each release.

    • Like 1
  4. On 7/19/2016 at 7:08 PM, John Lokanis said:

    Why does LabVIEW (almost always) crash when trying to undo the Remove and Rewire and the Insert Multiple Wires QD shortcuts?

     

    On 7/21/2016 at 3:25 AM, shoneill said:

    Crash when undoing QD. QD is buggy or is using unstable methods.  We've had several cases of QD shortcuts creating corrupt control references which ended up costing us days of debugging to find.  Random crashes and general instability ensued.

    I feel confident in claiming that I use Quick Drop more than anyone on this planet. I use these shortcuts (Remove and Rewire, Insert) dozens of times a day. I've never seen the instability y'all are talking about. No crashes, no "corrupt control references". I've also never seen a CAR reported on these issues either.

    I'm not discounting the fact that y'all are experiencing these issues. Believe me, I hate it as much as anyone when the car repair guy tells you that there's no way your automobile can be malfunctioning in the way you describe. But if y'all are seeing these issues as frequently as you claim, why have I not received a bug report that I can investigate? I realize that it's sometimes hard to get things into a reproducible state that can be reported. But hopefully y'all also realize there's not much I can do when the first I hear of these issues in 8 years of the feature's existence is on this LAVA thread.

  5. On 6/13/2016 at 2:11 PM, Darren said:

    Jeff added 6 .vims to [LabVIEW 2016]\user.lib\macros, including the Norm.vim he mentioned.

    Oops, spoke too soon. I saw these in an internal build image and assumed they were in the installer. They are not, so they will not be in the LabVIEW 2016 install. Sorry to get y'all's hopes up.

  6. 2 minutes ago, Aristos Queue said:

    I don't understand. Why would you expect VIMs to have changed anything with respect to events? This is an edit-time feature, not a run-time feature. Can you explain the link that you're seeing? 

    I think ShaunR wrote a .vim that provided the ability to name user events, but it didn't work quite right?

  7. On 6/10/2016 at 5:38 PM, jacobson said:

    Dang, couldn't find this structure in the last LabVIEW build and got 0 hits when trying to find more information about it internally. The thought had crossed my mind that JeffK just made this all up for his own entertainment and while I would be a bit sad, I would definitely respect that.

    I guess I'll have to wait patiently with everyone else until release.

    Jeff added 6 .vims to [LabVIEW 2016]\user.lib\macros, including the Norm.vim he mentioned.

  8. I've noticed similar behavior for other abilities. For example, if you click the drop-down on an Error Ring, then click cancel, your VI still gets a dirty dot even though you didn't change anything. I don't know of any way around this behavior.

  9. Do they throw an error 4 when they read the entire file? (one of my pet peeves)

     

    Other than the error input/output, the functionality of the VIs didn't change. I'm not seeing an error when reading an entire file. I am seeing a *warning* 4 when specifying a number of rows to read greater than the size of the file, is that what you're referring to?

    • Like 1
  10. This is a demo from the presentation Stephen and I gave at NIWeek 2015 regarding the new right-click plugin feature in LabVIEW 2015. You can get the slides for the presentation, along with all the demos (including the spell checker), and a demo script, here:

     

    http://www.ni.com/lvmenus

     

    Note that the spell check right-click demo requires that you have the VI Analyzer Toolkit for LabVIEW 2015 installed, as it uses the dictionary provided by the VI Analyzer's Spell Check test.

×
×
  • Create New...

Important Information

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