Currently working on a project, using Ignition 8.1.25.
I've noticed sometimes my icon objects have a stroke, and other times they don't.
As an example, I've created view with an SVG valve graphic and I am using it as a template/symbol on other pages. I use an icon on the template to indicate a failure/alarm (just bind the visibility tag to an alarm status). Sometimes the icon has a stroke on template and sometimes it doesn't. It's the exact same template, just a different parameter for the valve tag. The icon object doesn't even have an option for a stroke, and if you try and add one it doesn't seem to work. The stroke seems to occur randomly at times, and then without even making changes (that I can recall) it will go away again at some point.
I've seen this happen in the Designer, Firefox, Chrome, and Perspective Workstation.
Anyone seen this before or have any thoughts. I tried doing a search through the forums and wasn't seeing anyone else having this issue.
Does the icon have any style / style classes applied to it, other than it's color?
Do you have any style / style classes applied at a higher level in the view holding the icon?
To get rid of the stroke on only the Icon you can change the icons style to:
{
"stroke": "none"
}
If you always want a stroke on the icon try:
{
"stroke": "black !important",
"strokeWidth": "1px !important"
}
You can also always open your browser's dev tools and see the live style actually being applied, and usually where it's coming from; e.g. a style class will have a .psc-
prefix on the selector.
@PGriffith I've actually used the browsers dev tools in the past, but it's been a chaotic couple of weeks, and it just didn't occur to me.
Using the dev tools I was able to track it down to a style being applied on a parent div. In this instance specifically a stroke got applied to a couple of the view's dropped on the screen and a stroke was being applied to the entire view. It's not clear to me why/how a stroke was applied those views, but hopefully it was just a random mistake, and this appears to be resolved for the time being. Appreciate the help.
2 Likes