Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About lvman

  • Rank
    LAVA groupie

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks. I was hoping for a wizard that would magically do it for me:-) lol So overall, is it worth the effort to make the switch? Opinions?
  2. I'm tempted to make the switch from SVN to Hg. It seems it's easier to find a suitable online repository if your using Git or Hg (bitbucket). Ultimately I'm trying to make sure I always have access to my repository, even if I'm on another machine. I also like the idea of a separate local repo for each PC. A couple of concerns: 1- Disc space. Yes I realize hard drives are cheap, but I'm sold on solid state drives and they are not. 2- Work flow. I'm sure this is just a matter of retraining myself on how I use Hg (Joels guide is a good start). I currently using TortoiseSVN, and I would p
  3. Any chance you can post the example source code? I'm trying to wrap my head around these concepts and an example would help. Thanks for the great info.
  4. I did not run any benchmarks, but there is a noticeable difference. Here are a few tasks that seem significantly faster: 1- Loading LabVIEW or MAX 2- Loading projects that have several hundred vi's 3- Opening MS Outlook. Doing any searches for email are almost instant 4- Opening Itunes 5- Dialogs seem to pop up faster 6- Windows start up and shutdown is faster. Windows becomes responsive almost instantly after you see the desktop. Something else to keep in mind, some laptops have removable bays that are typically used for a cd/dvd drive. What I did is replaced it with a SATA drive b
  5. I just upgraded my 2.5 year old laptop to a solid state drive and it made a big difference in terms of responsiveness of the pc. Just something to keep in mind.
  6. Thanks for the replies. You were initially correct in that I could use the "to more specific class" vi. I was getting the error because I passed in a "unit" object that was not defined! Basically I had a "serial unit" input into my Add/Edit gui and I tried casting a "unit" to a "serial unit", but my "unit" object was not defined. I needed to make sure it was an actual "serial" unit, or create a "serial unit" object and skip the cast function. Hope that makes sense.
  7. The problem is that my "Add/Edit Unit" GUI is different for each Unit. I have coded an "Add/Edit Serial" GUI that expects a "serial unit" input. If I try to cast my "unit" object into a "serial unit" before passing it into the vi, I get the error mentioned above. If I pass a "unit" object into it, it does not compile. If I make the input terminal a "Unit" object type, I cannot access my "serial unit" specific information. I suppose I could make "Add/Edit Unit GUI" as a method for "Unit" class, and this will get over written for each child class of "Unit" ("serial unit"). Then I can pas
  8. Thanks for the reply. I took a look at that presentation but I'm not sure it solves my problem. It looks like the factory pattern has a vi which determines which sub-class to create an object from. So in my case I can select "serial unit" and I can get a "serial unit" object out. The problem is when they want to edit the "serial unit" object. Since I currently store all my units as "unit" objects (config class), when I try to get a unit that I know is a "serial unit", I get the error mentioned above. I think I'm coming to understand why this does not work. Say I create a new "serial uni
  9. I've been trying to dig into LVOOP but I've run into some issues. This is my first attempt at OO design and implementation so I'm thinking I would get some advice before I pull all my hair out. My objective is to build an application that could acquire data from multiple source. This application will have a means to configure each data source and load/save configurations to file. My first crack at this from an OO approach: 1- Create class called "unit". This represents a data source. Class data is "name" and "description" 2- Create class called "serial unit". This inherits from "unit"
  • Create New...

Important Information

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