Ton Plomp

One thing you need to take care of is that TDMS properties cannot contain cluster or arrays. So if your cluster contains a sub-cluster or Array you'll need to worry about that. You can get inspiration from the the OpenG INI-tools to see how you can detect (and expand) those data-types. Especially with the possibility of recursive VIs it's quite easy to build such a generic tool. Ton

Fatal error: Out of memory (allocated 10747904) (tried to allocate 30720 bytes) in /home/lavagorg/public_html/admin/applications/forums/sources/classes/forums/class_forums.php on line 725 Fatal error: Class declarations may not be nested in /home/lavagorg/public_html/admin/sources/classes/itemmarking/classItemMarking.php on line 25

You're correct that you should put every project in their own repository. You can add quite a lot repositories to Bitbucket that aren't aware of each other. Mercurial has the option to have subrepos (per customer) I haven't howerver looked at those features. Ton

Besides online hosting (microsft has a host that supports Mercurial), there are several packages that supports private hosting on your own server, I'm getting quite fond of Rhodecode. Some of the online hosting services also offer other integrations, bug-tracking, publising build packages, wiki's, twitter/facebook announcements. For public hosting I use Bitbucket as the public repo for my private code Ton

Regarding the SCC delay, it is there, LabVIEW is requesting the status of each VI individually, and then sending a burst with all the VIs at once, if you have a slow/bad design of SCC interactions this is noticeable. Ton

Unfortunatly NI is looking at XControls as second class citizens. I filed a bug because LabVIEW is ignoring .xctl files in user.lib during auto-indexing of the palettes, but this was rejected. My current work is: -Move the XControl and all of the sub-vis into an hidden directory (starting with an underscore '_') -Create a palette file next to the hidden directory that contains the actual XControl, and any other controls/VIs I want to expose Move those to files/folders into user.lib I posted anIdea on the Idea Exchange about this behaviour, that definitly needs more votes (currently 9 ), where JGcode mentions that he got a CAR (236395 ) Ton

I am not familiar with SAP, but what kind of error do you receive? Ton

What you are implying is a graphical IDE for C, .NET or ........? I don't think there's a market that is economically valid for NI, the LabVIEW language is pretty good covered by patents, while other languages are more open. And in fact LabVIEW code is converted to text, Machine Code to be more precise. Ton

What is the specific reason you want to disconnect from the lvlib? The lvlib can be included with the LLB like any other LabVIEW file. However you should disconnect each VI from the owning lvlib, there might be a VI-server method for this, but I am not sure. Ton

On the LabVIEW beta forum somebody said that he was able to move a VI into a library, and he had no issus with VIs finding the (renamed) VI. The only downside is that calling VIs are 'dirty'. So I see no issues with this move anymore. Ton

I would use the following construct to determine the decimal sign of my PC: Ton

Hello Justin, that sounds really cool. I am looking into AES right now and the different steps are puzzling (if you only use the NIST standards). I have a HMAC/SHA libarary online (bitbucket source) and would love to add an AES into that package. Ton

Search and replace code segments (snippets)

Perhaps you are maxing out on handles. Windows can only give a dedicated number of handles for each application (link, I have not studied it). But it sound to me that even if you close all references, you will get errors eventually, so be very careful in case of opening handles in a loop. Perhaps you can create your own handler of handles. Ton

Fatal error: Out of memory (allocated 17039360) (tried to allocate 82 bytes) in /home/lavagorg/public_html/admin/applications/forums/extensions/search/format.php on line 474 Ton

[plug] The code capture tool supports Imgur as an upload target. [/plug] Neither is Opera working.I think that NI puts someone on this issue it can be fixed rather fast. I assume that you need to look at some different drag and drop info. I have submitted an idea at the NI LabVIEW Idea exchange on this subject. Would it be possible to have simple POST methods for the VI snippets site? Ton

Apart from saving snippets for use in the NI/LAVA forums I use them as a documenting tool on our internal WIKI on bugs, code constructs etc. I think I create snippets on a daily basis, for this the NI tool is absolutely not adequate, hence I use the Code Capture Tool. This provide the followin advantages: -Adding a configurable header to add some info on the VI and LabVIEW version -Adding notes and description (arrows, rectangles) for high-lighting -Saving them in a configurable location -Keep property notes connected -Include the front panel image as well. -Copy the file path to the clipboard -For computers directly connected to the internet it can save the image on Imgur Ton (co-author of the Code Capture Tool)