Jump to content

Text file in PropertyPages folder


Recommended Posts

Anyone figure out how these txt files (C:\Program Files (x86)\National Instruments\LabVIEW 201x\resource\PropertyPages) work?

 

Looks like there are some link between the content of these files and the tabs shown on the control properties panel.

 

What I really want is shown additional tabs for the decorations.

 

 

Link to comment

Uh, what additional tabs would you want it to show?  It's unlikely to work anyway since these pages are probably very tightly coupled to the control, or front panel object, and even if you were able to say take a tab shown for a string control, and have it show up in the decoration, I doubt things would work right.  What are you wanting to add?  It might be a good idea to post on the Idea Exchange where you can suggest future features of LabVIEW.

 

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas

Link to comment

I want show the appearance tab, where you set the object width & height.

i.e. "C:\Program Files (x86)\National Instruments\LabVIEW 201x\resource\PropertyPages\Pages\PropPage_Appearance.vi"

 

Don't want to post on the Idea Exchange anymore.  Waiting forever!

I want to do it myself.

Link to comment

I remember seeing something around about 2010 about this.

 

If memory serves me correctly forum member jgcode did some digging into this and had a usable example, but there were some things preventing a complete solution.

 

I also think there is a NI community page dedicated to this, but cannot find it either.

 

Sorry!

Link to comment
  • 5 months later...

I've figured it out.

Each .txt file is for a GObject, such as path ctrl, or while loop structure, ...

The filename is the Class ID of the GObject. e.g. 11.txt is for the path ctrl.

Inside the file, each line defines a tab on the GObject properties dialog panel.

The first column is the tab id; the second column is the VI to be used on the tab.

Multiple VIs can be displayed on the same tab.

Now you can make your own VIs to show up on the dialog panel.

 

Edited by Zou
  • Like 1
Link to comment
  • 2 weeks later...

You don't need the queue-it is just adding complication for no benefit. You are taking the event (which is automatically named by the control label) then grabbing the control name and sending it via a queue to a case structure that has the same names as the events. Your code will be lot simpler and easier to read if you just use the event structure with a frame for each control.

Link to comment
5 hours ago, ShaunR said:

Your code will be lot simpler and easier to read if you just use the event structure with a frame for each control.

Yeah but if it's password-ed no one will see it right?  Certainly having a non passworded version would benefit the community more, nonetheless, thank you Zou.

Link to comment
22 minutes ago, hooovahh said:

Yeah but if it's password-ed no one will see it right?  Certainly having a non passworded version would benefit the community more, nonetheless, thank you Zou.

Ah yes. Forget everything I said because I obviously opened the wrong VI to be able to see the diagram. Thanks for pulling me up on it.

Link to comment

It's just a very, very simply, textbook VI.

You are all experienced programmers.

You can create your own VI to show up in the property dialog.

The queue is there to get message from LabVIEW, must have it, and don't destroy the queue when exit.

I'll create a template for those who can't figure out how to create a plugin VI.

 

Link to comment
6 minutes ago, Zou said:

You are all experienced programmers.

I am, but I can't speak for others who stumble on this thread years later, and actually Mike had an interesting quote regarding locked VIs.  Again thank you for any contribution you share.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

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