Closed
Bug 989272
Opened 11 years ago
Closed 11 years ago
FPS and TTL monitors shouldn't depend on the Developer HUD being active.
Categories
(Firefox OS Graveyard :: Developer Tools, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: janx, Assigned: janx)
References
Details
Attachments
(1 file)
Currently, the FPS and TTL monitor widgets of the Developer HUD are different from the other widgets, because they were there before and use different code paths to work.
This means that they actually don't need the frame instrumentation added by the Developer HUD, and as of now they do not hide when the main Developer HUD toggle is switched off.
They should either be integrated with the rest of the widgets, or their settings should not be disabled when the Developer HUD is turned off (either they should stay active, or be moved out of the HUD menu entirely).
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → janx
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•11 years ago
|
||
Evelyn, could you please take a look? In the Developer HUD, I prevented the foreign FPS and TTL settings from being disabled. That way they can still be used even when the rest of the Developer HUD is disabled.
Attachment #8399293 -
Flags: review?(ehung)
Assignee | ||
Comment 2•11 years ago
|
||
Comment on attachment 8399293 [details] [review]
github pull request
Maybe Evelyn is busy, Vivien could you please have a look?
Attachment #8399293 -
Flags: review?(ehung) → review?(21)
Attachment #8399293 -
Flags: review?(21) → review+
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Component: Gaia::Settings → Developer Tools
You need to log in
before you can comment on or make changes to this bug.
Description
•