Jump to content

hooovahh

Moderators
  • Content Count

    2,932
  • Joined

  • Last visited

  • Days Won

    199

Everything posted by hooovahh

  1. Here is a quick and dirty edit. It allows for column separators to be moved, but I noticed that on resize it will set the column widths. So this means if you manually move the columns, and then resize the control it may change the columns in an unexpected way. But at that point you can manually move the separators again. I only have 2017 and 2018 so this is for 2017 and newer now. Variant_Probe-2.4.3-0.ogp
  2. There's a little bit of Rube Goldberg action going on here, but I think I follow what you are trying to do. I'd suggest precalculating what all the values are and put that in a subVI. Then call that subVI and index out the current step that you are on keeping track of it in something like a while loop and a shift register. Attached is a simple example. Have you taken any free LabVIEW training online? Here is some on the LabVIEW Wiki. Ramp Pattern.zip
  3. Oh and lets not forget that some cRIOs now support DAQmx so programming the FPGA part is even more optional. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019PUNSA2&l=en-US Some times I find myself changing what things I want to be done where. I might start with an idea that certain tasks will be on RT and others on the Windows host, but as time goes on I realize my decision might not have been ideal. I guess what I'm saying is whatever you do, make sure you let your design be flexible enough, that a total rewrite isn't needed if some part of your software needs to be done on a different target than first intended.
  4. Oh yeah I forgot I used to do this. I'd download things and just throw them into a sandbox folder where I could play around with stuff people posted and see if I can mine any reuse nuggets out of. I'd try to make a text file with a link to where I found it online, but searching the name of the VI in google was usually enough to find where it was being discussed. Still this is less about what OP is asking, and more just myself trying to find and use useful tools.
  5. We generally don't close threads on LAVA, even things like this can be useful to others...assuming you have a solution that is worth sharing so someone in a similar situation can find what you did.
  6. For the most part I just use Google, and the fragments of memory I have. Someone will post something and I'll be like "That sounds familiar, did I help answer a similar question once?" and I'll search "(topic idea) hooovahh site:lavag.org". Beyond that I do have a list of commonly asked questions that I bookmark. Chrome settings are synced if you are logged in so I have a few folders with common links to various threads that I add to from time to time. Sorry I don't have some super magical RSS tool.
  7. I think this is exposing one of the issues NI had with XNodes. One reason I was told by R&D that XNode development had slowed and halted, was due to the fact that XNodes don't work well inside classes, or more specifically they don't work well in libraries. I couldn't pin point the issue exactly, but it seemed that opening a library would lock the XNode, and opening the XNode would lock the library. I found some working solutions that were all terrible but I just couldn't get the IDE to work nicely and I suspect an XNode in an XNode has the same issue and I think name space was partly to blame.
  8. That's good to hear, I guess I don't need to use this meme.
  9. Thanks for the update. There's lots of reasons to see less activity on the forums. Life happens, people get stretched, people get bored, people change careers, etc. I personally try not to take your activity, or others like you, for granted. And any contribution you make to the community is always appreciated.
  10. You've probably already seen it, but there was an announcement made.
  11. That is odd. I've been getting the same warnings for a long time now but my EXEs are build just fine and work as expected after hitting Ignore a few times.
  12. I'd disable PC sleeping and hibernation, disable power management, or set it to performance, and make sure USB ports aren't being put to sleep for whatever reason. Does this happen on all USB ports? Is this through a hub? Beyond that do you have any odd software running that might be scanning for USB devices? Some employers install software to lock down the PC and it could be interacting with it in a weird way.
  13. I'm pretty sure the item selection in that tree means nothing, and setting it to -1 and disabling it might be the best option so not to confuse the user. All that matters is what items are selected with the checkbox. And even the checkbox acts like a radio button where only one item can be selected at a time. You can of course have multiple controls in a QControl, but it will only inherit from one class.
  14. As far as I know it is still happening. As usual we are a bit behind in the planning but as of right now it is still on, details to be posted when we have them.
  15. I asked a similar question a while ago and Dr. Powell chimed in with what he believes it means. EDIT: Oh and a thread where AQ explains that having a clone reference doesn't keep the main VI from leaving memory. If it does it will close the clone references that you still have a handle on and can cause crashy.
  16. I just tried with another command that is in the system folder which is "dir" here is the command line string value I used: cmd /c dir "C:\Example Project" /w This was with the Working Directory being empty.
  17. Just for others worried about CLA-R, be sure and look into the Recertify by Points, that Fab mentioned earlier. The CLA was so hard and I barely passed and never want to do it again. Luckily I'm certified until 2023, and already have some points towards certifying again. I realize not everyone wants to put in the time into getting points, and some don't have enough time to get them before certification expires. But if you have a local LabVIEW user group in your area you get 5 points for attending and 10 for presenting. You also get 15 points for participating in an NI beta. This means if you participate in 2 LabVIEW betas, and attend 4 user group meetings a year, you'll have enough points to recertify in 2 years. But of course valid criticism of NI's recertification is welcome.
  18. Is the file read only? Or protected in some way in the file system?
  19. And here are a few more links with examples from LAVA.
  20. Only if you are okay with wiping away all other setting from LabVIEW. I prefer a package method which edits my LabVIEW.ini leaving the things there that the user or base install has set. It adds some QuickDrop shortcuts for instance, but if those shortcuts are already taken (because of user preferences) then it leaves them. On uninstall of the package it removes these shortcuts, but only if they were installed in the first place.
  21. I don't think XNodes would help with this. XNodes are great for making a single thing on the block diagram do different things and encapsulate functionality in it. But there is no front panel connection with an XNode. The best you could do is maybe make an XNode, that internally links to a control reference on the FP. You'd still have the normal control terminal on the block diagram because I don't know of a way to make the control terminal itself invisible. If I could then then that would be a solution, but likely full of hacks and who knows if it actually would work well. And then you'd be dealing with a technology NI isn't interested in making more public. If QControls did have an XNode component, and it could essentially replace the native terminals and references, then I'd suspect NI would be less interested in making it part of the LabVIEW core. One nice thing about QControls today is how it is normal pure G, which as you mentioned might be why it has a hope for being ported to NXG.
  22. Okay to be fair, QControls don't actually extend the VI Server tree, but from a developers perspective the outcome is the same, or close enough to not matter. You drop a property node, and you get get access to all the same things you're used to, and the new things. It looks like a duck, but might not be a duck. I can see why code changes in one place effecting the other can be weird, and for that I can think of a few ideas that are probably terrible. I haven't used them extensively yet, just working on a few ideas, but since it solves so many of my XControl problems, and adds just a couple problems of its self, I'm okay with it. I too wouldn't be surprised if NI doesn't invest in XControls, or an alternative. But then again for current LabVIEW I didn't expect that to get any better anyway.
  23. You are incorrect they do and it is amazing. Here is a slider that I made into a QControl and I have all the normal slider stuff, but then have the extra stuff I added. It isn't perfect, like you can see the "Scale" normally opens up another submenu but in this case it just returns a reference, but with this you can then do the same stuff. Or you can just reference the original control instead of this class and do things exactly like you always have but you won't have the new items.
  24. I just started down the rabbit hole of making a new XControl recently. Oh man such a pain. Here is a little graph I made complaining about the XControl creation process, and the time needed to make something useful. Any alternative is appreciated.
×
×
  • Create New...

Important Information

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