Saverio

Sorry, mean to say "constant" instead of terminal. But it's still the same. Once you right-click on the constant and make the label visible you can move the constant until you see the label (in case it got shoved way out there beneath another structure) so that you can get your grubby little hands on it. Though as noted, it seems it was just easier to just delete the constant and recreate it.

Technically, it's not broken behavior. The cluster contains two references, but they're different kinds of references. Hence, the Cluster to Array is complaining, since it only works when the cluster contains elements of the same datatype. You can see in the Build Array that there's data coercion on both so that they are being "downcast" to the common datatype of a "lowly" "Control Refnum". You could make the case that the Cluster to Array should be "smarter", but that's a different question, and I think posting it as an idea is a ... good idea.

codeproject.com has several articles on doing impersonation in .NET for this sort of thing. I used one of these in the in-house application I developed at work. Here's one: http://www.codeproject.com/KB/cs/cpimpersonation1.aspx and another: http://www.codeproject.com/KB/cs/zetaimpersonator.aspx and another: http://www.codeproject.com/KB/dotnet/UserImpersonationInNET.aspx Thus, you could take that code and use the assemblies they provide.

Maybe I'm missing something obvious (and it wouldn't be the first time), but if you're talking about the label of a terminal that's hidden why don't you just right-click on the terminal and select Visible Items -> Label?

Ah, that might explain it. Yes, I have AdBlock Plus with Firefox.

OK, but I was confused by this as well. Having to click on the dot didn't seem to be intuitive. It just looked like, well, a dot. I also noticed that the Unread Content seems to have been wiped. When I went in this morning it showed there was no unread content from my last login, which was late last week, and I know there have been posts since then. Like this one. Just FYI. I'm assuming the Unread Content will work correctly at this point going forward. I notice one formatting issue: On the Site News main page there's extra space on one of the threads (see attached). Unclear as to why. I did perform a cache clean.

You cannot send messages from a process that has lower-level access (such as user-level) to a process that has higher-level (such as admin-level) access. However, I don't believe that launching osk in the fashion that I had provided would cause it run under admin privilege. I don't have time to play with this this morning, but I'll try to look at it later this afternoon.

Yes, you may need admin privilege, depending on the task. The taskkiil command has a /u and /p parameter for specifying a username and password to use so the command can be run under that account. Of course, if it's the admin account, anybody who can see the code would also see the password... An alternative is to send the window the WM_CLOSE message, which tells it to close. You can do this with the SendMessage Windows API function, as shown in attached example. Send WM_CLOSE Message.vi

I agree that it's not cross-platform. Unfortunately, a cross-platform solution would need to be implemented by NI directly in LabVIEW. Until then, we're sort of limited to the tools we have at our disposal.

You could simply use taskkill:

Did you make sure to set the VI's execution thread to "UI" as I had indicated? It won't work if you don't.

Which drivers are you referring to? With some drivers some stuff gets installed into the Windows system directory, so you don't have much of a choice there. Have you considered making this suggesting in the appropriate Idea Exchange forum?

Is it just one number that you're getting or do you get an array of numbers? Is the set of bits that you don't care about always the same set of bits? If so, you could simply mask out the bits using a simple AND function with the required mask. For example, if you just want bits 0 and 1 you can mask your measurement by ANDing it with 0x03. Alternatively, you can use the Number to Boolean Array to convert your U8 to an array of 8 Booleans.

For a free alternative you could try PortMon.

Olivier, FYI: your second link point to a non-existent page. It appears you have an extra "s" at the end of "software" You can handle drag and drop by using the Windows API. As a quick way to get started I modified the example that comes with the Windows Message Queue library which you can download from NI. The primary reason for this is that it has a message loop. You can then tell Windows that you're going to accept drag and drop, and register for the WM_DROPFILES message. The DragQueryFile function will tell you how many files were in the drag, and you can then call it repeatedly to get each filename. Attached is the modified example (LV2009) to get you started. You will need to download the library separately from the NI site. All it does is display the dragged files to an array indicator. I also do not check to see where the drop actually occurred (i.e. to see if the user let go of the mouse on the tree control as opposed to somewhere else). If you need this I'll leave it to you to add it in. Windows Drag Drop Example.vi

Yes. In general, yes, it's been replaced by ActiveX. What are you trying to do?

Is it a .NET Invoke Node or an ActiveX Invoke node? If you show the Context Help window and place the wire tool on the wire that's connected to the reference input you should see the class name in the Context Help window. You should be able to determine then if you're dealing with an ActiveX class or a .NET class. If it's an ActiveX class then the DLL would most likely need to be in the C:\Windows\system32 folder. If it's a .NET class then the assembly would need to be in the GAC or in the same folder as the VI.

The likely reason why it's not working is that you're probably using 32-bit LabVIEW, but running on a 64-bit OS. Windows is not allowing you to call the osk.exe that it comes with since it's 64-bit. When you copied the osk.exe from Windows XP you copied the 32-bit version, and that's why it worked. If you were running LabVIEW 64-bit you wouldn't have an issue. You could try to use the Wow64DisableWow64FsRedirection function (http://msdn.microsof...v=vs.85%29.aspx) but I've never done this myself. Follow-up: Attached is a LV2009 VI that you can try. Note that the VI is configured to run in the UI thread. I have the 32-bit version of LV2009 and am running Win 7 64-bit and this VI launched the on-screen keyboard. EDIT: I made a wiring error on my previous upload. run osk.vi

Discussed at length at the NI forums: http://forums.ni.com/t5/LabVIEW/labview-memory/td-p/1547182 for those wishing to see what's already been said. In the future please indicate that you've already asked this question on another forum and have already received assistance.

All should know that this is a homework assignment, confirmed over at the NI forum by professor who actually gave out the assignment. He has asked that no further help be provided.

Yes. http://forums.ni.com/t5/LabVIEW/capacitor-charge/m-p/1333008 Confirmed by professor who actually gave out the assignment.

I don't quite understand your question. What do you mean by OpenGL being the "basis" of LabVIEW? In what way? Of course, remember that just because A implies B does not mean that B implies A.

Ton is correct. You have to set 'bar' and 'baz' to be 2D arrays because of the way LabVIEW populates arrays. LabVIEW has no concept of vectors, so rows and columns are the same with respect to 1D arrays. The alternative is to change your Matlab code to : bar=foo(:,1)'; (i.e., transpose it inside of the script). Then 'bar' and 'baz' can be 1D arrays.

cross-posted at the NI site

There is a difference since the object models are not the same, so they would program differently. It's quite similar to the Excel object model, though, so there are more similarities than differences. The Office Spreadsheet control is part of the Office Web Components. That control cannot read/write Excel workbooks (though you can export the contents of the spreadsheet control to an Excel file). Don't ask me why, that's just the way Microsoft designed it. What's it good for? Well, other than presenting a spreadsheet-like control on an application window, I have no idea. If you have to read/write Excel workbooks then you should either invest in the Report Generation Toolkit, or look over the examples that are available on this site as well as in the Excel thread over at the NI site. Please note: DO NOT POST QUESTIONS IN THE EXCEL THREAD. It is meant to be a repository of links only. As far as handling the changing of the version of office... no, there's no real good way to handle this. At least none that I have found, though others may have found a suitable solution. Ultimately I believe this is a limitation of ActiveX component "versioning".