I don’t really see how we can separate it out. The code which figures out which event is being dispatched is pretty low level in HTMLElementWrapper.
Maybe there’s some way to use dependency injection to specify which events will be needed, but I’m not sure how easy that will be. FWIW, we’re probably going to want to add touch events at some point, but maybe we can write utility functions to prevent all that to be hard-coded in. > On Jul 26, 2017, at 9:52 PM, Alex Harui <aha...@adobe.com.INVALID> wrote: > > Will anyone ever really ship an app that doesn't need wheel support? Our > smaller examples don't need it, so I'm wondering if wheel support should > be separated out or not. > > Thoughts? > -Alex > > On 7/26/17, 9:27 AM, "Harbs" <harbs.li...@gmail.com > <mailto:harbs.li...@gmail.com>> wrote: > >> While you’re at it, if you could write a test for wheel events, that >> would be very helpful. >> >> I don’t have time to write tests for that right now. >> >> I just added properties for wheel events. Yishay and I added support for >> wheel events in the framework and falcon last week. (You will need the >> latest builds of Falcon to use wheel events in MXML at the least.) >> >> Thanks, >> Harbs >> >>> On Jul 26, 2017, at 4:22 PM, piotrz <piotrzarzyck...@gmail.com> wrote: >>> >>> Harbs, >>> >>> Give me some time, cause I wanted to test it before you merge. >>> >>> Thanks, >>> Piotr >>> >>> >>> >>> ----- >>> Apache Flex PMC >>> piotrzarzyck...@gmail.com >>> -- >>> View this message in context: >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl >>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl> >>> ex-development.2333347.n4.nabble.com >>> <http://ex-development.2333347.n4.nabble.com/>%2FFlexJS-MouseEvent-tp63542p63566.ht >>> ml&data=02%7C01%7C%7Cdd1a7c3fcc014d734c4008d4d44346a0%7Cfa7b1b5a7b3443879 >>> 4aed2c178decee1%7C0%7C0%7C636366832801744724&sdata=LZ9EAwK4S9FJdDG7L7PMNu >>> kR4XC5%2FiCFJeUxA54CQxY%3D&reserved=0 >>> Sent from the Apache Flex Development mailing list archive at >>> Nabble.com <http://nabble.com/>.
