I would like to know if there is some simple name for single information unit in status bar or toolbar, in a broad context (not connected to any concrete UI framework). Concrete use-case is that I'm creating some toolbar framework, and in general, I want to differentiate between commands (or command buttons to be more specific) and state-viewers (that's my name for it right now, but I'm not satisfied with that). Here is the very concrete example of what I'm talking about:
With red, I have marked commands, those are input for some document viewer. And with blue, I marked - what? While researching, I encountered a name indicator - it sounds too strange and too narrow to me - like it indicates something if it is on or off for example or something else that is simple like that. I would like to have wider definition, but also I'm open for accepting the indicator is a good name - I'm not native English speaker so maybe that's the problem also. For instance, to me, first indicator on the image, 1/3, which says that you are on the first page of three pages in total is too complicated to call it indicator.
EDIT: with a hope that this will not trigger "Too broad question", I would like to add that I was researching concrete toolbars in several applications a bit and it looks to me that general UX/UI thing is that in toolbar everything is clickable. Maybe my use-case here is XY problem - if that's the case, I would like to hear that of course. In that case, everything should be clickable, and it has static or dynamic display in itself?
EDIT 2: I have found a perfect real use case example I think! In Windows File Explorer, in status bar (or however it's called) there are commands on the right, and those status-viewers on the left, as you can see on the screenshot below. Those status-viewers are not clickable and really, I don't see any logical commands to connect to those so they become clickable.
1/3
to type in thepage number
I want to jump to and click on100%
and type in azoom level
number.1-3
thingy is read-only fully (is it confusing? Didn't think about it :/ ) and about100%
you are absolutely right, that's the exact implementation I have made, didn't want to add the complexity. BUT, for this case, I want to say that it iscommand
(you click it, it resets the zoom) and it is ALSOstate-viewer-or-what
(shows the current zoom level). It implements two things then (in my architecture, how I imagined it). So, still missing the name for that read-part.