Home Community Idea Exchange LabVIEW Ideas

LabVIEW Idea Exchange

Community Browser
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post an idea
9 Kudos
sergiovelderrain

Allow user to override the icon editor with their own version

Status: In Development Submitted by Member on 10-14-2024 10:03 PM 5 Comment

The idea is to decouple the icon editor from LabVIEW so users can create their own. The intention is to make it easier for people to distribute their own icon editors by only having to place code on disk and modifying an ini token.

 

This would mean modifying lv_icon.vi so that it contains nothing but a launcher that would load the new icon editor from a path specified on a LabVIEW INI token.

 

There will be a default plugin that would hold the current icon editor, the path to the default icon editor would be a part of the LabVIEW ini file on LabVIEW install.

 

I created a working prototype that does that here.

 

I want to make sure this idea gets traction before going further with this.

21 Kudos
Petru_Tarabuta

The "Color" field of LvFontTypeDef.ctl should be replaced with a Color Box

Status: In Development Submitted by Active Participant on 06-07-2024 04:27 PM 7 Comment

Combined.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Benefits

  • Removes the need to use a separate Color Box Constant and Bundle By Name node when writing to VI server properties that take the LvFontTypeDef.ctl as an input.
  • More intuitive representation (a colour displayed as a visual colour rather than just a number).

Notes

  • The underlying data type of the Color Box is U32. Hopefully this means that this change would be "transparent" to the compiler. The change would affect only the visual appearance and  would improve the human interaction with this typedef cluster.
Labels:
View All (2)
81 Kudos
Mike_King

Wordwrap in all text controls/indicators (tables, listbox, trees, graph legends, etc)

Status: In Development Submitted by Member on 06-23-2011 11:18 PM 2 Comment

The fact that tables don't have wordwrap for individual columns still is pathetic.  Wordwrap is needed for all text components, columns in tables, cells, treeviews, listboxes, etc.  Plot legends as well should wrap and they don't.

 

Tables especially need this, alone with other suggest features for draggable columns, sortable A->Z AND Z->A, columns show/hide/filter, etc....

Labels: