LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Y Controls Version 1 - Ready for Guinea Pigs

Y Controls are an alternative to X Controls and Q Controls.  This table illustrates some of the differences:

Table.png

 

Unzip the installer.  Read the ReadMe.  Run the installer.

If you're curious, look inside the source.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 1 of 21
(2,231 Views)

Maybe not.  I'm finding newly introduced bugs.  Stay tuned.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 2 of 21
(2,181 Views)

OK, throw away that other one and try this one.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 3 of 21
(2,152 Views)

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

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 4 of 21
(2,105 Views)

@paul_cardinale wrote:

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


We're watching!

0 Kudos
Message 5 of 21
(2,080 Views)

A few images or a PDF would help greatly in judging whether one should give it a whirl or not.....

Message 6 of 21
(2,067 Views)

@Intaris wrote:

A few images or a PDF would help greatly in judging whether one should give it a whirl or not.....


Indeed.

 

I glanced over it.

 

A big reason for QControls is the inheritance of control properties. If you create a string child, you inherit all the string properties. That's the entire set property for the entire control class hierarchy is implemented with VI class methods .

 

At a glance, YControls seem XControl based, and they don't have this ability. That is a huge downside.

 

I couldn't tell at a glance how\if you solved this.

0 Kudos
Message 7 of 21
(2,059 Views)

wiebe@CARYA wrote:

@Intaris wrote:

A few images or a PDF would help greatly in judging whether one should give it a whirl or not.....


Indeed.

 

I glanced over it.

 

A big reason for QControls is the inheritance of control properties. If you create a string child, you inherit all the string properties. That's the entire set property for the entire control class hierarchy is implemented with VI class methods .

 

At a glance, YControls seem XControl based, and they don't have this ability. That is a huge downside.

 

I couldn't tell at a glance how\if you solved this.


From an instance of a Y Control (which is a cluster) on a front panel, the (only) visible element is an instance of the Facade.ctl.  You can right-click on that cluster element and create a reference, property node, or invoke node to access all the methods and properties of the facade.

 

There is an XControl hiding inside Y Controls; but it's just a helper used to capture certain events, it doesn't impose it's limitations on Y Controls.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 8 of 21
(2,052 Views)

@Intaris wrote:

A few images or a PDF would help greatly in judging whether one should give it a whirl or not.....



How about this.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 9 of 21
(2,050 Views)

That chm for me looks empty. I see the index, but it shows nothing where the actual documents should be.....

0 Kudos
Message 10 of 21
(2,040 Views)