Enhanced Icon Editor

Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.
Highlighted

Make Icon Editor API Public (include with LabVIEW)

Here is some of my feedback and ideas for a public Icon Editor API.

  1. Decoupling of the 2009 Enhanced Icon Editor UI Data Types from the API **THIS MUST BE DONE!**
    1. You cannot pass around the e.g. Layer Data clusters then move your code on disk (i.e. distribute it) as the Icon Editor code is not under a symbolic path
    2. Plus it looks messy passing around UI typedefs that are formatted for UI
  2. I don't think a LVOOP interface is required
  3. Wrapper methods of the Library refnums for Class Library refnums is needed so you don't have to upcast refnums
  4. Helper VIs for basic tasks e.g.
    1. Search for user layer by name (string)
    2. Match user layer
    3. Return all User Layer names
  5. Wrappers for access to Class's Control Icon with standard get and set functionality etc...
    1. A higher level abstraction so you don't have to have to be getting a refnum etc...
  6. String constants for default icons names VI Icon, NI_Library etc..
  7. VIs for color constants used by LabVIEW
    1. Native Class Color constants
  8. Create default icons
    1. Basic background: 32x32 black border, white fill
    2. Library banner: 12x32 <user> border + <user> fill etc...

I have also started this thread in the Idea Exchange forum for community support:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Icon-Editor-API/idi-p/1141247#A5811

Cheers

-JG

Certified LabVIEW Architect * LabVIEW Champion
0 Kudos
Message 1 of 1
(2,103 Views)
Reply
This is an open group. Sign in and click the "Join Group" button to become a group member and start posting.