Mouse double click event....

[John Tan]

I was trying out my windowless plugin's FB::MouseDoubleClickEvent on FireFox but somehow, this event will never be triggered. However, as I search around, I found a catch-all FB::WindowsEvent. I tried it and it works. I wonder why.... BTW, I'm using FB1.6 

[Gaurav Raj]

Yes this happened to me as well. Seems like firebreath doesn't filter out double click event. So the event is not called. The FB::WindowsEvent helps you to directly access all the raw window events and handle them yourself. So you get all of them.

You can also inherit from the FB::PluginWindowWin class (for Windows events) to directly access all the windows events and create your custom plugin window creation class.

On Tue, Apr 30, 2013 at 1:24 PM, John Tan <tjk...@gmail.com> wrote:

I was trying out my windowless plugin's FB::MouseDoubleClickEvent on FireFox but somehow, this event will never be triggered. However, as I search around, I found a catch-all FB::WindowsEvent. I tried it and it works. I wonder why.... BTW, I'm using FB1.6 

--
 
---
You received this message because you are subscribed to the Google Groups "firebreath-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebreath-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Gaurav Raj

[John Tan]

Has anyone ever encountered in Chrome where event 0x203 (WM_LBUTTONDBLCLK) will never be sent by the browser? Same goes for Safari. FireFox and IE is fine. WM_LBUTTONUP and WM_LBUTTONDOWN is triggered though. I suppose I'll have to emulate this be monitoring the 2 close button downs.

 

[dougma]

Yes, I've seen this; it's strange. My work-around was the same as what you're proposing.

I'm considering some code to aggregate these various workarounds to event strangenesses... but fear it will be incomplete and fragile in the face of evolving browser implementations.

[John Tan]

Lucky thing for FireFox (and I think IE too) is that 2 LBUTTONDOWN and LBUTTONDBLCLK is not set together. As such, the existing doubleclick event can still stay while adding the dbl click simulation.