UI Interest Group Discussions
An Extensible, Object-Oriented Alternative to XControls
There are two parts to the DataGrid, the right-click menu plugin stuff that controls the configuration dialog and the actual QControl code. Both would have to be converted to LabVIEW 2015. I have been trying to build a VI Package (VIP) of the Data Grid Configuration that I back saved for LabVIEW 2015 with no luck. VIPM keeps having an error while building but I'll keep trying. The configuration stuff needs to be installed first before using the QControl.
Thank you for the nice work. I was looking for C# user control equivalent in LabVIEW and found this QControl kit. I was able to use to create my own fist QControl and make it work 90%. However, I could not make my QControl accept user "key down?" event. Below is a screen capture of Event Hanlder.vi with "Key Down?" case that does not work. In addition, it it possible to enable QControl to accept mouse "left button double click" event?
The Key Down event works for me. Attached is a quick version of a test QControl using the Key Down event to put the pressed ASCII letter in a popup dialog.
My guess is that you have something else broken that is making your QControl not operate. If possible attach your code as a zip file and I'll see if I can help.
Here is a screenshot of my Event Handler.
So I found the problem. The cluster usually doesn't have or get the key focus. Instead, it's one of the controls inside that have the key focus. If you press tab in your tester until the cluster is highlighted and then pressed the keys, it works. In the Event Handler, I added the "Key Down?" event to the other controls so that if they have the key focus it works too. I then discard the Key Down if the keys were pressed so that it doesn't type anything. The fixed version is attached. (I made sure to keep your QControl in LabVIEW 2019.) Hope this helps.
To answer your other question, you do not need to close references to individual controls or indicators. LabVIEW does that for you when the VI leaves memory. (https://forums.ni.com/t5/LabVIEW/Which-references-need-to-be-quot-Closed-quot/m-p/307552/highlight/t...). You do not need to close anything that inherits GObject in the VI Server Class Hierarchy and this includes all controls (see https://labviewwiki.org/wiki/VI_Server_Class_Hierarchy and https://labviewwiki.org/wiki/GObject_class).
I have a follow up question about the example SysInfoUserControl.zip 196 KB you help modified. When closing the Test_SysInfoUserCtrl.vi in the example, DETT reports reference leak in Launch Event handler.vi. BTW, I was able to fix the other memory leak in the other VI highlighted in yellow.
That reference leak is on purpose. The "Event Handler.vi" is launched in the same manner that the "Actor Core.vi" is in the Actor Framework. It will only have one reference leak which by doing so allows launching to be a lot faster.
