Ton Plomp

What JKI does with VIPM, is making an executable, zipping the executable up. Store that zip as a string inside a VI. Then use the installer VI to extract the zip-stream. (you notice I cut some corners in this process, and this is all just guesswork [citation needed]). Ton

I'm doing this for a source distribution and I try to do the following things: Clean the target path Relink MNU files set the version of classes and libraries make a Mercurial commit Ton

Hi Shaun, that makes sense, is that also valid for manual changes? I'll have a look at the documentation for that function tomorrow. Ton

I try to change the version of a library or class with the accompanying VI, and this returns an error 53. Can anyone reproduce this? Ton SetLibVersion.vi

Since LabVIEW (2011?) has pre and post build VIs we can have hooks into the build process. Has anyone managed to sent a message to the build dialog? I have digged a little in the resource\framework\providers\builds folder but nothing stands out (there is a AB_UI_reply_framework_message VI_, however that needs an unknown queue ref. Ton PS the builder says during the post build VI that it's saving the last VI

Man I'm late too to congratulate, but here it is 'Gefeliciteerd!'

You could look at teamplayer. However this is definitly off-topic. Ton

Well if you try to rebuild a physical console where you need to push multiple button at the same time you would need multitouch support. I seem to recall that on the NI forums was some info. Here is a case study, more info on that. (apparently without code)

I would use a timed loop with a timing of 5 minuts. You get pretty good timing, and options to have a constant phase and core utilization. Ton

You are correct, the capitalization instructs editors to remove the chunk upon graphical editing. By using non-compliant tools (like Microsft Paintbrush or TweakPNG) you can bypass this. So it's not a prevention of malicious snippets, but a precaution. NI could add info to the 'niVI' chunk that contains info about the containing file (like the complete or hashed IDAT chunk). The code capture tool does exactly that. It even inserts the tool name, and optionally some copyright info. Ton

Well off course you could precreate the folders as well in a parallel process. One advice is to use exactly 512 kilobytes as the file size (524288 bytes) since FAT systems like powers of 2. Your values is just over that size. Perhaps store the header in an index file per directory. Maybe adding some more folder layers get you to stabilize the increase. It looks like the lookup of folder names is biting you. What options do you use when creating a new file? Perhaps that an option 'replace or create' helps. Since it looks like the bookkeeping of FAT is limiting, you could open the file in previous loop (as well as the folders): Ton

John's idea is something I found out last week. It's quite good. A conditional probe in the master VI won't work, since the code isn't running. But you can create a conditional probe (before running) in your master VI with a breakpoint. Ton

Changing one massive SVN repo into several Mercurial repositories wasn't an issue. Loading them into Mercurial HGWeb or Rhodecode (my preferred private HG server) was easy as well. If you setup your configuration of TortoiseHG right then HG is as good as SVN. Ton

If you have Mercurial as a client to SVN you can have the positive from Mercurial (local repository database), with the support for your legace/obsolete/accepted SVN repository. I have never used this but Mercurial should be able to act as an SVN client. Ton

You can look here for a tool to convert set of subversion folders to Mercurial repositories. Ton

I would use an array of waveforms instead of a 2D array, using an array of waveforms you can have an empty waveform. Ton

Name: Mercurial Provider Submitter: Ton Plomp Submitted: 25 Feb 2012 Category: *Uncertified* LabVIEW Version: 2011 License Type: BSD (Most common) This toolkit allows you to directly communicate with you Mercurial repository, from within the LabVIEW project environment. This toolkit acts as an extension of the supplied LabVIEW SCC interface in LabVIEW professional. The toolkit allows you to commit, push, tag changesets. Has support for adding Issue tracking IDs. Click here to download this file

Do you make sure that both installers have the same component code (unique installer ID)? If I would make two of these installers I would make the full version one version higher than the base light installer. This makes sure that if the user installed base light but needed full can use the upgrade method to get the full with all the additional components. Base Ligth 1.2.3 Full 1.2.4 Greetings, Ton

Unfortunately that link isn't accessible by all (for instance ME). Ton