Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. FragRz I have the evaluation version of 2018 , so i looked into the 'User Interaction:Compare VIs XML and it does just what I need .... I will have to wait until we upgrade to utilize it ... Thanks Dan
  3. smithd

    LabVIEW Memes

    I'm not bothered by the size of that guy, I'm bothered that everything is serially executing
  4. i think those variant functions should be a tiny meaningless fraction of the overall execution time. Have you profiled it?
  5. Today
  6. ShaunR

    LabVIEW Memes

    Lol. Bonus points if you have one of those VIs on each virtual desktop. Keep 'em coming.
  7. Does anyone have issues with blocking calls when used in parallel processes? I would like to deserialize data in multiple parallel processes, but the "from JSON Text", that in turn calls the "JSON text to Variant" function which uses the NI utilities for determining variant data types. These are set as non-reentrant and as they are protected, there is no way to change that. Am I stuck up poop creek without a paddle here?
  8. Dissapointing. I've managed to work around most of them but the one that prevents me from publishing is that I can't get rid of the xControl making the host VI dirty and requiring saving (a nested xControl). Still. It's OK for my personal use as I can put up with that.
  9. Bob, I just saw your document. WOW! Thank you for contributing that to the community. I'm looking foreward to reading it!
  10. There is a private method called 'User Interaction:Compare VIs XML' which is able to compare VIs and generate an HTML report. I didn't test it too thoroughly but I think it's worth looking at. I currently do not have LabVIEW 2012 and do not know if it is available in this version. Compare_Private_17.vi Compare_Private_12.vi
  11. I don't know of any hooks. That's not the same as saying they don't exist.
  12. No. Not all, and not any. There are some major bugs -- like the circular dependency bug with LV classes* -- but most of the issues people have with XControls are features, intended parts of the design. It's a bad design. Seemed like a good design when it was put together, and it does some things very well, but it's inflexible. When coupled with some of its loading idiosyncracies, it means that a lot of ultra complex XControls just don't work or require arcane code. But the issues are fundamental to how XControls are structured. Fixing them would not be backwardly compatible -- it essentially means rolling a new YControl (or whatever we name it) feature, and that's not on the docket for LV 20xx at this time. If XControls work for you, then they work. If they do not, they don't. I do not expect any shift in this in LV 20xx. * If loading your class loads an XControl into memory then you should take care that loading the XControl does not load the class into memory. Conversely, if loading an XControl causes a class to load into memory then you should take care that loading the class does not load the XControl. If you ever have an XControl that is circularly linked with any class, various forms of doom will come upon you, from random crashes to infinite hangs. It's a known issue with no way to resolve given the design of the XControls (the classes are just fine).
  13. I mostly post these over on Twitter, but here's some LabVIEW memes I've made: LabVIEW Style Checklist: "Size the block diagram window no larger than the screen size." Me: ✅
  14. Thank you for asking a lot of good questions. I have got NI to start a QControl Enthusiasts community group. Some of your questions and suggestions would make great topics there if you are willing to add them. The Link is: https://forums.ni.com/t5/QControl-Enthusiasts/gp-p/5383?profile.language=en
  15. I tried to make it so you could do it from a new project but it always had problems (that is why I warn against it in the tutorial, it wouldn't work every time). I'm going to put some time into making this better.
  16. That is true. I have thought about using the "Not shown as Icons" to get the same look as a Invoke Node or even creating an Xnode (but I have never created one of those before). A polymorphic would give you a list of the VIs included in it but not the ones inherited from the class hierarchy which are available too. A cool tool that does give you all of the methods available is MGI's Class Method Browser (MGI's Website | LabVIEW Tools Network). I do need to add some more templates and scripting. One of which would be to help make Properties from the items in the State Data. New Method templates could be helpful too.
  17. Weird because the wizard calls the same code the examples call.
  18. @The Q In the manual, you write (7.3 Methods): I don't see any example of a public method in the examples coming with the toolkit, so I am trying to figure out the intended use. My understanding is that if I want to add a method to a QControl (say, "Add Element"), I need to provide a VI which the user needs to use wherever they want to call that method, rather than having the convenience of using an Invoke Node and connecting the QControl refnum to it (which would be neat, as this would provide a built-in list of methods). Do I get the idea right? It sounds like a polymorphic VI for those methods could do the trick of providing a list of methods, and using VIs not shown as Icons would bring us close to an Invoke Node: The VI above has nothing to do with QControls, it's just borrowed from my own approach to the same problem (of native control enhancement), but it shows what I mean. If that makes sense, I wonder whether this is something that could be added to the Wizard? Something like "New Method from template" that would add a VI to (or create if there is none) a polymorphic VI and let the user define the number of parameters to use for that specific control (or fix that to one, I could live with either option)...
  19. Yesterday
  20. ShaunR

    LabVIEW Memes

    My first ever meme prompted from this post
  21. I doubt there are plans to fix any of the bugs. Some of them have been going pretty much since the start.
  22. Not the words I would've used There has to be a meme that can link GoT and NI inter-departmental politics.
  23. As I stated before, I don’t know what the replacement for XControls will look like in NXG. However, the work you spend writing XControls now will likely have to be repeated when rehosting that functionality to NXG later. QControls are all regular, plain G under the hood and therefore there is a higher likelihood that they could be portable to NXG. I have attempted to port the whole toolkit to NXG a while ago but have not tried recently. I don’t know what it would take to make a NXG QControl Toolkit but I do think it will be possible. If it can be done, then time spent now on creating QControls might still be usable in NXG.
  24. After much googling I think I know the answer , but , I will ask here... I need to write a utility to compare vi's in a large project , and probably future projects.. Automating the Compare Hierarchy is pretty simple , but , I need to go one step farther and and show the differences circled then saved as a jpeg etc.... As of now there doesn't appear to be a way to automate showing the differences , it will be a real pain to have to do it all manually ... We are currently using LV 2012 , but , will be upgrading to either 18/19 soon... Dan
  1. Load more activity
×
×
  • Create New...

Important Information

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