LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Hinweisstreifen entfernen?

hallo,
 
Ich habe in einem LV Programm von mir Hinweistreifen eingefügt, mit denen der Nutzer nähere Infos einblenden lassen kann. Im späteren Verlauf der Programmierung stellte ich dann fest, daß diese Hinweisstreifen nicht an allen Stellen, an denen ich sie bis dorthin einbaute, nötig waren. Somit entwerfte ich diese Eigenschaftsknoten, mit der Hoffnung, dass auch die Hinweisstreifen nichtmehr eingeblendet werden. Leider werden sie trots dieser Entfernung weiterhin angezeigt. Wie werd ich diese H-Streifen denn jetzt wieder los, ohne gleich ein neues Programm schreiben zu müssen?
0 Kudos
Message 1 of 9
(3,379 Views)
Neue Feststellung: Wenn ich eine leere Stringkonstante vor den Eigenschaftsknoten hänge, taucht er  wie gewollt nicht mehr auf. Somit kann ich das Problem mal soweit beheben. Aber sobald ich den Eigenschaftsknoten komplet entferne, taucht der alte String wieder auf, der von der leeren Konstante noch aktiv war. Das ist doch sicher nicht so gewollt von LV oder?
 
0 Kudos
Message 2 of 9
(3,363 Views)
Hallo Simon,

was sind Hinweisstreifen? Ich habe bisher nur mit engl. LV gearbeitet...

Kannst du mal ein Beispiel-VI anhängen?

(Can you post this in English too? You can expect more answers...)
What are 'Hinweisstreifen'? In the english LV versions there is nothing similar...
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 9
(3,361 Views)
I dont have the english word for "hinweisstreifen" too, but i can send you a VI, how you wanted it.  How sould i explain this now on the best way...hmmm. You have to know my english is horrible  Smiley Tongue
 
If you move the mouse over the button, you get shown a litte text, where you can see "bla bla"
When I remove the Item with the string on it, also dont know the english name for it, then the text should disappear. But it dont goes away! I tesed a bit, and found out, if you make a empty var. insted of the string "bla bla" it does not appear. It works so, but why can i not only remove thr Item, and the string goes also. Anyway, I have a anwser now...but what do you think about it?
0 Kudos
Message 4 of 9
(3,360 Views)
Hello Simon,

without having the possibility to look into your vi, I can guess this:
You are talking about the 'tips' from the 'description and tips' properties of controls.
If you set this property once, LabView remembers this value for the control. So if you remove the property node from your block diagram, Labview still has the tip text and shows it to the user. You have to clear the tip text to avoid their appearance!
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 9
(3,350 Views)
k thx
thats works...but why does LV save those infos? for what?
0 Kudos
Message 6 of 9
(3,348 Views)
Hello Simon,

that's the way it works:
once you set/configure those properties, LV remembers them until you change them again. This also applies to other properties, like the range/increment values of numrical controls. You define the properties of the control and LabView saves them with the control. And it's not important if you set them while editing or programmatically with property nodes...
Or do you want to set the mechanical behaviour of your boolean switch each time the vi runs? (right-click on control -> properties)

Message Edited by GerdW on 06-14-2006 05:16 PM

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 9
(3,342 Views)


@SimonKob wrote:
k thx
thats works...but why does LV save those infos? for what?


Before property nodes where there you only could use static "Description" text. (Tip Strips weren't there then).
And most users still develop their front panel with static descriptions and tip strips. This makes sense as this information seldom changes during runtime. In fact there are only two reason I could think of to change this information and that is because you use the same control for two different operations depending on the context of your application or you are developing your own multilanguage user interface.

Otherwise the information put there at development time will almost always stay there for all the time.

Rolf Kalbermatter
Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 8 of 9
(3,338 Views)
k, thanks for that. In deed we use a languageselection for our program.
0 Kudos
Message 9 of 9
(3,323 Views)