Closed
Bug 820654
Opened 12 years ago
Closed 11 years ago
Work - Clean up MetroInput's use of ModifierKeyState and nsIDOMTouch/nsDOMTouch
Categories
(Firefox for Metro Graveyard :: Input, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: TimAbraldes, Assigned: TimAbraldes)
Details
(Whiteboard: feature=work [completed-elm])
Attachments
(1 file, 3 obsolete files)
39.16 KB,
patch
|
jimm
:
review+
|
Details | Diff | Splinter Review |
Misc cleanup. Also removes the need for #include "KeyboardLayout.h" in MetroInput.cpp
Assignee | ||
Comment 1•12 years ago
|
||
This will apply cleanly only after applying the patch in bug 819223
Attachment #691172 -
Flags: review?(jmathies)
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 691172 [details] [diff] [review] Patch v1 I'm rebasing this to apply to elm tip since the work in bug 819223 is slightly delayed. I'll mark for review when I attach the updated patch
Attachment #691172 -
Flags: review?(jmathies)
Assignee | ||
Comment 3•12 years ago
|
||
Rebased to apply cleanly to elm tip
Attachment #691172 -
Attachment is obsolete: true
Attachment #693687 -
Flags: review?(jmathies)
Comment 4•12 years ago
|
||
http://mxr.mozilla.org/mozilla-central/source/widget/windows/KeyboardLayout.cpp#111 What was it about ModifierKeyState that we didn't like? Is there any way we can incorporate the improved key detection code in InitModifiersForGeckoEvent into ModifierKeyState::InitInputEvent?
Comment 5•12 years ago
|
||
I don't understand why the fix is necessary. If you don't want metro widget to depend on KeyboardLayout.h, you should move the related methods to WinUtils or something.
Assignee | ||
Comment 6•12 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #4) > http://mxr.mozilla.org/mozilla-central/source/widget/windows/KeyboardLayout. > cpp#111 > > What was it about ModifierKeyState that we didn't like? Is there any way we > can incorporate the improved key detection code in > InitModifiersForGeckoEvent into ModifierKeyState::InitInputEvent? There isn't anything particularly bad about ModifierKeyState. InitModifiersForGeckoEvent doesn't offer improved key detection; it basically mimics the functionality of ModifierKeyState. I wrote the previous patch because 1) I want to remove metro widget's need to include "KeyboardLayout.h" since "KeyboardLayout.h" defines classes that we shouldn't be using in Metro development. 2) The current implementation of MetroWidget doesn't use ModifierKeyState very well; it creates a whole bunch of them when it could instead just have 1. While the previous patch fixes these issues, a better fix would be to continue using ModifierKeyState in MetroInput, but to separate ModifierKeyState from "KeyboardLayout.h". This is the solution suggested by Nakano-san. (In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #5) > I don't understand why the fix is necessary. If you don't want metro widget > to depend on KeyboardLayout.h, you should move the related methods to > WinUtils or something. I've attached a patch that simply moves ModifierKeyState out of KeyboardLayout.h/cpp and into its own ModifierKeyState.h/cpp. Does this approach seem reasonable?
Attachment #693687 -
Attachment is obsolete: true
Attachment #693687 -
Flags: review?(jmathies)
Assignee | ||
Comment 7•12 years ago
|
||
In the interest of making forward progress, I'm limiting the scope of this bug to just MetroInput cleanup: using a single ModifierKeyState that is a member of MetroInput, and utilizing nsIDOMTouch more effectively (so that we don't have to create our own TouchEntry class). I've filed bug 825337 about separating ModifierKeyState from KeyboardLayout
Summary: Remove MetroInput's dependency on ModifierKeyState, miscellaneous clean-up of MetroInput → Clean up MetroInput's use of ModifierKeyState and nsIDOMTouch/nsDOMTouch
Assignee | ||
Comment 8•12 years ago
|
||
This patch cleans up MetroInput: It adds a ModifierKeyState member to MetroInput so that we don't have to create them all over the place It takes advantage of the nsIDOMTouch interface, making it so that we don't have to define and use a separate TouchEntry class It removes the "buttons" flag from MetroInput, since that is not as reliable as ModifierKeyState for keeping track of button state Miscellaneous other comment, whitespace, and naming fixes
Attachment #694249 -
Attachment is obsolete: true
Attachment #696418 -
Flags: review?(jmathies)
Updated•12 years ago
|
Attachment #696418 -
Flags: review?(jmathies) → review+
Assignee | ||
Comment 9•11 years ago
|
||
I built this patch locally and did a sanity test to make sure it didn't break anything horribly. Patch submitted to elm: https://hg.mozilla.org/projects/elm/rev/3afea2350981 Build containing the patch: https://tbpl.mozilla.org/?tree=Elm&rev=3afea2350981
Whiteboard: [metro-it2] → [metro-it2][completed-elm]
Updated•11 years ago
|
Summary: Clean up MetroInput's use of ModifierKeyState and nsIDOMTouch/nsDOMTouch → Work - Clean up MetroInput's use of ModifierKeyState and nsIDOMTouch/nsDOMTouch
Whiteboard: [metro-it2][completed-elm] → feature=work [completed-elm]
Comment 10•11 years ago
|
||
Resolving bugs in the Firefox for Metro product that are fixed on the elm branch. Sorry for the bugspam. Search your email for "bugspam-elm" if you want to find and delete all of these messages at once.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•