Adnan

Hi, You must set SceneObject.Blending.Mode to ON.

QUOTE(Aristos Queue @ Dec 17 2007, 11:04 PM) +1. I just bought the Orange box. Portal is really a Great game. What's real gameplay. And if you like multiplayer, you have in the same box the incredible cartoon-like http://orange.half-life2.com/tf2.html' target="_blank">TeamFortress 2.(not really tried yet but i like the visuals).

QUOTE(Falevoz Y. @ Dec 5 2007, 08:35 AM) Sorry, I did not see that it points on the same URL on sourceforge. NB : MSXML is Windows only, thereas LibXML is for Windows and Linux platforms.

Or you can use LabXML(LibXML LabVIEW implementation)

Hi, I am Adnan and I am a lurker. I think, I am a little bit shy and not very self-confident for replying. But I try to heal myself (are we in group therapy? ). People are very unselfish, passionate, and love :beer: . I really like this place .

Here a possible implementatin of Ben idea. We could go further and have different editor for cells (numeric, checkbox, ring). I'm going to try to do an "AdvancedEditableTable" XControl as we could find in JAVA JTableCellEditor

You can convert LabVOOP wire to variant (To Variant function). It gives information on type and value (check show type on Variant indicator). With OpenG' Data tools, you can have maybe these informations formated into String.

You can find this template here : C:\Program Files\National Instruments\LabVIEW 8.2\resource\Framework\Providers\LVClassLibrary\CLSUIP_MemberTemplate.vit

I attached a basic example which update array caption when you clicked on booleans. I hope it helps. Download File:post-1057-1154615177.vi

Indeed, it works well! It seems to be the best solution. Moreover with adding the lines below in application INI file (WriteTimeToFile_LV711.ini), it will hide window in Task Bar. [WriteTimeToFile_LV711] HideRootWindow = TRUE Walx a question : what is the "WriteTimeToFile_LV711.bat" file in your build directory?

I found here an information about how LabVIEW handle the panel and the VI in memory but I'm not sure it was true for every version. To sum up, they suggest that the VI must open a self reference in such way LabVIEW keep it memory. So I made some tests in different versions of LV : 6.1, 7.1.1, 8.0.1 (see Attachment). The code of VI is simple and it is the same for all version (Open Self VI Reference - CloseFP - write date & time in a text file - Close VI Reference). I'm build exe for every version and use it for results. Test machine : PC WinXP sp2 CPU : P4-2.6GHz RAM : 1.5Gb Results : LV61 : always works LV711 : randomly works LV801 : doesn't work It's difficult to me to explain this difference. Someone has an idea ? Rolf, you seem to understand threading rules in LabVIEW, maybe it's obvious for you. Download File:post-1057-1153985925.zip

Great idea !

I use to think so. But It seems it depends on which kind of code is on your BD. I will try to synthesize this and post some example when i have time. I suppose it is due to thread switching as Rolf said.

Deactivate all options in VI properties.Window Appearance (Title bar, Menu bar,etc...) and use Close FP method on start of your VI.

I like Poseidon. There is a community edition, which is enough for most of needs.