All Activity

I like it and I want to play around with it, but I feel like most of those examples you gave could be accomplished with subpanels, or 2D picture controls set to the top of the Z layering.

Custom Menu(With Glyphs)?Ring with custom drop down list? Floating Toolbar?😁Relace everything that can't be customed

Okay that is kinda cool. Other than an on screen keyboard, what uses are there for this?

Hi guys,here is the final solution NoActVITest_LV2015.zip

The automatic shutdown feature is implemented by a "watchdog", which watches for the launching actor to stop running and sends the message. This has the advantage that it always happens, even if the launching actor stops due to an out-of-memory error or hitting the stop button, but it has the disadvantage that shutdown happens only after the launching actor has stopped.

For some reason I had assumed that the top level actor waited for child actors to reply to the boilerplate shutdown message. I will use your suggestion in the future, thanks!

Here is an example from one of my Apps, where I shutdown multiple subactors (in an array) and wait for all to reply that they have fully shutdown (I'm using Scatter-Gather to allow all to shutdown in parallel):

I would suspect your problem is that your app closes the main window before its finished all its shutdown operations like your INI file. That is fine in source, but it is my understanding that Windows will kill a process with no open windows (Google is failing me on confirming that). Things to try: Command your subactors to shutdown and wait on their replies before stopping the top level actor and closing the main window. Then you know your subactors have executed their shutdown actions. If there is a reason you can't tell them to shutdown (and you have to rely on auto shutdown). Then you need to keep a window open until your code has a chance to execute it's cleanup, so Windows doesn't kill you first.

I use subpanels frequently for UI management of instrument actors in a large SCADA application. Everything works well until shutdown of the top level actor. I am seeing some evidence that the child actors running in subpanels do not shutdown gracefully. For example in the cleanup case of my subpanel actors I have the following code which attempts to save the actors control settings to an ini file. This works fine in the IDE but fails in a built exe. As far as I can tell the vi reference is still viable at the start of the Cleanup case but the ini file does not get written to. Subpanel references are handled by the messenger framework automagically so I am wondering if there might be something going on I need to consider. Also I added the Save Default Profile message which I can call from the top level prior to shutdown and that seems to work in the exe.

Hi, can anyone with experience with using Messenger Library on RT please have a look at this question and see if they can help: https://forums.ni.com/t5/JDP-Science-Tools/Issue-with-Child-Actors-on-cRIO/td-p/4484658 I'm afraid I haven't had an work on RT in years and have no access to an RT system to debug so I have difficulty helping.

Sorry I missed this. I'm afraid I have no time to work on PQ myself at the moment but I would happily look at your PR. Those all sound like features that wouldn't be problematic.

IIRC LAVA used to allow it

Why is the XKCD mage URL (for hotlinking/embedding) blocked for posting? -> "The link could not be embedded because that URL is not allowed."

xkcd: Dependency

I see that as a testament to quality. No contact, no bugs.

Ohh well, I guess I will post all releases from now on with a disclaimer: Use at your own risk! 😁 "But nobody will be using them anymore after that!" Maybe, but it's not like a huge difference. The feedback one received in the past was virtually zero anyways, so not sure there were many people using it at all. 🙃

I think the main issue (and probably the reason for the question originally) is the Cyber Resilience Act which basically makes everybody legally responsible for software they use. There are carve-outs for opensource but the only real way forward is through what they call "Software Stewards". I wouldn't stick your head above the parapet for OpenG. The next question will be "where's the SBOM and CVD Policy" The way forward would be for NI or JKI to name themselves as "Software Stewards" for OpenG but it's a big ask for American companies.

I'm actually maintaining the LabVIEW ZIP library in this repository: https://github.com/Open-G The other projects in there are not active as far as I can see. After Sourceforge more or less succumbed to the Gods of advertisement under Slashdot ownership, the OpenG project on there was relocated to different repositories by different people. I happened getting involved by the person who did the OpenG Github repository and relocated my own copy of the LabVIEW ZIP library in my Github repository to that location. But the OpenG Github repository does not seem to have any other activity unfortunately. The package for the library is however posted to vipm.io on each release. I would not be opposed to spend some time on real bug fixes for other libraries but don't see much beef in adding new features to them. So far they work still surprisingly well for me after more than 20 years of existence with very little trouble. The most serious is probably the missing support for Maps and Sets in the Variant Data Library, but that is something I haven't really needed until yet.

I'm a bit late to the party, but this is a great use of the Tag Engine and muParser. Use cases like this were exactly what I had in mind when I released those libraries. I've also been asked several times about implementing something similar. One suggestion would be to always use labels rather than captions. Personally, I would never consider using captions for this purpose. I would also introduce a flag character, such as @, as the first character of the label to indicate that the control's value should be updated automatically. Another improvement would be to allow the user to specify whether a control should be updated on a tag value change event or on a periodic interval. For periodic updates, I'd have the control values refresh every X milliseconds (user-configurable), with the timer reset whenever a control value change event occurs. Perhaps the second character of the label could be used to indicate this option, with periodic updates as the default behavior. Why update periodically? In many systems, data arrives much faster than it needs to be displayed on the UI, so periodic updates can reduce unnecessary processing. I would also avoid writing directly to tag values. Instead, I would use a Tag SetRequest event. In my view, the UI should not write directly to tag values. Hmm... maybe use the third character of the label to decide this? Looks like maybe all of these flags need to be contained within some brackets. Parsing labels as expressions is a nice idea. It had never occurred to me to do that. My usual mindset is that if a value is important enough to be displayed on the UI, it should already exist as a tag. Anyway, all this to say. Thanks for sharing what you have done. Nice video. And it would be great if you could share the source code so that everyone can try it out and learn from it. And maybe even improve it.

Individuals still are interested in maintaining the OpenG packages. They have been copied a few times, and several repos are on github. I think the most up to date ones will be from here. They look like they were last updated around 2 years ago. VIPM.IO hosts the packages, and you can make comments, and feature suggestions there.

Is the OpenG Suite (distribution of open source LabVIEW VIs and application) still maintained at the following?: 1. https://github.com/Open-G 2. https://www.ni.com/en/support/downloads/tools-network/download.openg-libraries-for-labview.html#379041 I am not seeking if it's supported or if there's guarantee of future maintenance. I am seeking as of this point in time, is the OpenG software maintained, such as if there was a vulnerability documented, specifically a CVE, this project would patch it or release a message denoting they're not going to patch it (the why or why not is not important per this yes it is maintained or no it is not maintained per URL above for the purpose of this question - understood if it depends on the component). Thank you for your time and for creating these tools.

Me too, for the compane. I got fed up with deleting connectors every time I created a new VI.

I still leverage the VIT method in the New... VI >> From Template. It allows for selecting from a variety of New VI templates. Instead of overriding the installed functionality. Admittedly it is a couple more clicks.

This is the nine year-old link I've saved for this - Solved: Re: New VI - default window size - NI Community It behaves oddly in that if you change it and close it before saving, it won't prompt you to save. Anyone understand this?

I searched with the subject line above and got way too many hits, so I apologize if this is already covered. If so, just point me there. How and where does one save a default VI that will be automatically loaded whenever you do File - New VI or rubber band code and Create SubVI? Several years ago I knew how to do it for New VI, but I found recently that NI changed the way things are referenced. Any assistance will be greatly appreciated.