On Sun, 03 Nov 2013 09:56:45 +0000 Thomas Strobel <ts...@cam.ac.uk> said:

> On Sun, 2013-11-03 at 14:49 +0900, Carsten Haitzler wrote:
> 
> > On Sat, 02 Nov 2013 08:55:50 +0000 Thomas Strobel <ts...@cam.ac.uk> said:
> > 
> > > Hi everyone,
> > > 
> > > I wanted to extend Evas' pointer for a way to selectively grab certain
> > > events, while repeating others. After looking at the event system for a
> > > while, I'm currently thinking that the cleanest way would probably be to
> > > extend Evas' pointer struct for a list which keeps track of all grabbed
> > > object, and to use the current pointer.objects.in to just account for
> > > objects where the pointer is "pointing" into.
> > > 
> > > Changing Evas on such a deep level could trigger a lot of side effects,
> > > and so I wanted to ask you if you had any idea how to implement a
> > > selective event grabbing?
> > 
> > yes. it will. which means the current behavior has to stay and NEW behavior
> > has to be explicitly requested. that is possible. (eg request a new pointer
> > grab mode).
> > 
> > now the use i can see is actually multitouch and./or pen support WHEN you
> > want pen ANd mouse AND touch all to be independent and not linked (touch
> > doesnt affect mouse - pen does not either etc.). and at least for the case
> > of multi touch where you may want each touch point to have its own grab
> > "pointer.in" list thats separate of the primary (first) touch/mouse.
> 
> Or, Multi-pointer X, but that's not quite what I'm after. I am looking
> for a way to grab certain events from one pointer with an object, let's
> say DOWN/UP, let the object follow others, e.g. MOVE, but still forward
> the non-grabbed events back into the object hierarchy.

this seems useufl indeed for multi-pointer too.

> > > A selective event grabbing would be very handy to implement a drag and
> > > drop system for Evas objects.
> > > 
> > > Many thanks in advance!
> > 
> > what about the current event system disallows for implementing dnd? :)
> 
> To me it seems that currently an object needs to grab the mouse pointer
> to get e.g. MOVE updates and UP events. But this means that other
> objects can't receive IN/OUT events anymore, and so they can't detect
> whether the dragging pointer went in or not. Or, is there a smart way
> around?

if you move the object WITH the mouse .. this object follows. that means then
the pointer ends up IN the object u drag all the time... not in the target drop
object. this is the case in xdnd in x11 too... the solution is for whoever is
handling the drag to query the object(s) UNDER the drag point and then send a
SPECIAL "someone is trying to drag IN to you.. what do you want to do?"...
similar with drop (mouse-up). :)


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to