04-08-2022 03:57 PM
Hello,
I am making an Icon template and this is not my first time. However, this is my first time using LV21. Is this a bug? Cuz I could have sworn I was always able to make this work in the previous versions of LabVIEW without issue. Someone please tell me where I am going wrong.
Step 1: Select Generic _blank template
Step 2: Delete VI Icon layer
Step 3: Edit however you want it to be
Step 4: Make sure the words still center vertically
Step 5: Save Template (make sure you delete the test words)
Step 6: Reload Templates and select your new template you just made
Step 7: Delete the generic user layer
Step 8: Type Words Describing VI
Step 9: Someone on NI Forums tell me where I messed up and why the words won't center vertically in the blue section. Thank you!
Solved! Go to Solution.
04-08-2022 08:24 PM
The issue is that in the latter part, it considered your whole image as such and could not identify any borders to center the text vertically.
04-08-2022 10:40 PM
@santo_13 wrote:
The issue is that in the latter part, it considered your whole image as such and could not identify any borders to center the text vertically.
I appreciate the response. I do. But... How then do I help it identify borders? What did I not do that needs doing?
04-08-2022 10:51 PM
Perhaps not the exact solution you are looking for but if you use classes to create your VIs, it does all this for you automatically. So if you made a class called COMPNY, you can edit the class icon then all the VIs made in that class will automatically have the COMPNY header already on the VI icon so all you have to do is add the VIs text under the header where it will be centered and look nice.
04-08-2022 10:52 PM
Tried the same on LV2019, and it seems to work just fine, a possible bug.
04-09-2022 01:26 AM
Wow, who would've thought that after at least a decade of leaving the icon editor alone, someone would change something and break it?
04-09-2022 06:51 AM
Ouch! I'm feeling guilty.
When LabVIEW 2015 was released, there was a "hidden feature" that I was privileged to participate in that provided access to what was released in LabVIEW 2016 as "Asynchronous Channel Wires", a feature I absolutely adored and continue to use heavily. In my mind, the two "developers" of this feature were Jeff Kodosky and Stephen Loftus-Mercer, the Fathers of LabVIEW and LVOOP, respectively.
I noticed that Stephen had created an Icon for one of his "Asychronous Loops Managed by Channel Wires" that looked like this:
I loved the idea of a "While Loop" Icon to identify parallel asynchronous loops, with Channel Wires bringing data in and out, but I wanted a little more "real-estate" inside the loop, so I made an Icon that had thinner lines (double instead of triple thick lines) that looked like this:
That worked fine. I'd already made a small Icon Library for myself that were similar to the VI Icon in the "Frameworks" folder that ships with LabVIEW, so I put my double-thick center-colored Icon in the Icon Template folder, and tried it out.
It was a complete disaster! When I tried to use it, and put text in the big "space in the middle", it tried to place it between the two lines making up the bottom edge of the Icon. [I'm not going to show you an ugly picture of this ...]. I remember trying to bring this to NI's attention (I know I button-holed several of the developers at NI-Week in 2016 or 2017), but nothing came of it. For myself, I "fixed" the problem by making my Icon look like this:
This is the Icon template that I used to make the Icon above -- if you look carefully, you will see that the Icon template has only a single line at the bottom. I deduced (by experimenting) that what the Icon Editor was doing was looking for horizontal lines in the Template. If it found three (or more) (like the Frameworks "VI" Icon), it put all of the Icon Text between the two lowest lines. I suggested that a better algorithm would be to look for the largest "space" between horizontal lines in the Template for the Icon Text.
But nothing happened. I hope this wasn't a "fix" for the issue I raised five years ago ...
Bob Schor
P.S. -- I'm still using my Icon set. They seem to work fine in LabVIEW 2021, but I haven't been using this version much except to respond on the Forums, as my colleagues are all running LabVIEW 2019, so I'm "being compatible" until we get a big Project out the door ...
Bob Schor
04-09-2022 12:40 PM - edited 04-09-2022 12:41 PM
@Bob_Schor wrote:
Ouch! I'm feeling guilty.
When LabVIEW 2015 was released, there was a "hidden feature" that I was privileged to participate in that provided access to what was released in LabVIEW 2016 as "Asynchronous Channel Wires", a feature I absolutely adored and continue to use heavily. In my mind, the two "developers" of this feature were Jeff Kodosky and Stephen Loftus-Mercer, the Fathers of LabVIEW and LVOOP, respectively.
I noticed that Stephen had created an Icon for one of his "Asychronous Loops Managed by Channel Wires" that looked like this:
I loved the idea of a "While Loop" Icon to identify parallel asynchronous loops, with Channel Wires bringing data in and out, but I wanted a little more "real-estate" inside the loop, so I made an Icon that had thinner lines (double instead of triple thick lines) that looked like this:
That worked fine. I'd already made a small Icon Library for myself that were similar to the VI Icon in the "Frameworks" folder that ships with LabVIEW, so I put my double-thick center-colored Icon in the Icon Template folder, and tried it out.
It was a complete disaster! When I tried to use it, and put text in the big "space in the middle", it tried to place it between the two lines making up the bottom edge of the Icon. [I'm not going to show you an ugly picture of this ...]. I remember trying to bring this to NI's attention (I know I button-holed several of the developers at NI-Week in 2016 or 2017), but nothing came of it. For myself, I "fixed" the problem by making my Icon look like this:
This is the Icon template that I used to make the Icon above -- if you look carefully, you will see that the Icon template has only a single line at the bottom. I deduced (by experimenting) that what the Icon Editor was doing was looking for horizontal lines in the Template. If it found three (or more) (like the Frameworks "VI" Icon), it put all of the Icon Text between the two lowest lines. I suggested that a better algorithm would be to look for the largest "space" between horizontal lines in the Template for the Icon Text.
But nothing happened. I hope this wasn't a "fix" for the issue I raised five years ago ...
Bob Schor
P.S. -- I'm still using my Icon set. They seem to work fine in LabVIEW 2021, but I haven't been using this version much except to respond on the Forums, as my colleagues are all running LabVIEW 2019, so I'm "being compatible" until we get a big Project out the door ...
Bob Schor
Is this the infamous "vertical line" issue? I forget exactly what it was - I haven't run into it lately because I haven't made an icon with a custom format in a while, but I seem to remember something about horizontal lines and strange vertical alignment.
Edit: nvm, I read your detailed description a couple of times and yes, this is exactly it.
04-10-2022 09:59 AM
Your mistake is in using words in icons to describe VIs. I consider that a hideous practice. (But it is better that what my cow-orkers do; which it not to edit the icons at all and just use the default.)
As for a common component in a group of VIs, I don't use templates, I put the VIs in a .lvlib and then make flag icon for the library. Here are a few of my lib flags:
Test Framework
Deployer
Wizard
Upconverter
Quick Apps
Universal Dialog Box
04-10-2022 11:36 AM
@paul_cardinale wrote:
Your mistake is in using words in icons to describe VIs. I consider that a hideous practice. (But it is better that what my cow-orkers do; which it not to edit the icons at all and just use the default.)
As for a common component in a group of VIs, I don't use templates, I put the VIs in a .lvlib and then make flag icon for the library. Here are a few of my lib flags:
Test Framework
Deployer
Wizard
Upconverter
Quick Apps
Universal Dialog Box
I'm willing to wager that your opinion is in the minority (even though it is sound advice). The fact that the icon text editor seems somehow broken now has the potential to affect a lot of people.