On Mon, 17 Sep 2018 22:00:56 +0300 sergio <ser...@outerface.net> said:
> On 17/09/2018 20:45, Carsten Haitzler (The Rasterman) wrote: > > >> 1. right (or some other) button hold + scroll > > > > in apps? this is up to widget sets/apps to do. wm's don't do this. efl > > doesn't support this - but it has wheel support already and regular left > > click+drag support for touch... > > In my imagination it was "Any" "Action Context". there is a dividing line between what wm's can and do do and what is sensible to do and then what "apps" do (app here being an x client with a regular app in it where most of the time it is a toolkit library like gtk, qt or efl handling events and what to do with them). what you describe above is squarely in the "up to the app" land. > >> 2. right button press -> left button press -> right button release -> > >> left button release > >> 3. 2 vice versa > > > what is that meant to do? > > press (and hold) mouse button 3, than press (and hold) mouse button 1, > than release mouse button 3, than release mouse button 1 > > xev: > > ButtonPress event, serial 39, synthetic NO, window 0x2800001, > root 0x6b8, subw 0x0, time 517114277, (117,135), root:(919,165), > state 0x0, button 3, same_screen YES > > ButtonPress event, serial 39, synthetic NO, window 0x2800001, > root 0x6b8, subw 0x0, time 517115037, (117,135), root:(919,165), > state 0x400, button 1, same_screen YES > > ButtonRelease event, serial 39, synthetic NO, window 0x2800001, > root 0x6b8, subw 0x0, time 517115549, (117,135), root:(919,165), > state 0x500, button 3, same_screen YES > > ButtonRelease event, serial 39, synthetic NO, window 0x2800001, > root 0x6b8, subw 0x0, time 517116053, (117,135), root:(919,165), > state 0x100, button 1, same_screen YES > > > I'd like to switch desktops with mouse only. With full-screen windows > without panels. this is a really nasty thing to do.we'd have to trap left and right mouse in all contexts. it will work in a smallish subset of cases (e.g. this mail i'm typing now, right mouse opens up a context menu that the app/toolkit is handling... after that the mouse will be grabbed and the wm will never see/get the left click). in the case of chromium since it is its own toolkit, the left click after right is down will dismiss the menu... but as this is also trapped by chromium... it won't get to the wm... so again - won't work. in wayland we could do this as all input goes through the compositor... but that is a separate matter and i'm not sure you're using wayland yet... :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
