Closed
Bug 596494
Opened 14 years ago
Closed 14 years ago
Update render mode on device removal
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: bas.schouten, Assigned: bas.schouten)
Details
Attachments
(3 files, 1 obsolete file)
1.01 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
1.86 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
15.42 KB,
patch
|
jrmuizel
:
review+
|
Details | Diff | Splinter Review |
We should update the render mode when we detect a device removal from our layer manager, since we should then make sure we can still support the current render mode.
Assignee | ||
Comment 1•14 years ago
|
||
This patch refactors how render-mode works. It removes the pref and adds a direct2d.force-enabled pref so people can still choose to force-enable D2D ignoring blocklists and such. It also wraps all the logic that determines what render mode is used into an UpdateRenderMode function, which can be called at runtime to re-determine the render mode. Existing fonts in the cache might continue using DirectWrite/GDI after direct write usage mode changed, but this should be acceptable for now. It should probably improved in a follow-up.
Attachment #475437 -
Flags: review?(jmuizelaar)
Assignee | ||
Comment 2•14 years ago
|
||
Attachment #475438 -
Flags: review?(roc)
Assignee | ||
Updated•14 years ago
|
Attachment #475438 -
Attachment description: Patch 2: Update render mode on device removal → Part 2: Update render mode on device removal
Assignee | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Updated•14 years ago
|
blocking2.0: ? → betaN+
Attachment #475438 -
Flags: review?(roc) → review+
Comment 3•14 years ago
|
||
Comment on attachment 475437 [details] [diff] [review] Part 1: Refactor and add UpdateRenderMode This shouldn't use cairo_verify_device() instead it should get the device and do the verification itself.
Assignee | ||
Comment 4•14 years ago
|
||
Attachment #475555 -
Flags: review?(jmuizelaar)
Assignee | ||
Updated•14 years ago
|
Attachment #475438 -
Attachment description: Part 2: Update render mode on device removal → Part 3: Update render mode on device removal
Assignee | ||
Comment 5•14 years ago
|
||
Updated for get d3d10 device method.
Attachment #475437 -
Attachment is obsolete: true
Attachment #475556 -
Flags: review?(jmuizelaar)
Attachment #475437 -
Flags: review?(jmuizelaar)
Comment 6•14 years ago
|
||
Comment on attachment 475555 [details] [diff] [review] Part 1: Expose method to get the D3D10 device for cairo d2d device I like the name cairo_d2d_device_get_device() name better.
Attachment #475555 -
Flags: review?(jmuizelaar) → review+
Comment 7•14 years ago
|
||
Comment on attachment 475556 [details] [diff] [review] Part 2: Refactor and add UpdateRenderMode v2 >+ >+ if (isVistaOrHigher && !safeMode && >+ (!d2dDisabled && (!d2dBlocked || d2dForceEnabled))) { This condition is pretty complex. Can we simplify this by either breaking it into multiple conditions or giving names to subexpressions. i.e the precedence between d2dDisabled and force enabled isn't immediately obvious to me.
Attachment #475556 -
Flags: review?(jmuizelaar) → review+
Comment 8•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/7a05dd5b25de http://hg.mozilla.org/mozilla-central/rev/c5608e9f3753 http://hg.mozilla.org/mozilla-central/rev/7cf62a2a821e
Assignee: nobody → bas.schouten
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 9•14 years ago
|
||
http://mxr.mozilla.org/mozilla-central/source/toolkit/content/aboutSupport.js#68 Does not this need to revise it?
Comment 10•14 years ago
|
||
(In reply to comment #9) Sorry spam, Please ignore
You need to log in
before you can comment on or make changes to this bug.
Description
•