Maybe I'm missing something, but the default on ksnapshot should be whole-desktop by default, then you can select individual window or region. The reason being that individual window captures accept a 'delay' input set by the user on the dialog and 'region' requires a user box-outline. That is not accessible when launched by default.
That was the entire purpose of setting
[PrtScr]='ksnapshot' Shift-[PrtScr]='ksnapshot --current'
Default behavior captures a snapshot of the screen, the alternate use captures the current window. What you are proposing is making 'ksnapshot -- current' the default behavior. At least for me, that somewhat defeats the purpose of the --current option for the alternate call.
Perhaps you are confusing a basic keyboard shortcut to capture the desktop to the clipboard versus actually launching Ksnapshot and manually changing the desired capture option. :)
I often take screen captures of windows rather than the entire desktop.
Regarding the preferred style for screen captures, I need to write those guidelines soon. We want all images in all handbooks to have the same consistent look. Yes, capturing images will require setting up a separate user account, theme, or a VM to ensure that consistency.
On ktorrent - it has always failed. The autofoo files are messed up and I'm no autofoo wizard. I think it will probably be an easy fix for a makefile/automake guru...
Refer to bug report 1465. I have to use the enable-closure configuration option. As i shared in the bug report, something changed after April 15 because I never had to use that option before I filed the bug report. I still can't build ktorrent without that option. I can't build with the additional handbook files with or without that option.
Darrell
On 01/27/2014 08:48 PM, Darrell Anderson wrote:
Refer to bug report 1465. I have to use the enable-closure configuration option. As i shared in the bug report, something changed after April 15 because I never had to use that option before I filed the bug report. I still can't build ktorrent without that option. I can't build with the additional handbook files with or without that option.
I will give it a shot as soon as the i686 build run I have going completes.
Man -- so far so good. (no jinxes...). If nothing unexpected occurs, we should build all 97 of the packages end-to-end without having to lift a finger. (fingers crossed) If that completes, then I will have both i686 & x86_64 package sets for TDE on current ARCH. I had great apprehension starting this rebuild that the drastic changes to Arch would have prevented TDE from building without substantial code changes required. So far I am pleasantly surprised, TDE is in very, very good shape if it will build on the bleeding-edge. Good job to you, Tim, Slavek, All...
Now it Calvin will just hunt up some server space for holding the packages for testing, we will be in great shape.