Michael Aivaliotis

nice try yen...

Please report ALL problems to NI. We are just lucky by a fluke coincidence that Mr. Mercer from NI reads LAVA. Honestly, if you don't submit these issues to NI they will NEVER be fixed. If they respond that it is a known bug or issue, then you can request the CAR# and then post it here as a reply.

Find attached a LV 8.2 project that demonstrates this. Run the example VI in there. The problem is that the scrollbar on the multicolumn listbox (MCL) loses the keyfocus after a few seconds. This causes the user interface to feel like it's "locked-up". Download File:post-2-1169442686.zip

Well that sucks!You can, however, place them inside a cluster. With some programmatic trickery, you can position them automatically and you can get an array of references where you can set properties (color, etc) to a specific element. Cluster to array and array to cluster primitives help here. i think this type of thing was also on the CLA test.

No problems for me. I did the following: Create new XControl Placed a numeric control on the facade from: Controls>Classic>Simple Numeric Rightclick on the numeric and selected: Fit Control to Pane. Saved the XControl Plopped it on a blank VI panel. That's it.

When you're knee-deep in coding\debugging, and the VI is staring you in the face, the easiest thing is to double-click the VI. That's how I work.A side note: It seems like NI is putting in more and more hinderances with every new LV release to "force" people to use the Project Explorer more. Maybe I'm wrong but i can give a list of changes that are making me frustrated.

I would take it easy on the condemnation. A lot of this stuff is not super protected. It just requires some one with a little sense of curiosity and the ability to use Windows file explorer. You know, it's really ok to browse inside your C:\Program Files\National Instruments\LabVIEW 8.2\resource folder... Keep up the good work Aitor!

Oh, great! This saves an extra step. Thanks :thumbup: for the undocumented tip. (At least I didn't find it).

When you open a reentrant subVI from the block diagram (double-click), LabVIEW opens a clone of the VI instead of the source VI. The title bar of the VI contains (clone) to indicate that it is a clone of the source VI. Does anyone know of a shortcut way to open the reentrant original (not the clone)? Currently it's a pain in the rear! I have to double-click the subVI which opens the clone, then I have to hit ctrl+M to go into edit mode. LabVIEW then opens the reentrant original (in addition to leaving the clone open) then I have to perform a slight of hand and somehow click on the X of the clone VI panel so I can close it then switch back to the reentrant original for editing. It's obvious that no-one at NI went through this scenario too often because if they did, they would realize what a pain it is and would have probably come up with a shortcut already.

I need a way to get the current mouse cursor type. Is there any way to do this in LabVIEW? I need this because I want to know when a user's mouse is hovering over the divider between two columns of a multicolumn listbox. I figure that if there was a way to detect the cursor change then this would be a good indicator.

Response back from NI support: So, my request from the LAVA community: If you care to change this back to the 8.0 behavior then send a feature request to the indicated link. The best solution in my opinion is to be able to select between both behaviours.

This worked in LV 8.0 but does not work in LV8.2. If you right-click on a control and select "fit control to pane" then you resize the panel, the control doesn't resize in real-time with the panel scaling. It only resizes after you have finished resizing the Panel. The proper behavior is to have the control resize dynamically as you resize the VI front panel. This has been submitted to NI support.

Pretty freakin' awsome!!

<object width="425" height="350"><param name="movie" value="http://www.youtube.com/watch?v=V1z7fFBrjmA"></param><param'>http://www.youtube.com/watch?v=V1z7fFBrjmA"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/watch?v=V1z7fFBrjmA" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object>

I guess the question is, why even make the release public it in the first place?

Can you attach the Facade VI showing this? I still can't find it in your last attachment.

Have you tried this? Does it work? The reason why I'm asking is because in order for you to use the references from within the Property nodes, you have to set State Changed boolean to TRUE every time you update the references from within the Timeout case.

It behaves the same on my machine as well. I guess the timeout does not apply to network connected resources? What's also interesting is that if you set a timeout > 15 secs, it STILL returns after 15 secs.

I ran it on my machine and it works great! Excellent work. :thumbup: Yet again, another case study in the argument for opening up VI scripting to the masses. Can you explain how this would work a little bit more? I didn't see this implemented anywhere in your template. Is this a manual edit step in the process?In general, you shouldn't do real work in the timeout case but perhaps this is the only way.

When I think of XControl, I think of XWife or XArcade. It used to be a control...

You can configure properties in XControls so they appear nested when selecting them from a right-click. See here.

I'd like to post an update to this thread. Yes, there is indeed a way to create so called "pull-right" properties for XControls. Someone from NI informed me of a way that is not officially supported by them but none-the-less works. All you need to do is change the localized long name of the property to include the nesting. For Example: If you have a property called My New Nested Property 1 and you want the menu to appear like Mike->My New Nested Property 1, set the Localized Long Name to Mike:My New Nested Property 1. Colon is used as the separator. Further experimenting reveals you can also create line seperators by replacing the name completely with a hyphen "-". Of course, this means you lose access to the property since now it's not selectable. You would probably create dummy properties to support this.

Well, I'm not too upset with the current implementation. What I find a little annoying is to make all those Method and property VI's. Then you need to do more work in the Facade. What I would like to see instead is just let us register the methods and properties RIGHT INSIDE the Facade event structure. Then we can do the work in one place. This could potentially be done along the same lines as dynamic event registration. An additional side benefit would be that you now will know exactly what property fired and when.

What kind of hardware are you using to do this?

I understand that the Display State control of an XControl can be used to store the current internal state of the XControl. One thing I don't like however is that every time you update this data from within the Facade and set the State Changed? value to TRUE, it triggers the caller VI using the XControl to show an asterix in the Titlebar which indicates that the VI has changed. I understand why this is happening, however it's not desirable if you're just keeping some temporary internal values in the XControl which only last for the current lifetime and you don't care about saving them. One alternative I guess would be to use an un-initialized shift register on the Facade VI to keep these variables and not use the Display State data. One limitation with this method is that the data would only be accessible from the Facade and not from the Methods and Properties. Another possibility would be to create a LabVIEW Class for the XControl. I want to avoid that since I don't want to open another can of worms. I'm already having enough trouble trying to get my XControl implemented in the first place.