Ton Plomp

First of all, our company desktop computers are still win2k, probably going onto XP in may. We the lucky ones with laptops have XP, but the chance that I'm getting a new one within 2 years 20%? On a side note NI has a website about Vista. Ton

PJM, here's my (working) version of OGPB.llb Download File:post-2399-1169792253.zipin 8.2 off course Ton

I like the idea. And besides that, the fact that NI refers to the front panel, so each dialog should have an NI tag... strange... Ton

Thanks Darren, I already ran it and posted it at the OpenG bug forum. (this starts to be a major cross-post issue :laugh: ) Ton

PJM, do you know if it is possible to do a search and replace with a merge VI? would be fun if we could replace the read (and write) variant.config vi's replace with a merged one including the to variant primitive Ton

Last year at my intermediate course this was mentioned as well. VIPM uses the following: LabVIEW

Well that looks not too bad, insert a wait until next inside the loop. Now you need to figure out how to communicate with the database. I2dx has developed hi ado toolkit for this, or NI has a DB toolkit. Or if this is all you need you could try to write your own with the TCP primitives. Ton

Good one you caught, I was trying to start with OpenG Package builder, and somehow couldn't add VI's to my package.... Then I noticed saving and opening of a .ogbd file wasn't consistent the 'Package Files' tab was always empty. I found out that the [Files] section had no entries, debugging let me to this bug... somehow the read-key doesn't suffer from this problem (maybe because there is only one item under [Files]. I also noticed that the Package builder uses a quit old version of the variant config VI's (2.4 instead of 2.7) PJM, have you tested if this happens on all datatypes? If packagebuilder needs to be updated that's quite some work. Probably builder also needs updates..... Or builder should be elimated in 8+ EDIT: In Package builder I have preceded every Write Key (Variant) and Read Key (Variant with the to variant primitive, now the package builder works. I tried to look up every to variant coercion dot with VI Analyzer but the number was a little bit to overwhelming... Ton

Verified in LV 8.2, the variant from Get Variant Attribute returns the last found variant and not the default value (empty variant) Ton

kbllau, you have been a bit lazy in asking the question, next time post some code of what you allready got. Now some advice: break up the code in smaller parts, (or seperate functions), tackle each problem apart. If you have a problem search on the NI forums. They have a much much bigger user base (currently 30:9000 do the math) and are more suit for your beginner problems. It's not that we don't want to help you it's just that you show no effort besides copy-paste from your assignment. Ton

Now we allready have that alpha channel! (does anyone know the color code of transparent) is that just plain 0x00? Ton

Yes, but that is the wrong idea. What you should do is create a system that let's you set the configuration, and starts the actual code when you hit a 'start' button. Put all your code inside a flat sequence, add a frame before put a while loop with a boolean control (name it start or something) inside it, put a wait on next ms node inside (with a 25 ms wait) the while loop. Here you go. Ton

So that's quite clear (what about a animated gif?) Now one advice to NI, when you release it in an official version (I heard rumours about 9.2), give some serious documentation with it. We don't expect that it will be stupid/Jimi proof, we know NI can't do with it what we do for testing. But in the case of XControls the documentation is quite lacking. No information about how it is called exactly when it is called. Sometimes XControls are called without reason, or they loose their state information... Ton

Good catch Jimi :thumbup: Ton

Right click-> rename? Then about the missing and double items.... Maybe a refresh (F5) will help. Or removing one (it will still show up in MAX but greyed out), maybe the correct one will show up. Also make sure the card is in the slot it tells it is (in the properties or something) Ton

My solution is quite dynamic, in your case (I think I know which property you need ), you could streamline the amount of code, but I don't think you can't change it on runtime, so you'll need the dynamic calling anyway. And does the target reference type exist in LV 6.1? Ton

Hello NAGWI, could you convert the DAQ assistant into normal code? (right click and than 'convert to VIs' or something similar) And what is going wrong? You did not mentioned that in your first post Ton PS I see you make progress in asking questions :thumbup:

Hi Jim, I know Jeffrey has done something like this in scripting. I used scripting in my XControl Inheritance property thingy.... (I think I need to come up with some official name), I'll add the related files: Download File:post-2399-1169442833.zip You probably need to modify the template path (and the templates if you want to make them usefull) Ton

No (sorry), I was giving some feedback about it! Ton

One week later... I have spoken to Jim and Michael during the skypecast and noticed that PJM had stopped by. I found out it is very usefull to make the skypecast private (it is always somewhere late at night were people come home drunk). So what about the time? Saturday might not be the best moment... Also the anouncement time was rather short. Next time we need to make the anouncement earlier and set a topic. mballa: maybe the next lava coding challenge is an option to talk about! Ton

Hi Herbert, we use lv to control diadem, but we have one issue with the waterfall display (the new one added in 10.1) we get several heap memory issues (if it happens to show up on your desk, please have a look... (it should contain a zip of 7.7 meg) Ton

The Knowledge Base? Ton

This won't work, you can't place an XControl inside an array.... You should make the array inside the XControl, or just use them apart Ton

Joris, it looks you are looking for 'late binding' with the typecheck features of the LV compiler? Ton

One other option (haven't checked) but I think the project explorer would be the answer. Ton