Jump to content

Ton Plomp

Members
  • Posts

    1,991
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by Ton Plomp

  1. 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?

    I think you put the commas in the wrong place. It's on the hidden label of a visible constant. However the label has been moved away from the constant.

    Ton

  2. Yes flatten to string adds some bytes, (number of elements for instance and size of the total cluster, however you can turn the latter of).

    You might be looking for the Typecast function.

    However make sure you look at the section 'How LabVIEW stores data in memory' in the LabVIEW fundamentals help.

    Ton

  3. When trying to pass the char array of 260bytes, unflatten from string does not return the all 260 bytes.

    In the attached VI after unflatten from string reads only 4 bytes, does anyone know why? Is there any other method to allocate string size in LabVIEW to read 260 bytes of char?

    In C the array is char ProjectName[260];

    TIA.post-9853-0-89905300-1313185930_thumb.jp

    Most likely you use the wrong command, have a look at the 'String to [u8]' function, your function checks the embedded length (like a c-string pascal-string), but your string probably misses that info.

    Ton

  4. NI is now suggesting that reusable libraries should be located in the vi.lib. I was curious why the OpenG Toolkit 4.0 is installed to the user.lib.

    File and Folder Names for Integrating into LabVIEW

    The main reason is compatibility with older versions, since NI has openend the 'upgrade' functionalities they use internally (open up an old 6.x file VI and you'll see what I mean). So without breaking all the software allready utilizin OpenG we cannot move the files (we could deprecate the old locations though).

    And I have another perspective than NI, I've always assumed that everything inside vi.lib should be available on any LabVIEW install. This assumption alwasy told me to post add-ons into user.lib or instr.lib. So I'm in favour of the user.lib location.

    Ton

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

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

  7. Bitbucket looks great except for one thing.

    I can handle moving to mercurial, and I can even handle splitting my SVN repo into multiple by-project repos and simply organizing the repos into folders by customer. However, it looks like on bitbucket I have to place all of the repos at the same folder heirarchy level. That would force me to do something like [Customer_ProjectName] instead of [Customer]/[ProjectName]. Is there a way around this? I have too many projects to leave them all in a single folder.

    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

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

  9. 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 :nono:), where JGcode mentions that he got a CAR (236395 )

    Ton

    • Like 1
×
×
  • Create New...

Important Information

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