Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add INI token to ignore 'valid library icon' check when creating Text Icon #25

Open
dnattinger opened this issue Aug 6, 2024 · 2 comments
Labels
good first issue Good for newcomers

Comments

@dnattinger
Copy link

This feedback comes from Hunter Smith at JKI.

The Ctrl-Space, Ctrl-K shortcut in Quick Drop has become very popular among users wanting to assign text-based icons to their VIs.

This plugin currently has some pretty strict requirements on what it thinks is a "good" library banner that can support a VI having a text-based icon.

Some users (Hunter being the most vocal) would prefer to disable this requirement and be able to set a text-based icon on any library VI, regardless of what its banner looks like.

I've attached a screenshot of a "fix" for this issue to this Bug. It just involves updating this VI:

vi.lib\LabVIEW Icon API\Set Text Icon\Qualify Library Icon Core.vi

Check an INI token (NI.LV.TextIcon.SkipLibraryIconValidityCheck=True), and if it's present, ignore the library banner icon validity check.

icon bug fix

@JayKayAce
Copy link
Contributor

Hey @dnattinger
I have some questions to this.

  • Do we know the underlying reason for the modified VI to be changed? As far as I can see the debugging nodes should be be shown for the debugging.
  • Do we have a test vector that is setting Good Library Icon to True, or are all of these failing?

@dnattinger
Copy link
Author

@JayKayAce I don't quite understand your first question. My change is simply adding an INI token that advanced users like Hunter can employ to disable any library icon banner validity checking when assigning a text-based icon to a VI. I'm not changing the default behavior of anything with this change. And the debugging indicators on this VI have nothing to do with my change. The two red boxes show my only edits... adding the INI token read, and ORing it with the library icon banner validity check flag.

For your second question, I'm not aware of any existing test vectors that would be affected, as my change does not change default behavior, and is only activated with the (new) INI token that I'm proposing adding. For testing with the INI token, here's Hunter's canonical "no border" library icon banner that, without my change, doesn't allow Ctrl-K, but with my change (and the INI token), Ctrl-K works fine.
HUNTER_ICON

@svelderrainruiz svelderrainruiz self-assigned this Oct 9, 2024
@svelderrainruiz svelderrainruiz removed their assignment Oct 23, 2024
@svelderrainruiz svelderrainruiz added the good first issue Good for newcomers label Oct 23, 2024
@svelderrainruiz svelderrainruiz self-assigned this Oct 23, 2024
@svelderrainruiz svelderrainruiz removed their assignment Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants