arguably we could just claim fluxbox's event handling is broken and
leave it unusable for the poor guys (by reverting c101d8f3c again).
example: i go into a window with my pointer, click the left mouse
button, release it again, move away. in dwm i get motionnotify,
buttonpress, buttonrelease, motionnotify, as i would expect.
in fluxbox i get this weird series of unrelated events, like so:
MotionNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1245552, (33,44), root:(680,67),
state 0x0, is_hint 0, same_screen YES
LeaveNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1246463, (33,44), root:(680,67),
mode NotifyGrab, detail NotifyVirtual, same_screen YES,
focus YES, state 256
EnterNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1246464, (33,44), root:(680,67),
mode NotifyUngrab, detail NotifyVirtual, same_screen YES,
focus YES, state 256
KeymapNotify event, serial 36, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ButtonPress event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1246463, (33,44), root:(680,67),
state 0x0, button 1, same_screen YES
EnterNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0x0, time 1246464, (33,44), root:(680,67),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 256
KeymapNotify event, serial 36, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ButtonRelease event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1246671, (33,44), root:(680,67),
state 0x100, button 1, same_screen YES
LeaveNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0x0, time 1246671, (33,44), root:(680,67),
mode NotifyUngrab, detail NotifyInferior, same_screen YES,
focus YES, state 0
MotionNotify event, serial 36, synthetic NO, window 0xe00001,
root 0xcc, subw 0xe00002, time 1253746, (44,44), root:(691,67),
state 0x0, is_hint 0, same_screen YES
note all the unpredictable keymap and enter/leave events.
i still think we shouldn't break fluxbox if we don't have to (but i'm
not using it myself which doesn't help the priority..).
-jo
On Sat, Mar 9, 2013 at 6:01 AM, Pascal Obry <[email protected]> wrote:
>
> This is release blocking to me.
>
> - the count of image is not properly displayed/updated
>
> - clicking on the background does not remove all selection
>
> Reverting c101d8f3c from master fixes both issues.
>
> Which was a revert for fluxbox event handling.
>
> Johannes, can you have a look?
>
> --
> Pascal Obry / Magny Les Hameaux (78)
>
> The best way to travel is by means of imagination
>
> http://v2p.fr.eu.org
> http://www.obry.net
>
> gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> darktable-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
