paul_cardinale

2 hours ago, X___ said:

Still can't seem to be able to access the Help. Certainly not in the Help -> New -> Y Control -> Y Controls menu and the chm file still doesn't work for me?

It seemed quite straightforward when I first installed it, but maybe the UNinstall step messed up with something?

I just uninstalled 1.002 and tried again the release from post 22 and am without an easy way to find Help within LV (and the chm file is not working anymore as a standalone) 😞

Uninstall deletes "C:\ ...  National Instruments\LabVIEW nnnn\resource\plugins\Y Control\*",  "C:\ ...  National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm", and removes the Y Control from "C:\  ... National Instruments\LabVIEW nnnn\resource\plugins\NewDialogFiles\ LVNewDialog.xml".

Is the installer creating "C:\ ...  National Instruments\LabVIEW nnnn\help\Y Control\Y Controls.chm" for you?

Y Controls.chm

There were some missing dependencies in the source zip.  I also renamed a library to make name collisions less likely.

Y Controls Support Version 1.0.0.2 Installer.zip Y Controls Version 1.0.0.2 Source.zip

On 11/25/2020 at 10:44 AM, The Q said:

I just added an explanation of how to add to the New dialog on the LabVIEW Wiki:

https://labviewwiki.org/wiki/New_dialog

If you have any ideas to help me make QControls better, let me know.  I have a thread on the QControl Enthusiasts page:

https://forums.ni.com/t5/QControl-Enthusiasts/QControl-Usability-Improvements/td-p/4101397?profile.language=en

Perhaps you might find this useful.

Update File_New.zip

That issue has been corrected (see attached files).  However it won't fix already-created Y Controls.  To fix them, make sure that Facade.ctl and the .yctl file are set as "TypeDef" and not "Strict TypeDef"

Other improvements:

• The installer and uninstaller will ignore RO status of an existing installation of Y Controls.
• The wizard fixes up the label of the cluster in the .yctl file.

Y Controls Support Version 1.0.0.1 Installer.zip Y Controls Version 1.0.0.1 Source.zip

I've made some minor improvements.  Is anyone interested?

Unzip the installer, read the READ ME, run the installer, read the help (LabVIEW -> Menu -> Help -> Y Controls).

If you're curious, look in the source.

Y Controls Support Version 1.0.0.1 Installer.zip Y Controls Version 1.0.0.1 Source.zip

On 11/25/2020 at 2:36 AM, Antoine Chalons said:

This looks interesting, I've created a QControl and really enjoyed the concept, haven't dug too much into Y controls but it looks interesting, are you developing this alone or as an open source project?

I get the same error when building the VIP, you should post here I think : https://forums.jki.net/forum/5-vi-package-manager-vipm/ to get some support, JKI is usually quite responsive.

I managed to post the issue there, but it's very cumbersome because I only get one post per password reset (and their Contact Us link is broken).  I did get a reply and was able to solve that problem, but now it throws error 1357.  Maybe it's time to throw in the towel on VIPM.

4 hours ago, The Q said:

I just added an explanation of how to add to the New dialog on the LabVIEW Wiki:

https://labviewwiki.org/wiki/New_dialog

If you have any ideas to help me make QControls better, let me know.  I have a thread on the QControl Enthusiasts page:

https://forums.ni.com/t5/QControl-Enthusiasts/QControl-Usability-Improvements/td-p/4101397?profile.language=en

Gee, I put all my ideas into Y Controls.  Attached is my help file (still under construction) for Y Controls.

Y Controls.chm

I've been developing it alone, but I'll take any help I can get.

Sometimes I get this (which makes no sense because that VI is not a dependency of Y Controls, and it is not missing)

I have invented Y Controls and I am trying to create a VI Package for installing them.  I would like it to result in "Y Control" being an option when selecting File -> New from the LabVIEW menu.

But my .vipb file doesn't seem to do anything; no output, no errors, just a big NOP.  Any help would be appreciated.

Y Controls.zip

The Mac equivalent of LabVIEW.ini is at:    <volume> / Users / <username> / Library / Preferences / LabVIEW.app 20xx 64-bit Preferences

You can edit it directly.

I just came across this:

Apparently there's an XNode developers forum somewhere.

1 hour ago, MarkCG said:

Is there anything like Xcontrols in NXG? I didn't think there was

That's my point.  No XControls, no physical quantities.  If LV 20xxis abandoned I'm doomed!

1. I like to use physical quantities when the values represent physical quantities (such as is common with device drivers).
2. When the code to run a control starts getting complicated, and the owning VI is already complicated, I like to encapsulate the code that runs the control into an XControl.
Am I doomed?

Ok.  As an alternative, is there a way to get the tab key to function as a tool selector on a block diagram that's in a SubPanel of a running VI?

(It seems that the VI that owns the SubPanel is swallowing the keystrokes).

I want to turn AutoTool on.  Shift-Tab toggles AutoTool on/off.  That would be useful if there is a way to check the state of AutoTool.

Is it possible to programmatically change the inheritance of a LV class?

I'm working on a test executive framework (for both test execution and development).  The test step editor places the block diagram of a test wrapper VI in a SubPanel.  It works fine, but when the framework is running, within that panel, you can't change tools by tabbing.  I want the test executive to turn on AutoTool selection so the test engineers using it won't have to.

Thanks for the reply.  Close, but that will just toggle the state.  I need to set the state to ON.

Is it possible to programmatically turn Automatic Tool Selection on & off?

I found a ToolNumber property, but it always throws error 1028 (LabVIEW: (Hex 0x404) Attribute selector is invalid).  I have no idea what that means.

Try this.

ms path.vi

If you have a malleable VI (.vim) inside an XNode,

and an instance of that .vim has a declined frame of a type specialization structure,

and inside that declined frame you call a VI owned by the XNode,

and you have a build spec that copies and renames the XNode,

Then that renamed copy of the XNode will be broken because the item in the declined frame isn't properly linked.

Is this what you are trying to do?

My Script.vi My Template.vi Setup Static VI Ref.vi

I'm pretty sure that you've built your block diagram incorrectly.  Just do it right and it will work fine.  (Since you didn't provide any code, I can't be more specific than that.)