Hi, I've re-written the GUI in QWidgets. Startup is almost instant now. Give it a spin! I haven't done any bugtesting at all, so you might find something.
On 29 April 2015 at 10:45, Boudhayan Gupta <m...@baloneygeek.com> wrote: > Hi Gregor, > > Sorry for the delay in replying; I was busy with college. I've replied inline > >> >> I installed the required library (xcb cursor devel) and now it compiles. I >> would also find >> it better when you fail the build if XCB CURSOR is not found. >> >> Startup speed: still at least 3 times slower than ksnapshot (both build on >> top of debug >> mode KF5). >> > > I pushed out a fix two days ago that replaced one QTimer::singleShot() > with a QMetaObject::invokeMethod(Qt::QueuedConnection), which improved > the startup speed by a lot (I'm on Release builds of KF5). On my > computer it starts up almost as fast as KSnapshot. I can notice that > it's just a tiny bit slower, but that's probably because of QML. > > If the delay gets annoying, I'm going to abandon QML and go for a > QWidgets based approach. For the time being, though, I'm letting it > be. > > As for CMake, I'll make the modules REQUIRED. Thanks for this bugreport. > >> >> E.g. Greenshot does it like this: If you press Print Screen then >> 1) The whole screen including the cursor is captured immediately. >> 2) The image is drawn on top of the actual screen image. >> So you see a still image of your screen. >> If you do not look closely you might not notice it. >> 3) Select the rectangular region as with kscreengenie. >> > > This is what happens with kscreengenie when compositing is not > available. In case it is available, I switch to a live view. I guess > what I can do is record the mouse cursor position when the grab was > initiated (before the cropper appears), and then overlay the cursor > image at the recorded position. > > -- Boudhayan Gupta >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
