- 04 Aug, 2015 1 commit
-
-
James Robinson authored
This introduces the notion of event disposition and allows event targets (widgets and render objects) to consume events that should not be processed further. This is needed by the Switch component in the Drawer in the stocks example. The Switch is embedded in a DrawerItem. The Switch handles the gesture tap event to toggle its state and should handle pointer events to allow swiping and draw its own radial reaction. The DrawerItem also handles gesture taps to allow toggling the switch value when tapping anywhere on the drawer and to draw its own ink splash. When tapping on the switch, both the switch's render object and the DrawerItem's listener are in the event dispatch path. The Switch needs to signal in some fashion that it consumed the event so the DrawerItem does not also try to toggle the switch's state.
-
- 30 Jul, 2015 1 commit
-
-
Adam Barth authored
When embedded by the view_manager, sometimes we receive pointerup or pointercancel events without having received a cooresponding pointerdown event. The underlying issue is that the view_manager doesn't capture on pointerdown and instead performs a new hit test for every pointer event. We should fix that in view_manager, but, in the meantime, this patch makes us not crash in this scenario. Fixes #339
-
- 28 Jul, 2015 3 commits
-
-
Adam Barth authored
Rather than using a microtask to schedule component build functions, instead use the scheduler. We now tread building just like layout and painting as a visual update.
-
Chinmay Garde authored
-
Chinmay Garde authored
-
- 16 Jul, 2015 1 commit
-
-
Collin Jackson authored
-