Closed Bug 907243 Opened 11 years ago Closed 11 years ago

There's no way to call SetDPI on AsyncPanZoomController through APZCTreeManager

Categories

(Core :: Graphics: Layers, defect)

26 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla26

People

(Reporter: jimm, Assigned: jimm)

References

Details

Attachments

(1 file)

AFAICT, we are working with an APZCTreeManager down in metro widget, so there's no way to set the dpi properly. We probably don't want to go fishing to apz objects to do this, I think what we need here is the ability to set the dpi on the main APZCTreeManager, and AsyncPanZoomController's would then get their dpi settings from that. APZCTreeManager would also have to flush dpi settings out.
Blocks: 907119
Assignee: nobody → jmathies
Attachment #792990 - Flags: review?(bugmail.mozilla)
I'll just land metro pref here and resolve the parent bug with this one.
Comment on attachment 792990 [details] [diff] [review] move dpi to tree mgr patch v.1 Review of attachment 792990 [details] [diff] [review]: ----------------------------------------------------------------- I'm not 100% sure this is right, because we might want different DPIs on different parts of the layer tree. Is the DPI here always a hardware DPI? Or is it related to the AppUnitsPerDevPixel scale factor?
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #3) > Comment on attachment 792990 [details] [diff] [review] > move dpi to tree mgr patch v.1 > > Review of attachment 792990 [details] [diff] [review]: > ----------------------------------------------------------------- > > I'm not 100% sure this is right, because we might want different DPIs on > different parts of the layer tree. Is the DPI here always a hardware DPI? Or > is it related to the AppUnitsPerDevPixel scale factor? The way I interpreted this was hardware dpi since we currently use this value for a couple of input hysteresis tests. The input metro sends to the apz is in device pixels and there doesn't appear to be any physical to logical conversion taking place on the receiving side. As far as different dpis per apz, I'd be surprised if we wanted that. But I'm pretty new to this code, so I might be wrong.
Comment on attachment 792990 [details] [diff] [review] move dpi to tree mgr patch v.1 Review of attachment 792990 [details] [diff] [review]: ----------------------------------------------------------------- Ok, looks fine then. Doesn't look like it should break any existing behaviour at any rate. ::: gfx/layers/composite/APZCTreeManager.h @@ +280,5 @@ > * lock also needs to be held when accessing the mRootApzc instance variable, as that > * is considered part of the APZC tree management state. */ > mozilla::Monitor mTreeLock; > nsRefPtr<AsyncPanZoomController> mRootApzc; > + static float sDPI; nit: Please add a blank line above sDPI
Attachment #792990 - Flags: review?(bugmail.mozilla) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: