[1501] Rephrase the tooltip setting texts
tracked
naqtn
Build 1501 introduced "Interactive Object Tooltips" settings. Although the actual behavior of each setting is quite simple, it is hard to understand that by reading the option names and the tooltips. Also, there are many inappropriate or unbalanced expressions around that.
They should be rephrased.
The labels, option names, and tooltips (Build 1501)
(The numbers are the identifiers of the strings on Crowdin for the localization)
- 109034 `UI Tooltips`
- Tooltip: 13695 `Display tooltips under menus and objects.`
- 109052 `Interactive Object Tooltips`
- Tooltip: 109050 `Change how tooltips on interactive objects in the world appear.`
- Options:
- 109036 `Highlight Only`
- Tooltip: 109038 `Only show the outline for interactive objects.`
- 109040 `Tether`
- Tooltip: 109042 `Show the tether line for interactive objects.`
- 109044 `Tooltip`
- Tooltip: 109046 `Show the tooltip text and tether for interactive objects.`
- 34148 `Controller`
- Tooltip: 109048 `Show the controller, tooltip and tether for interactive objects.`
The actual behavior of interactive object display
Highlight Only: outline
Tether: outline + tether
Tooltip: outline + tether + text
Controller: outline + tether + text + controller
The problematic points
- The and objectspart of 13695 must be removed. As the spec has been changed, you must rephrase it.
- The part for interactive objectsof each tooltip is not needed. It is expressed by the label 109052. It is somewhat more confusing to users than helping by letting them recognize more long sentences.
- With eliminating for interactive objects, the tooltips would be the following. They don't match with the actual behavior, and users can't understand quickly because of random omission of "outline", "line", and "text".
- `Only show the outline.`
- `Show the tether line.`
- `Show the tooltip text and tether.`
- `Show the controller, tooltip and tether.`
- 109048 doesn't explain what the controller is. Rephrasing it with "controller 3D model" might be helpful.
- It is hard to imagine or understand the actual behavior by reading the names of the option "Highlight Only / Tether / Tooltip / Controller". It is actually "Highlight Only / and adding Tether / and adding Tooltip / and adding Controller". "Full / Medium / Less / Minimum" might be better.
- 109052 would be better if it is rephrased to Interactive Object Appearancebecause it is doubtful whether "outline highlight" and "tether" are tooltips.
- (Depending on the previous one,) 109034 would be better if it is rephrased to UI Menu Tooltips. Because, "Interactive Object" is also a kind of user interface of the world. So, there is a wrong inclusion relation, and it would confuse users.
The issues of patch note
> If you've never touched this setting before, it will be set by default to "Controller"
This "it" is unclear. Readers would be confused because it is not "this setting".
> Aside from the existing "Controller Model + Text" and "Only Blue Tether and Outline", there's now also a mode that hides the controller but leaves the text, and one that only shows the blue outline for maximum immersion.
As a whole, this sentence presents that two new options are added to the existing two. However, the reader would be confused because many unfamiliar words are put into one sentence. Dividing into several sentences would be helpful.
And the option names don't match "Controller Model + Text" and "Only Blue Tether and Outline". That is another source of confusion.
Also, there is the meaningless, unbalanced use of "+" and "and".
Log In
StormRel
tracked
ᴋᴀᴡᴀ
I fully agree!
And why not just add toggle for
each
visual separately
, like:- "Show tether line towards interactive objects"
- "Show text tooltip on interactive objects"
- "Show controller model on interactive objects"
(mentioning in the tooltip that outlines are always on) Yea, it will be 3 lines instead of one, but this would be much simpler and easier to understand for end users.
I know from other cannies that UI designers try to minimize number of settings to not scare users with panels like on airplanes. But this 👆 example proves that combining some settings into one switch just makes things even worse. End users really need to do research like naqtn did to get that.
Also, I would simplify "interactive objects" to just "interactives". Yea, It's informal, but completely understandable to most users and justified simplification to not choke end users with too formal terms.