Multistate graphic object configuration example
-
I can't get the graphical views page "Multistate graphic" to display any graphic icons. I also could not find any example of the syntax in the documentation. Additionally, the Multistate graphic menu displays identical graphic icons, and only shows the custom icon if I mouseover the identical-looking icons. Can you please post a screenshot of the configuration pop-up of a working multistate graphic object? Where is the syntax documented for this?
On another note, can a single icon be displayed for a range of values? For instance:
icon <== multistate valuesright_arrow < == 45 ... 135 Down_arrow <== 136... 225 left_arrow <== 226...315 up_arrow <== 316..359, 0..44
Thanks.
-
Hi Pedro,
I'm not sure it ever was documented. And, since the graphical views aren't going to supplant the Angular dashboards, it's unlikely they will be documented farther.
The fields next to the icons (which also only displayed the linked image at mouseover of the same-icon) accept a comma delimited list of states for which to display the image and a default selection for unspecified states.
I verified this works in a 2.7 and 3.2 instance.
-
Thanks. That's what I tried that last week, and again today, with core 2.8.8. I tried it with different lists containing either six, nine, or 140 images. The point I'm using is a multistate point that I picked from the point pulldown list of the multistate graphic dialog. It contains 10 states, and was in state 3. Instead of rendering the point, the multistate graphic displays a grey block with a yellow triangle to the left. Mousing over the yellow triangle displays "The point for this component is missing or invalid."
It renders text a "simple point" on the same page, but the text is too long; I'm seeking to instead display small arrow icons (startup, accelerating, decelerating, constant speed, stopped).
If I don't select a default icon I get a non-intuitive error message, but selecting a default icon also did not help render the icons.
-
I suppose I could mimic the multistate icon behavior by adding a server side script to the graphical view, but then I won't have the benefit of displaying the point history table on mouseover, or of picking the icons from a menu. Do you have a work-around for the multistate graphical object error "The point for this component is missing or invalid?" If not, can you show me how to display the point history table or graph when I mouse over the icon rendered by a server-side script I would write to display the appropriate icon?
Thanks,
-
I have just tested Mango 2.8.8 with Graphical Views 1.7.0 with the fan, and once again it works.
Is it possible you're not hitting the save disk when changing the point? I am guessing it's not possible either the data source or the point really are disabled, but that would do it too. You are getting this result with the regular graphics sets too, or it's only occurring on graphic sets you're adding?
Can you share the JSON for the component you're trying?
-
- I'm definitely saving the point
- it's not possible either the data source or the point really are disabled, because the point is rendering normally as text via a "simple point" graphic renderer
- It is even not working for the fan multistate graphic.
The JSON for the component I am trying:
{ "type":"MULTISTATE_GRAPHIC", "updatePeriodType":"SECONDS", "dataPointXid":"DP_VFDWell1Status", "imageSet":"sstGraphics.Fan", "stateImageMappings":[ { "state":1, "imageIndex":0 }, { "state":2, "imageIndex":0 }, { "state":4, "imageIndex":1 }, { "state":5, "imageIndex":1 } ], "defaultImage":0, "displayText":true, "bkgdColorOverride":"", "displayControls":true, "nameOverride":"", "settableOverride":true, "updatePeriods":0, "x":319, "y":352 }
-
Worked fine for me. Have you tried using a clean graphical view to test it, in case there's some complication from another element elsewhere on the page? For instance, if you have an HTML component with an unbalanced tag earlier than it in the components list, etc.
-
Thanks, that's a good idea. I created and saved a new view. The point still renders as a grey Lego block with a yellow triangle to its left. A mouseover of the yellow triangle still displays "The point for this component is missing or invalid" as it did in my other view described above.
When I mouseover the grey block, I see the valid point rendered as text, displaying the expected Multistate text string, time stamp, set dialog, and table history.