Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/08/2009 in all areas

  1. Meet Lilah Kring, the newest member of the Kring family: Born Monday, 10/5/2009, at 11:30 PM GMT -7 I can't guarantee she'll use LabVIEW, but I'll do my best [insert object-oriented programming puns, here]
    2 points
  2. For inserting an object's UI into a subpanel, I have used the reverse approach successfully - I have a DD VI that accepts a reference to a subpanel called something like "Insert UI", then its up to the individual class to decide what VI gets inserted and give the opportunity for the class to do any housekeeping before actually displaying its UI to a user. Here's a pic:
    2 points
  3. View File UI Tools UI Tools v1.4.0 Copyright © 2009-2016, François Normandin All rights reserved. Author:François Normandin Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 2012 Dependencies: OpenG Application Control Library >= 4.1.0.7 OpenG Array Library >= 4.1.1.14 OpenG File Library >= 4.0.1.22 OpenG LabVIEW Data Library >= 4.2.0.21 OpenG String Library >= 4.1.0.12 LAVA Palette >= 1.0.0.1 Description: This package contains tools for designing user interfaces. A first palette helps create special effects using transparency of front panel. Using them allows to quickly create fade-ins or outs using linear or exponential variation of the intensity. A second palette contains VIs to calculate the position of GObjects for many purposes like alignment, snap, mouse follow, etc. A third palette contains VIs to create dialog boxes based on class instances. "Simple Error Dialog" and "Simple Selection List" are featured with or without backrground blackening effect. A fourth palette includes some VIs to move objects programmatically on the front panel, using a basic deceleration algorithm to provide an impression of a smooth movement. The packaged VIs are all namespaced using a suffix “__lava_lib_ui_tools” which should not conflict with any of your own code. Includes: Front Panel Transparency (Fade In & Fade Out) Utilities (Alignment, Snap) Dialog (OOP based, extensible) Engine (Beta) for object movement Instructions: This package is distributed on the LabVIEW Tools Network (version 1.3) and updates are on LAVA (1.4). It can be installed directly in the addon folder of any LabVIEW version from 2012 to now. The addon installs automatically under the LAVA palette of the addon submenu. License: Distributed under the BSD license. Support: If you have any problems with this code or want to suggest features, please go to www.lavag.org and navigate to the discussion page. Submitter Francois Normandin Submitted 09/21/2009 Category LabVIEW Tools Network Certified LabVIEW Version
    1 point
  4. Congrats. I could paraphrase my recent joke from the NI forums Class Baby{void sleep(int seconds)Ewww FillNappie(fillKind fillKind)HappyPapa MakeAFace()} But I think that asking you to remove her hat to see whether the inheritance mechanism works correctly is a better one.
    1 point
  5. Congratulations, Jim. I'm sure she'll be wiring in no time. You know peek-a-boo is just a lesson in object persistence.
    1 point
  6. Increment IP Address 80.vi (LV 8.0)
    1 point
  7. version 1.0.11 released. I've added an Outlook-style sidebar based on radio buttons. This allows to take advantage of the Enum typedef. Disconnect the typedef and customize with your own buttons, change button order or even style. http://content.scree...-10-08_1129.swf
    1 point
  8. Hi I would of cause not even consider by value unless I really needed the highest speed. This is a reference solution: Farm.zip As an initial design I wouldn’t add the complexity of the List object, and have the array of animals direct in the Farm attribute. Cheers, Mikael
    1 point
  9. Indeed, to preserve dataflow, this is exactly what you have to do. If you have many classes, let's say "pigs", "cows" and "goats", then you should add a layer "animal" from which they all inherit. Your Farm class would contain a list of Animals and you can have only one "Write/Read infants" for the Animal class, provided that all animals have the same "bornalive/stillborn/mummified" properties for the infant counts. If you need to override with a different Read/Write for a particular animal, then you can. But it should let you have only one UpdateObject for the whole animals hierarchy.
    1 point
×
×
  • Create New...

Important Information

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