You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, the workflow is to open the VI/Library/Class etc and then open the Icon editor from there. I propose to add support fort the reverse process, where you can load a VI or multiple VIs into the icon editor.
Having the Icon editor support being started as a separate program capable of opening VIs and editing their icons would make it easier to focus on the VI Icons, when designing toolkits and making pallets.
The supported files should be all the standard LabVIEW files with Icons: (non-exhaustive list)
VIs
Controls
Classes
Libraries
...
The text was updated successfully, but these errors were encountered:
Hey @JayKayAce, i have a working prototype that decouples the icon editor from LabVIEW into a plugin on my fork.
It would be simple to create a VI that can use the same plugin. We could collaborate on this idea if you want.
Historically, the workflow is to open the VI/Library/Class etc and then open the Icon editor from there. I propose to add support fort the reverse process, where you can load a VI or multiple VIs into the icon editor.
Having the Icon editor support being started as a separate program capable of opening VIs and editing their icons would make it easier to focus on the VI Icons, when designing toolkits and making pallets.
The supported files should be all the standard LabVIEW files with Icons: (non-exhaustive list)
The text was updated successfully, but these errors were encountered: