There are MouseController beads in many places already. IMO, they would
be replaced with touch/gesture controllers for those who need it. The
rollover code isn't needed on mobile devices AFAICT. The
DragDropControllers at one point "injected" new event types into the
ElementEvents list.
So ther
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63579.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
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 pro
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" wrote:
>While you’re at it, if you could write a test for wheel events, that
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63573.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
Harbs,
My local Maven build is failing and I'm actually not sure why... [1]
[1] https://paste.apache.org/hHHU
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63573.html
> piotrzarzyck...@gmail.com
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63566.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
ge in context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63566.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
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:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-tp63542p63566.html
Sent from the Apache Flex Development
or without a button pressed), if
>> any keyboard key was also pressed at the same time.
>>
>> I don't see why computations need to be made unless some value in one
>> platform is unavailable and needs to be calculated, but I don't see any
>> that fall into
ed (either with or without a button pressed), if
> any keyboard key was also pressed at the same time.
>
> I don't see why computations need to be made unless some value in one
> platform is unavailable and needs to be calculated, but I don't see any
> that fall into this cat
e
platform is unavailable and needs to be calculated, but I don't see any
that fall into this category.
Having FlexJS MouseEvent extend a platform event class seems to have it
drawbacks, but it also makes the event work in the current system, so I
would let that go.
What's disturbing
I've been doing work with Drag and Drop and that involves mouse events. I'm
> wondering if someone could give me a history on the Apache FlexJS MouseEvent?
> Specially, its use of localX/Y and screenX/Y.
>
> I'm wondering why the platform implements do not simply assign
I've been doing work with Drag and Drop and that involves mouse events. I'm
wondering if someone could give me a history on the Apache FlexJS MouseEvent?
Specially, its use of localX/Y and screenX/Y.
I'm wondering why the platform implements do not simply assign their version o
it would be both flash.MouseEvent as well as
>>flex.Event ...
>>
>>
>>Chris
>>
>>________
>>Von: Harbs
>>Gesendet: Freitag, 15. Juli 2016 13:58:03
>>An: dev@flex.apache.org
>>Betreff: Re: [FlexJS] MouseEvent extends flash event
>&g
e
>flex.Event interface, it would be both flash.MouseEvent as well as
>flex.Event ...
>
>
>Chris
>
>
>Von: Harbs
>Gesendet: Freitag, 15. Juli 2016 13:58:03
>An: dev@flex.apache.org
>Betreff: Re: [FlexJS] MouseEvent extends flash event
ent.
>
>
> Chris
>
>
> Von: yishayw
> Gesendet: Freitag, 15. Juli 2016 11:52:17
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] MouseEvent extends flash event
>
> It turned out handleOK on SimpleAlertView was expecting an Event and
> complai
t.
>
>
> Chris
>
>
> Von: yishayw
> Gesendet: Freitag, 15. Juli 2016 11:52:17
> An: dev@flex.apache.org
> Betreff: Re: [FlexJS] MouseEvent extends flash event
>
> It turned out handleOK on SimpleAlertView was expecting an Event and
> complained about receiving a Mou
Well how about having an Interface "Event" and every form of event implementing
that? I think a MouseEvent should be an Event.
Chris
Von: yishayw
Gesendet: Freitag, 15. Juli 2016 11:52:17
An: dev@flex.apache.org
Betreff: Re: [FlexJS] MouseEvent ext
context:
> http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-extends-flash-event-tp53730p53923.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
7.n4.nabble.com/FlexJS-MouseEvent-extends-flash-event-tp53730p53923.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 7/6/16, 9:37 PM, "yishayw" wrote:
>Is there any reason why
>
>COMPILE::SWF
> public class MouseEvent extends flash.events.MouseEvent
>
>rather than
>
> COMPILE::SWF
> public class MouseEvent extends Event
>
>It might solve
>
>https://issues.apache.org/jira/browse/F
:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MouseEvent-extends-flash-event-tp53730.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
23 matches
Mail list logo
