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
Small glitch that I noticed when playing with this plugin.
In Draw Full Names mode (which I use), the display custom nicknames only works for components that have identical Names and Nicknames.
Example below with Partition List whose nickname is Partition, but displayed as Partition List when GH is in draw full names mode.
I had a look at the code and I'm not sure if this is sufficient, but maybe the nickname should be also compared to the name of the component to determine is the filtering has to occur or not.
The text was updated successfully, but these errors were encountered:
Partition is the default nickname of Partition List, so it's not a "custom" or user-defined nickname, that's why it's not displayed when Display only custom nicknames is active. You can solve this by including a whitespace at the end or start, for example Partition .
Yes, I noticed that, but actually what I would like is that Partition List does NOT show on top of the component.
From what I understand the Draw Full Names mode overrides the nickname and puts the name instead, though the default Nickname is unchanged. What I'm suggesting is that Sunglasses should compare to the name and the nickname, and if either is a match, then the text display is disabled.
Hi Daniel,
Small glitch that I noticed when playing with this plugin.
In Draw Full Names mode (which I use), the display custom nicknames only works for components that have identical Names and Nicknames.
Example below with Partition List whose nickname is Partition, but displayed as Partition List when GH is in draw full names mode.
I had a look at the code and I'm not sure if this is sufficient, but maybe the nickname should be also compared to the name of the component to determine is the filtering has to occur or not.
The text was updated successfully, but these errors were encountered: