On Sun, Dec 07, 2014 at 12:48:06PM +0100, Johannes Hofmann wrote:
Interestingly if I comment out the following code that was introduced in fltk-1.3.3 things work as expected for me:
--- src/Fl.cxx.orig 2014-12-07 12:27:31.291453000 +0100 +++ src/Fl.cxx 2014-12-07 12:44:14.991338000 +0100 @@ -962,6 +962,7 @@ if (x) x->set_key_window(); } #elif defined(USE_X11) + /* if (fl_xfocus != win) { Fl_X *x = Fl_X::i(win); if (!Fl_X::ewmh_supported()) @@ -969,6 +970,8 @@ else if (x) // New WMs use the NETWM attribute: Fl_X::activate_window(x->xid); } + */ + fprintf(stderr, "====> Fl_X::ewmh_supported() -> %d\n", Fl_X::ewmh_supported()); #endif fl_xfocus = win; }
The fprintf line gives: ====> Fl_X::ewmh_supported() -> 0 on my system.
Could you try the above patch to fltk-1.3.3 on you system too and report what Fl_X::ewmh_supported() returns on your system?
====> Fl_X::ewmh_supported() -> 1 So the problem only exists with fltk's handling of non-ewmh capable setups? v4hn