Guenther

Hi PJM, yes, that is a good solution to make the frame thinner. Just what I was looking for. Thanks! Guenther

OK, I found a way but this is really REALLY cumbersome. The inspiration came from an older thread in LAVA: http://forums.lavag.org/index.php?showtopic=105 The idea is to have two arrays with color boxes behind each other, with the color boxes in front slightly smaller so you can see the box in the back as a frame. The box in the front array is embedded in a cluster with invisible frames so here the frame takes care of the spacing. Important: For the front array drag an array control to the front panel and color the array background transparent BEFORE you drag the array element inside, otherwise you won't be able to see the back array. This is really tedious, I wish NI would give us more control over the cluster frame. Cheers and :beer: Guenther Download File:post-3733-1152197366.vi

That's what I did - the frame is invisible but it's still there. The gap between the elements is consists of the invisible frame...

Hi VDB, I tried that, but if I make the cluster smaller the visible area of the controls inside the cluster is also reduced and the frame remains the same. :headbang: I didn't find a way to disconnect the visible area from the cluster frame. Any more ideas? Thanks, Guenther

Hi guys, I'm trying to build an array of 2 nested color boxes, which are in a cluster. The idea is to have the inner box display the state of the array element and use the outer box for a kind of highlighting frame. It works all fine but when putting the cluster into an array the cluster frame separates the elements and if there are a lot of small color boxes the frame tends to eat up most of the display area. I've used the cluster control from the classic controls and made the frame transparent, but it is still there and is visible as the gap between the elements What I would like to have is like the right part of the picture (just an array of color boxes, no cluster) but with the nested pair of color boxes. Any ideas how to remove the frame around the cluster or at least reduce its width? Thanks a lot!

You can use a string indicator, which is usually hidden. If the user enters an illegal character, make this indicator visible and display the error message. To show the user which one is the offensive character, you can use the text.selection property on your string control to highlight it. The string control has to be in key focus for the highlighting to work. Good luck! Guenther

You're right. I've got the error in LV8.0, now with 8.0.1 it works fine. Looks like NI fixed that. One bug down, plenty more to go. Greetings Guenther

It's even worse: Using 2 different string constants as "seeds" for the arrays - just as Jim did - reproduces the error on my machine. BUT: using just one string constant - and everything works fine! Now thats some really funny behavior Guenther

Here is another one: Bundle your array elements with a random number as first element, sort the resulting cluster array, and then throw away the random number.

The option you mentioned applies only to sub-VIs. If you want to close the main VI, you need to use the "Quit Labview" function, which you'll find in the application control palette. However, this is only advisable for VIs compiled to an .exe file, since it will close down LV entirely and you might even lose some unsaved changes. Good luck Guenther

This is a very annoying behavior of LV8: When I stop a running program within a subroutine (either with the abort button or Ctrl-.) sometimes it happens that the front panel of this subroutine or an upper level VI is being minimized - and I'm not talking about minimize to the task bar but shrinking the front panel to a less than stamp-sized area in the upper left corner of the screen. Then I have to drag it larger again manually. Not really serious but very annoying. Hasn't been fixed in LV8.0.1 Any ideas? Guenther

Hi TNT that worked! What you see is not always what you get. THANKS!! :worship: Guenther

I need an array of radio buttons, each which its own label next to it. Because of the array, I can't use the caption or boolean text properties. So I put the radio button control in a cluster, along with some string controls next to the buttons. However, the string controls now show shadows underneath them, see the picture. I guess this is because the radio buttons are by themselves a cluster and the string controls are not really a part of this cluster, but on top of it. I tried to get rid of the shadows by using a classic string control and making everthing transparent (left button), but it didn' t help either. Any ideas how the get rid of the shadows? Thanks Guenther

So, it doesn't look like there's an easy way out. Guess I'll have to live with the 2 copies. Thanks for pointing that out, Aitor!

Hi folks, I want to call a VI from the same main VI one time as a standard sub-VI, later as a dynamic VI. The 2 instances do not run at the same time, but consecutively. The sub-VI call runs allright and so does the dynamic call, the VI works allright. Trouble starts, when I want to read an indicator of the dynamic instance, then I get an "invalid refnum" error. If I use 2 identical copies of the sub-VI with different names, using one as sub-VI, the other as dynamic VI, everything is allright. Is there something in LV that prevents me form doing such a thing or am I doing something wrong in the dynamic calling part? I hate the thought of having 2 identical copies of a VI clogging up memory. :thumbdown: Thanks a lot! Guenther

Hi keb go to "VI properties" (right click on the icon) -> window appearance -> Customize and activate "show front panel when called" This will open the front panel of your sub VI Hope this helps Guenther

Download File:post-3733-1136821779.viHi Folks, I came across some very strange behavior of the index array function in LV8. There is problem when you mix readout of single elements and rows or columns within one index array function (see attached VI). If I open the VI as is, I get a compiler error. A click on the broken arrow tells me that the code could not be generated. However, none of the error messages actually tells me that it is the index array, which is making trouble. Now the funny thing: when I delete the second output wire from the top, everything is ok! So you actually have to use the output to reproduce the error - that's why the sequence is there. The workaround is simple, split access to single elements and row into separate functions. I came across this when it opened a VI that was working fine in LV7. Spent quite some time to track it down. Hope this is of help to somebody.