You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we maintain 2 different string sources for tooltips:
src/skin/tooltips.cpp
src/controllers/controlpickermenu.cpp
Currently, we have the following quirks
Same control different content in the tooltip
Same control different spellings in the tooltip
Control missing tooltip in one or another source
This is unnecessary work for code and translation contributors as well.
We have manifests for effects including a description, what about something similar in a centralized fashion for control descriptions?
The text was updated successfully, but these errors were encountered:
jus, unless you are committing to take care of this for 2.2, I don't think it is helpful to assign bugs to a milestone. This is how milestones accumulate a lot of noise, which makes it hard to tell what actually needs to get done to make a release happen.
Reported by: esbrandt
Date: 2014-12-18T06:37:41Z
Status: Confirmed
Importance: Medium
Launchpad Issue: lp1403748
Tags: polish, usability
Currently, we maintain 2 different string sources for tooltips:
Currently, we have the following quirks
This is unnecessary work for code and translation contributors as well.
We have manifests for effects including a description, what about something similar in a centralized fashion for control descriptions?
The text was updated successfully, but these errors were encountered: