All,
I don't know if this is a focus problem, or a problem with ksnapshot itself. But with ksnapshot configured to capture 'window under cursor' with no delay, if the window is not the top window, ksnapshot will capture any overlying window within the geometry of the window you are trying to capture. I've opened a normal bug for it:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=966
I don't know if this is gcc47, a bug in the desktop when focus set to 'follow mouse' or what. I have never seen this behavior before. Here are a couple of screenshots:
http://www.3111skyline.com/dl/dt/trinity/ss/ksnapshot-win-under-cursor-bug.j...
http://www.3111skyline.com/dl/dt/trinity/ss/ksnapshot-win-under-cursor-bug2....
Also, if you notice, the right side of the window is not captured correctly either. (possible libpng15 issue??)
Thoughts? tdegraphics build is:
cmake ${srcdir}/${pkgname#*-} \ -DCMAKE_CXX_FLAGS="-fpermissive" \ -DCMAKE_VERBOSE_MAKEFILE=ON \ -DCMAKE_INSTALL_PREFIX=${TDEDIR} \ -DWITH_T1LIB=ON \ -DWITH_LIBPAPER=ON \ -DWITH_TIFF=ON \ -DWITH_OPENEXR=ON \ -DWITH_PDF=ON \ -DBUILD_ALL=ON
(no patches)
Thoughts?
On 04/18/2012 11:53 AM, David C. Rankin wrote:
Thoughts?
Note, if the target window is already the top window, the screenshot is fine:
http://www.3111skyline.com/dl/dt/trinity/ss/ksnapshot-win-under-cursor-bug3....
Dne st 18. dubna 2012 David C. Rankin napsal(a):
All,
I don't know if this is a focus problem, or a problem with ksnapshot itself. But with ksnapshot configured to capture 'window under cursor' with no delay, if the window is not the top window, ksnapshot will capture any overlying window within the geometry of the window you are trying to capture. I've opened a normal bug for it:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=966
I don't know if this is gcc47, a bug in the desktop when focus set to 'follow mouse' or what. I have never seen this behavior before. Here are a couple of screenshots:
http://www.3111skyline.com/dl/dt/trinity/ss/ksnapshot-win-under-cursor- bug.jpg
http://www.3111skyline.com/dl/dt/trinity/ss/ksnapshot-win-under-cursor- bug2.jpg
Also, if you notice, the right side of the window is not captured correctly either. (possible libpng15 issue??)
Thoughts? tdegraphics build is:
cmake ${srcdir}/${pkgname#*-} \ -DCMAKE_CXX_FLAGS="-fpermissive" \ -DCMAKE_VERBOSE_MAKEFILE=ON \ -DCMAKE_INSTALL_PREFIX=${TDEDIR} \ -DWITH_T1LIB=ON \ -DWITH_LIBPAPER=ON \ -DWITH_TIFF=ON \ -DWITH_OPENEXR=ON \ -DWITH_PDF=ON \ -DBUILD_ALL=ON
(no patches)
Thoughts?
As far as I know, it works this way from the very beginning. And personally I do not consider it as an error. The switch does not say anything about that window should be pulled to the top. The user can prepare a scene to his liking and ksnapshot capture exactly such a situation.
Slávek --
On 04/18/2012 01:03 PM, Slávek Banko wrote:
As far as I know, it works this way from the very beginning. And personally I do not consider it as an error. The switch does not say anything about that window should be pulled to the top. The user can prepare a scene to his liking and ksnapshot capture exactly such a situation.
Slávek
Hmmm.. You are probably right. I know it should work that way for capturing 'Full Screen', but I thought that capturing 'Window under cursor' should capture the window under cursor and not the overlap. But if there is no logic in the code to handle adjusting window stacking, then it has probably been that way since the beginning and I've just not noticed. I'm using ksnapshot in virtualbox at 1280x800 so I have more overlapping windows than normal.
On 04/18/2012 01:03 PM, Slávek Banko wrote:
The user can prepare a scene to his liking and ksnapshot capture exactly such a situation.
Slávek
What about the corrupt part of the image on the right side? Did you see anything in the code that might explain it?
Dne st 18. dubna 2012 David C. Rankin napsal(a):
On 04/18/2012 01:03 PM, Slávek Banko wrote:
The user can prepare a scene to his liking and ksnapshot capture exactly such a situation.
Slávek
What about the corrupt part of the image on the right side? Did you see anything in the code that might explain it?
Sorry, I did not look into the code - I am busy working on backporting patches. I noticed in the git patches for SAK, so I'm very curious :)
Slávek --
-
David C. Rankin -
Slávek Banko