I filed bug 24755 against enlightenment. Turns out it's kuickshow that's broken. Reproducible: Always Steps to Reproduce:
Kuickshow isn't being developed anymore, so it's not much of a surprise you're starting to have problems with it. I'd recommend Mosfet's pixieplus as a replacement (media-gfx/pixieplus-kde).
I tried pixieplus, and what do you know: pixieplus has the _exact_ same problem as kuickshow does. Comparing these two failing apps, I think I know how this happened: both request a window opened in a way that the window titlebar is above the visible screen area (more screen estate for the picture), which worked great with kuickshow: open picture, use mouse wheel, keyboard shortcuts or pop-up-window to control the program, hit "q" to close it. It seems most window managers (including KDE's own) reject the requested coordinates and move the window down until the title bar fits. e16 OTOH used to position the window as requested, but in the latest version it doesn't do that anymore, instead it fails rather badly. Besides, I could open one picture in kuickshow and then browse through all pictures in that folder with the mouse wheel. Doesn't seem like pixieplus can do that. Instead, I always have to close it twice (first the image window, then the "pixie editing browser" that always pops a second later. Most annoying. Oh, and if a "View images as fullscreen" choice is selected, pixieplus will maximize over two monitors, which is something most applications know better these days. How many bugs do you want me to file for these?
I feel your pain - I experience these problems as well (with pixieplus). If you want to file bug reports you're probably best to do it at bugs.kde.org or with mosfet directly as he is the one that's going to have to make the fixes to his code.
actually, turns out its enlightenment thats broken :D they just fixed it in cvs Roger Luethi wrote: > There are quite a few applications that break with 0.16.6pre. Turns out the > reason for this is the new _partial_ support for the Window Manager > Specification. > > The new e16 tricks programs into believing the standard is implemented, but > it fails to set _NET_WORKAREA, which is a _required_ property (it's been > this way since 1.0) [1]. Depending on the application, hilarity ensues > (some try to fit into a 0x0 work area). > > The attached patch is against e16 CVS and has seen little testing. It works > for me (fixes broken apps), but you may well have better values for that > property, or better locations to invoke EWMH_SetWorkArea() from. > This makes kuickshow behave quite a bit more reasonable :-)
i just added pre6 ... that should fix this bug ...
fix confirmed.
fixed confirmed by author
