Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Posts posted by crelf

  1. hmmm ... I use LV 7.1 / 8.0 on my laptop allmost every day (I have RT + PDA Module installed). Ok, it's not super fast, but it's ok ...

    My personal laptop is a 3GHz P4 with 1Gb of RAM - unfortunately my wife uses that one for checking her mail, whereas my work-provided one is a 1.3Ghz M with 512Mb of RAM - there's a HUUUUUUUUGGGGGGEEEEEE difference between them :(

  2. I often saw this error with my old computer. Since I got a faster computer from my admin this error disappeared.

    Yep - it's not a LabVIEW error per se, it's that you've tried to load a file from explorer (double clicked on a VI, project, etc), and Windows has started to launch LabVIEW to handle the file (you'll notice that your explorer window is still locked). Windows waits for LabVIEW to load to amek sure everything happened smoothly, but after a while it gives up with a couldn't-do-it message (LabVIEW continues to load in the background). That's why a faster PC "fixes" the problem - it just means that LabVIEW's got a better chance to load before Windows gives up on it. Another way to avoid seeing this error is launch LabVIEW first and then open your VI from the File menu.

    Of course, the other way to get around it is to make LabVIEW load faster, but that's another story ;)

  3. I have been using these tools for a few years, I would not say that knowing I have these tools makes me excited about documenting my code :rolleyes: . However, when forced to document these tools certainly make it less painfull.

    I can't say I know any software engineer that is ever excited about documenting code - we usually just wanna write more code :)

  4. <Shameless Commercial Plug> ;)

    There is such a tool available: The VISTA Documentation Manager and Documentation Generator - check out the links on the left side of the page. I have the luxury (and it is a luxury) of working for V I Engineering, so I get to use these tools (and more) internally for free, but even if I worked somewhere else, I would still certainly use these tools. From our website:

    VI Documentation Manager

    Quickly edits VI descriptions, controls and indicators. Improves productivity when documenting VI

  5. I installed LabVIEW 8 on a test PC yesterday as well as a bunch of stuff from the device drivers CDs. I openeed LabVIEW today, and there was no DAQmx palette :( I manually started the Device Drivers CD installer to try to install DAQmx 8, and it won't let me select it - apparently "This feature is incompatible with products already installed on this computer"

    post-181-1142538271.jpg?width=400

    Any ideas?

  6. ...so my question is should i go for a 24" widescreen or stick with my 2 19" lcd's ?

    Why not have them all ;) :

    +----------+ +-----------------+ +----------+

    |XXXXXXXXXX| |XXXXXXXXXXXXXXXXX| |XXXXXXXXXX|

    |XX.19".XXX| |XXXXXX.24".XXXXXX| |XX.19".XXX|

    |XXXXXXXXXX| |XXXXXXXXXXXXXXXXX| |XXXXXXXXXX|

    +----------+ +-----------------+ +----------+

  7. Is there a way to bypass this? like deactivate the "enter" shortcut while the user enters text in the control?

    Since you only want the enter key navigation disabled while the user is typing in the string control, use an event structe to detect when the use is typing in the control (key focus), and then set the key navigation of the button to nothing. Then, when the string control looses key focus (another event in your event structure), set the key navigation of the Boolean back to its original state.

×
×
  • Create New...

Important Information

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