Jump to content

Ton Plomp

Members
  • Posts

    1,991
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Ton Plomp

  1. A little later.......

    I can get error 53 if any of the Major, Minor, Fix numbers are zero. But works perfectly if they are all non-zero

    ...

    You cannot decrement the version of a user class. So if you are trying to set it to a lesser value, it fails with 53.

    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

  2. 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

  3. Can MS Mouse Mischief or Multitouch allow me to use a single very strong computer with multiple screens to allow several users simultaneous work over the computer?

    For example, instead of buying 4 computers, one for the dad, one for mom, one for the son and one for the daughter, will it allow me to buy a single strong computer with extended desktop over 4 screens that will allow each member to manipulate a different program simultaneously?

    It is probably just my longing to the MainFrame days but I really wish this was the case instead of having to support and maintain so many pcs even at home when I come back from work.

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

    Ton

  4. On this LabVIEW Wiki page, the following text can be found:

    Quote

    The capitalization of this chunkname makes sure the code is removed if someone alters the image, thus preventing the creation of malicious snippets.

    I aim to show that this is not true. While most programs will remove the code if the image is altered, it's relatively simple to use a free tool called TweakPNG to put any VI into any PNG image.

    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).

    For instance, you may want to add some extra text to a VI Snippet explaining something, but don't want it to appear when it's dragged into LabVIEW.

    The code capture tool does exactly that. It even inserts the tool name, and optionally some copyright info.

    Ton

    • Like 1
  5. 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):

    post-2399-0-14424700-1341566038_thumb.pn

    Ton

  6. 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

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.