Michael Aivaliotis

Well, the more I work with Xcontrols, the more I realize that there is a SERIOUS lack of documentation or examples for them. Can someone shed some light on the Convert State For Save Ability and how the hell I'm suppose to freakin' use it?

Ok, I solved it. Here it is:

Maybe something like this?

There is possibly an interim option. Every submitted code has a dedicated support thread with it. You, as a developer can post a reply there to solicit feedback if you wish.

Do you mean it shuts down? Are you creating it through the MAX user interface?

Welcome aboard!

Which one is it? Bad performance or wrong answer? Are the values (on the inputs) going into the VI the same as when the VI is run by itself?

Here's a link to the LAVA New Year's eve skypecast. https://skypecasts.skype.com/skypecasts/sky...e390418a378528c

If you want your application to run on a Mac you have to build it on a Mac.

You can get the references to all front panel controls and iterate over an array of them with a FOR loop. Use the property Panel reference then Controls []. You can select the controls you want by getting the label or caption text, or even the type.

Well, my first attempt is not going too well. I made it public instead of private. This means non-LAVA members can join. I also made it 5hrs. I just discovered that you can't cancel a skypecast. So I have to wait until the time expires to start a new one. At that time, I will start a private skypecast and post the link in this thread so only readers of this thread can join.

I've just started one. Apparently you can setup a duration for it and the max is 5 hrs. Search for LabVIEW now... I'll start a new one if this expires. Let's do a new years eve LAVA chat!

Wouldn't you know it, that's the only place I didn't look. Thanks! :thumbup:

Does anyone know where NI keeps the templates for the XControl Method, Property and Facade VI's? I want to create my own which are nicer.

This is the same solution I have come to as well. The problem however with exposing a reference to the end user is that this breaks encapsulation rules. There is the potential of messing around with elements that you want protected. I don't have a problem with re-creating certain properties. If only we could group related properties and use nesting then it would be one step closer. As it stands, you end up with a super long property list.

I agree! I have only been exposed to XControls for a short time. I consider myself a newbie rgarding XControl, however I have already come across the need for this. I sure hope NI is working on this for an upcomming release.

That worked. Thanks.

I tried that but it had no affect.

I'll clarify my question a bit more since your answer is not what I was looking for. If you open up the one and only Xcontrol example which ships with LabVIEW, you will see a custom property called: Fahrenheit Mode? Notice that it does not have any Context Help. How do we add help to this specific property? Now, you can add as many custom properties or methods as you desire. However, you can't add them in a nested fashion I hope this clarifies what I'm after.

I wanted to know if it's possible to create nested properties with XControls. See the built-in boolean properties as an example. Also, how do we create custom help so that when someone hovers over the custom XControl property node you can see help in the floating help window?

Well, there's another way to detect a change. You can detect the column width size before and after and compare the two.

This is easily fixed if you remove the checking in the mouse up case to see if it's in the column. Don't need this check anyway.

Wow jimi, thanks! The VI you posted works great! The trick is the mouse down+up combination.

Using LV8.2. I'm working on an Xcontrol that contains a multi-column listbox (MCL). I wanted to do certain things from inside the Xcontrol based on if a column was resized by the end user. One snag is that there are no events for this on MCL. I tried putting the code inside the timeout event case in the xcontrol but this case only executes under certain conditions. In other words it's not always called. One solution I was thinking was to spawn a parallel process VI (from within the Xcontrol) to monitor this continuously. Any other suggestions?