Jump to content

Tobi_J

Members
  • Posts

    6
  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 8.0
  • Since
    2009

Tobi_J's Achievements

Newbie

Newbie (1/14)

0

Reputation

1

Community Answers

  1. wow, now i feel a bit emarassed, since i asked the same question already two years ago well... here the link for the ones interested: https://lavag.org/topic/16471-setting-the-tabbing-order-of-front-panel-objects/#entry100730
  2. Hi All, i wanted to set the tabbing order and followed the advice on http://zone.ni.com/refer1ence/en-XX/help/371361G-01/lvhowto/changingtheorderoffpanelob/ . However I don’t get to change the tabbing order of the controls on tab control, see the picture. Can you tell me how to do it? Thank you Tobi
  3. Hi Guys I wanted to set the tabbing order of my front panel and found it under Edit-> Set Tabbing Order. Since I use a Tab Control with two pages that blanks half the controls, Labview will not store my tabbing order settings. Does anyone know how to deal with this issue? Thanks Tobi
  4. Thank you guys very much, the hint with the local variables helped me, since i am using labview 8.0
  5. Dear Labview Users, I want to build a VI that can read and write the settings for the controls. The VI should be able to write certain config-settings and be able to read it in the same control. I found Labview examples (Read Configuration Settings File.vi and Write Configuration Settings File.vi both attached below) and the writing of the control-doubles via the Write Key.vi works just fine. The problem arises when the config-settings should be read, since a “control” in Labview cannot be used as an “indicator”. Basically I want to have both VIs (Read Configuration Settings File.vi and Write Configuration Settings File.vi) in one VI and that the indicator/control on the front panel is the same. Thanks for your help Tobi Read Configuration Settings File.vi Write Configuration Settings File.vi
×
×
  • Create New...

Important Information

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