ShaunR

Still reeling from that one eh?

1. Read from spreadsheet file. 2. Delete array element. 3. Write To Spreadsheet file. Either way its only a 30 second vi. How easy do you want it?

Even Excel cannot save its own page breaks to a text file.

Ummm. VI, TCPIP, UDP. IMAQ, Bluetooth, IRDA?

As Asbo said. You have to select a scale that shows the minor markers.

I think I see. Like this?

Sorry. Here it is in a version you can open.

Here you go

Its what I expect since I think of refs similarly to pointers. An unitialised pointer is a "null" pointer (no memory allocated). But I think Daklu thinks of them as references to objects and that by placing it on the diagram the "pointer" is allocated. So I got the impression (rightly or wrongly) that he expects a reference to an uninitialised ref to be the same as an initialised one since it is the same object. In that respect. Daklus last image seems prefectly normal to me, however it is an "unexpected" result.

I'm not sure its is that smart. It basically just typecasts the ref to a U32 (or maybe an I32) and compares the values. It does the same for VISA and IMAQ sessions. If you think about your uninitilaised references, the value when typecast is 0 which is not equal to its value if its initilaised.

Its more of a reboot than a reset. The state depends on what you have set the power-up states to be from MAX and the position of the DIP switches (refer to the manual)

Told you I get confused as to which propery nodes need closing of the refs

Sweet

You can't help but laugh AT them in this

Try this Although I don't know whenter it will reload the vis if the vis in memory aren't modified. LV might ignore it if it doesn't think anything has changed. But you should really be checking in/out and merging since its really a source control issue.

Not quite sure what your getting at here since the project is just an organiser. You can set a directory to autopopulate which will cause it to react when changes to the organisation take place. Individual vis can be reloaded by selecting "revert" which forces a reload from disk if the vi has changed (you can use an invoke node for this).

Interesting. You don't get any of those when you click on "Code Repository" in the menus at the top (the way I went )

And these " LAVAcr standards" are documented where?

I think it needs to be approved or something. It doesn't appear in my file list but I can see it in the repository and edit/download etc (and its a different colour to the others). If I click on the link its there, so must be just the uploader until its approved.

You'll probably need the "Embedded Module For Blackfin" http://www.ni.com/labview/blackfin/

The short answer is you cannot. You cannot change the text attributes of a single column/row and you cannot embedd child controls into the cells. What you can do is make it look like that is what it is doing. For thee password display, you can replace the text after the cell is edited using the event structure. You will have to keep another copy of this column since you will be overwriting the cell contents. For the combo-box, you can overlay an array of menu-rings or enums. You will have to manage resizing if that is required.

Watch this space insted. PassaMak

Well. Yes and no. It uses .NET so its a bit like saying a vi creates Word documents when, in fact, it is an automation interface to Microsoft Word and Word creates the document. No word, no document. No .NET, no messages.

Well. What can I say. It'd take me a week to figure out whats going on in that spaghetti. I would suggest thet you keep the diagram open while running and when it no longer responds, click the "Highlight Execution" button (the lightbulb). That will show you where it is currently executing. That will at least narrow it down.

Be even better if we could catch windows messages in the event structure!