Michael Aivaliotis

try this.

Your definition of a block as related to the array information does not jive. In any case, regardless, what you probably want is to use the array subset function. You can feed in the start index and length of the the elements you want. This should handle what you want.

Yes, you are correct. I've been throught this exact dilemma before. There is no object (decoration) that mimics the WinXP themes stuff. This is a real wish, to tie-in somehow to the winXP skinning.

I agree with PJM, attach an example please.

I don't see this posted, if it is, oh well. Make your coercion dots stand out by making them bright red:

More annoying singing people... I don't know what this is but.. I gotta get me some of that!

I say let them have it! People who've been programming in a bubble all their lives need to be shaken up. I'm sorry, how else are we to improve the overall quality of the stuff we have to dig through on a daily basis. Let's say it like it is. It's crappy code. I sometimes see it here on the forums too, people parlaying "advanced" read: obfuscated, programming techniques. My answer to customer's requests for feature additions to existing badly written code: No problem, anything can be done (it really can). It will only cost you x dollars. If they disagree, all the better, I need my weekends for personal time, not for digging through some interns "learning" project. I just hope if you are the programmer who ends up doing the fix that you are honest with the customer about the amount of work required. Let's not whore ourselves out to the lowest bidder. Bottom line, as long as I have breath in me I will educate and preach proper programming standards, regardless of the audience response. Hopefully, if enough of us blow in the right direction, we can start a wind of change in the world of badly written LabVIEW code.

So, the moral of the story is... Provide a test harness to test all VI's before release. A much simpler preventative measure would be to position the inputs and outputs at the same alignment. This way you don't have to think too much about wiring mistakes. Having them swapped like that is asking for problems. Another thing in this example is the coercion dots. Correct connection removes coercion. The coercion in this case would raise a flag to the programmer. This is why I change the colour of my coercion dots to bright red instead of the dull grey.

Well, why put the burden of figuring out which panel is active on the operator? It's the developer's job to make this obvious right? One solution is to hide the panel that does not have the focus. Programming this is easy but the problem is that the operator will be confused when different panels become visible or invisible. The reason behind this behavior is not immeadiatly apparent to them. Another solution is to leave everything as it is and just flash the titlebar of the VI which has the focus. This can be done using the windows API utilities that are available on NI's site and other places (i wish I had the link handy). I believe this will even flash the bar if it is minimized.

Convert your flat sequence architecture to a state machine. See the FAQ for more information: What is a state machine?

Still waiting for your summary...

This does not seem to be a problem in the "classic" version of the table. I assume you are using the default 3D one. This is probably a bug but there is a workaround that "unlocks" the colour picking on the background. See the attached AVI that shows the solution. Download File:post-2-1126592671.zip As you can see, the background colour selection "unlocks" once you hover over the first (far left) user defined colour.

Khalid, this is correct however it appears Fernandotid has LV61 so the solution is slightly different since that method changed in LV70. Also, there is a method that operates ONLY on the ctrl of interest. No need to capture the entire panel, only the graph. Find an image attached of how to do this in 61. PS. Fernandotid, considering the Forums just saved you $495, why not donate some of your new found wealth to LAVA?

Wishfully... Read again....

Hmm, this is a neat trick from that site:

See here and here for some ideas.

Coding Challenge Ok, LAVA Members You think you've got what it takes? Do you want to own a very desirable Grey LAVA T-shirt and White Mug? All you need to do is participate and win our first official LAVA coding challenge. Challenge Description: Model the ripple effects of moving a mouse over a liquid. Download the following AVI movie to view an example of the challenge. Download File:post-2-1126486112.zip The minimum requirement is that your mouse disturbs the background image when hovered over it. The disturbance must be as close as possible to that of a liquid (ripples). The size of the image must be 500px wide by 200px height. You may use IMAQ tools and viewers, however the goal is to accomplish this challenge using the default picture control that comes with LabVIEW. If you know of a better native way to do this in LabVIEW, go right a head. For bonus points you can implement the following features: Ability to load any user defined image (jpg or gif). Hovering the mouse over the image produces a light ripple effect. Click and drag the mouse produces a more pronounced ripple effect (waves). The liquid density can be configurable. Include random droplets of rain. Include wind effects. Include falling leaves. The toplevel VI submited must be named Making_Waves.vi and can be stored in an llb file if desired. The use of sub-vi's is allowed. Please include them all. Scores for this competition will be based first and foremost on the functionality of your model and realism. They will also be based upon coding style. For help with coding style, see Chapter 6 of the LabVIEW Development Guidelines attached: Download File:post-2-1126488648.pdf Note: All coding must be done in LabVIEW. No external code, DLLs, CINs, exes, ActiveX, .NET, etc (DLL's or libraries that are part of the core LV are allowed) Have fun! Submit all solutions to: codingchallenge@lavausergroup.org. Do not post them to this thread. The deadline is Nov. 30th 2005. You can use this existing thread to discuss the challenge or to ask questions. Good luck! PS. The winner will have the choice of showing a special icon next to their name on the Forums. They will also have a special signature image. The details of these images will be revealed soon.

Your solution is very nice. This is why I love the LAVA Forums... Great exchange of ideas. Keep it up guys... and gals.

Too many colours: Bad. Default OS attributes + colors: Good. Icons on buttons with text: Good. BTW, Irene, To reduce the amount of work, reduce the colors. Use the OS attribute. This way if they don't like the colors then let them change the OS colors which in turn will automatically change your panel colors. PS. Color=US, Colour=Canadian\British.

Very Nice! Now if only it would remove transparency when I hovered over it with the mouse and then return transparency when I remove the mouse. I would program it myself but I think the Mouse Enter event is only available in 7.1. Hmm, you could possibly create a timeout event and monitor if the mouse enters one of the dial controls.

Yes, picture as intended... But I am not a closet user since I don't actually use them.

Icons on desktop are bad form in my opinion. I hide them all, How can you find anything like that? Very messy and useless. How many applications do you really use on a daily basis? Put those in the root of your start menu. It's hard to think clearly and you can easily click on them by accident when programming. I like a clean slate. No need to delete them, just turn them off globaly:

Yes, your solution is good. Here is another one which is easier to implement and actually works quite nice. BTW, this is also used somewhere in Commander I think: http://forums.lavausergroup.org/index.php?showtopic=67

OOH nice one, I gotta try me some of that!

My customer's look at me strange when I tell them: "I improved the performance of the software by adding a delay". This technique is perfectly fine.