Jump to content
News about the LabVIEW Wiki! Read more... ×

DTaylor

Members
  • Content Count

    50
  • Joined

  • Last visited

  • Days Won

    10

DTaylor last won the day on February 28 2018

DTaylor had the most liked content!

Community Reputation

27

About DTaylor

  • Rank
    Very Active

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    2011

Recent Profile Visitors

677 profile views
  1. DTaylor

    Control References Node

    Did RegisterAddon.exe not run at all, or are you thinking it ran with incorrect privileges? I do see RegisterAddon.exe run every time I install.
  2. DTaylor

    Control References Node

    I think the included license is OK, we have a handful of users successfully using the trial, though you're the first to try it on Windows 10 (I don't see why that would matter). I did see the invalid status come up once when I was testing, though I don't remember the cause. If you uninstall the EM Control Refs package and re-install it, does it fix the issue? Would you be able to post a screenshot of what you're seeing? Thanks!
  3. DTaylor

    Control References Node

    Language-independent update just landed! For those curious, the node was creating some property nodes and setting the selected properties by the property's name, which varies from one language to another. We just needed to update it so that they were set by the property's unique ID.
  4. DTaylor

    Control References Node

    For right now, this node only support English LabVIEW installations. We are working on a language independent update.
  5. DTaylor

    Control References Node

    We have an internal tool at Erdos Miller that we've turned into a product. It's a node that outputs a cluster of references to all controls on the front panel. A free trial is available for download here: http://info.erdosmiller.com/node-control-references-software-download-v1 It replaces code like this: With a single node: It also lets you: Bind the output type to a typedef. Include a reference to the owning VI and/or the owning VI's front panel. Exclude references to controls above or to the left of the origin. Optionally exclude controls individually. Controls on tabs are organized into page clusters. Try it out and let us know what you think!
  6. DTaylor

    Default VI file name

    Using this is almost assuredly a violation of license agreements: http://www.hmilch.net/h/labview
  7. DTaylor

    XNodes Prevent Inlining

    Why stop there? It seems like there are a few nodes that disallow inlining even though it seems like it should be fine. Now we can just wrap them in an Error Ring.xnode!
  8. DTaylor

    XNodes Prevent Inlining

    I think you can! It looks like the compiler exception doesn't check the fully qualified name. You can put your inline-safe XNodes inside libraries to namespace them, and name them all Error Ring.xnode.
  9. DTaylor

    XNodes Prevent Inlining

    I think there is just a special case that LabVIEW knows the XNode named "Error Ring.xnode" can be inlined. If I rename an XNode to Error Ring.xnode, the aforementioned error goes away. I wonder if there is a way to whitelist other XNodes.
  10. DTaylor

    XNodes Prevent Inlining

    There is a VI in the same directory as the Error Ring XNode named XSFP_ReplaceSelfWithGenCode.vi. I don't know if this has anything to do with this behavior. I've seen some private methods prefixed with XSFP - any idea what it stands for? That VI is not a member of the XNode, but I agree that none of the XNode's abilities or properties look like they have anything to do with the inlinability.
  11. DTaylor

    XNodes Prevent Inlining

    I did , and the owning VI shows no error when it's replaced with it's generated code.
  12. DTaylor

    XNodes Prevent Inlining

    Hmm Error Ring XNode does work for me, but others that I think should be inlinable are not, like the Butterworth Coefficients XNode.
  13. DTaylor

    XNodes Prevent Inlining

    I'm also seeing this if the XNode contains only nodes that can be inlined. It appears that a VI that uses any XNode cannot be inlined, regardless of whether the generated code can be inlined or not.
  14. DTaylor

    XNodes Prevent Inlining

    It seems that using an XNode in a VI in which inlining is enabled always generates the error: "This object is not allowed in a VI on which you enabled inlining. Disable inlining or remove this object." Is this always true, or is there some XNode ability that would allow it to be inlined?
  15. DTaylor

    LV2017 Parallel DVR Access Bug?

    I can confirm as well. Parallel read-only access is broken until this is fixed. I played around with the bug a little bit, and it appeared as though up-to-date data fails to make it out of the SubVI when parallel read mode is enabled (super weird).
×

Important Information

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