Jump to content
  • 0

How do I get my own custom controls (or theme) to appear in the JKI Design Palette?


Jim Kring
 Share

Question

1 answer to this question

Recommended Posts

  • 0

Adding your Own Themes and Controls

Note: Adding your own themes and controls is not officially supported, since we may be making improvements to how this works, but we wanted to tell you how to do it, so that you can make the most of the JKI Design Palette in your LabVIEW work. We hope you like it.

Installing Theme Files

Themes are stored beneath LabVIEW, in the following location:

  • <LabVIEW>\resource\JKI\Design Palette\Themes

To create your own theme, for example for your company named “Acme Corp”, just create a new folder such as the following:

  • <LabVIEW>\resource\JKI\Design Palette\Themes\Acme Corp

Inside that folder, place your controls as *.ctl (Custom Control) files, such as the following:

  • File Path Control (Acme Corp).ctl

  • Listbox (Acme Corp).ctl

Have fun!  And, if you’ve created some controls that you’d like to share with others (especially the built-in themes like Classic, System, NXG, etc.), please post them to the JKI Design Palette Community Discussion Forum.

File Naming and Search Keywords

The words in the file name are used as keywords for finding search results when typing into the search box of the JKI SDP -- so, you want to name the file with keywords that users will typically use when looking for your control.  So, you’ll probably want to include the following words in the filename:

  • The type of control (e.g. “Button”, “LED”, “Chart”, “Date Timestamp” etc.)

  • The Theme Name (e.g. “Acme Corp”, “Classic”, “System”) since people may want to type the theme name into the search box, rather than using the Theme selector/filter drop-down list.

  • “Control” or “Indicator” if your theme has both control and indicator versions of the control file

Regular Custom Control vs Type Definition

If you make your *.ctl file a “Type Def.” (type definition), then the dropped control will link to the type definition *.ctl file and will be updated accordingly, if you change the type definition file. This may or may not be desirable for your users. If you don’t want the dropped instances linked to the type definition file, then be sure your *.ctl is a regular type definition.

image.png

Link to comment
Share on other sites

Join the conversation

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

Guest
Answer this question...

×   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.

Loading...
 Share

×
×
  • Create New...

Important Information

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