@Yamaeda wrote:
If a function, or lack thereof, hinders the usage of the guidelines, i'd say it impedes development.
From the same document it also mentions that you should use icons as first choice, and text as secondary (which also leads to the question why a text icon isn't automatic but you get that default one).
As to your preferrences or "enough designed" isn't applicable to all companies guidelines.
/Y
None of this is helpful to bilko's issue. It doesn't answer the question being asked. It's off topic silliness. If we're being fair, "impede" changes in defintion if we're looking at short term or long term deveopment. In short term, guidelines impede development. If we're going to debate what "impede" means on a macro scale rather than focusing on bilko's issue, we're being silly.
The second idea brings up two thoughts. First, a default image versus a default text isn't really any different. The icon is built when the VI is created. "Untitled VI 1" is no less useless as a default image. There's no value in either decision being made so it likely wasn't discussed at any length. As far as text being suggested second, that relates to language differences. Everyone knows a thermometer has something to do with temp. But, not everyone reads English, Spanish, French, etc.
That's why the impact was asked. In this case, Bilko's impact is he likes to make smaller VIs when only a couple of inputs/outputs are required so he can stack these VIs closer together on his block diagram. The impact is he'll have to spread the VIs across more space on his block diagram.
Looking through the thread, it appears bilko has seen this on 2015. Jacobson has seen it on 2016. We've noticed it doesn't happen in 2014. If I remember right, 2015 was announced with quite a few optimizations. I wonder if one of the optimizations might have caused this behavior. I'd be curious to see if you built the PPL in 2014 and opened it in 2015 if the transparency was still there or not. This tells us if the problem exists in the creation of the PPL or if the problem is in the display from 2015+. Those two would be entirely different problems.
In either event, this has been replicated and can't be intended behavior. There should probably be a filed CAR.
