Hi,
On 16 August 2015 at 16:47, David Edmundson wrote:
> Edit: on re-read that comes across as harsh, what I meant was I was just
> curious if this was discussed somewhere as I would have wanted to add some
> comments.
>
Heh, that's fine :-)
As for discussions, Martin Graesslin originally sug
On Sun, Aug 16, 2015 at 11:23 AM, David Edmundson <
da...@davidedmundson.co.uk> wrote:
>
>
>> It is further recommended (although it is not required) that
>> KScreenGenie be set as the default screenshot tool,
>
>
> Recommended by whom?
>
> Edit: on re-read that comes across as harsh, what I meant
> It is further recommended (although it is not required) that
> KScreenGenie be set as the default screenshot tool,
Recommended by whom?
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Hi,
On 10 August 2015 at 02:04, Thomas Lübking wrote:
> On Sonntag, 9. August 2015 21:39:37 CEST, Boudhayan Gupta wrote:
>>
>> Do I have to do it the xcb way (get an atom, call xcb_change_property()
>> and
>> all - and does this property even have an atom)
>
>
> Yes - "unfortunately". I filed bug
On Sonntag, 9. August 2015 22:57:54 CEST, Boudhayan Gupta wrote:
I should have this, as well as the current 200ms timeout to take care of
other not-so-nice compositors
Yes.
and note in the user manual that if you see a ghost of the window in your
screenshots, just set a delay in KSG itself?
On 10 August 2015 at 02:04, Thomas Lübking wrote:
>> If there's sample code I can refer to, all the better
>
> Here it comes:
Wow thanks, that is extremely helpful! Yes, I do support X-less builds
(the define is HAVE_XCB).
So what I gather is - I should have this, as well as the current 200ms
ti
> As someone who didn't follow the discussion too closely: Will it eventually
> be renamed to KSnapshot and just replace it? :-)
Yes
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
On Sonntag, 9. August 2015 21:39:37 CEST, Boudhayan Gupta wrote:
Do I have to do it the xcb way (get an atom, call xcb_change_property() and
all - and does this property even have an atom)
Yes - "unfortunately". I filed bug 351137 about this, but notice that any resolution will
require a somew
On Sunday 09 August 2015 19:11:56 Bhushan Shah wrote:
> On Sun, Aug 9, 2015 at 3:34 PM, Boudhayan Gupta wrote:
> > This is a heads-up that I'll be doing a stable release of KScreenGenie
> > (v2.0.0) sometime late 15th August (after 10 PM) / early 16th August
> > 2015, Indian Standard Time.
>
> Si
Hi Thomas,
> Since closing animations can however easily take 500ms, it's not sufficient
> to cover them. (And instead waiting for ages until the window animation
> *may* have ended, we added this hint instead)
This is going to sound novice-y, but can you point me in the right
direction as to *ho
On Sonntag, 9. August 2015 21:20:03 CEST, Boudhayan Gupta wrote:
Will this work on hide() as well
Yes.
or is there no actual difference between closing a window and hiding it?
Not in this regard. The window gets unmapped, that all what matters here.
(There're, however, in general differences
Hi Thomas,
> For cases where you bypass the screenshot effect (and in general) ensure to
> set a _KDE_NET_WM_SKIP_CLOSE_ANIMATION property to "1" on all windows you do
> not want to see on the shots.
>
> Waiting for "arandomtime™" won't work reliably because the closing effects
> can take differen
On Sonntag, 9. August 2015 20:06:23 CEST, Boudhayan Gupta wrote:
I'm not using KWin's screenshot effect. In fact I'm dropping directly
to pure xcb.
For cases where you bypass the screenshot effect (and in general) ensure to set a
_KDE_NET_WM_SKIP_CLOSE_ANIMATION property to "1" on all windows
Hi Bhushan,
> Since you are having stable release, do you want bugs.kde.org product created?
>
> (I know that this is going to be ksnapshot-next, but for this release
> it is kscreengenie
Your call. I don't mind either way. In fact, having a Bugzilla product
might help casual users report bugs si
Hi,
>> With subsequent screenshots only. It looks like the KScreenGenie
>> window is not able to hide completely.
Hmm, I just noticed it happens at my end too. I'll increase the
timeout to 300msec (from 200 now).
>
>
> You're not talking to the kwin screenshot effect to hint bypassing your
> win
On Sun, Aug 9, 2015 at 3:34 PM, Boudhayan Gupta wrote:
> This is a heads-up that I'll be doing a stable release of KScreenGenie
> (v2.0.0) sometime late 15th August (after 10 PM) / early 16th August
> 2015, Indian Standard Time.
Since you are having stable release, do you want bugs.kde.org produc
On Sonntag, 9. August 2015 14:31:34 CEST, Siddhartha wrote:
On 9 August 2015 at 17:22, Boudhayan Gupta wrote:
Does this happen on the initial screenshot, or ones that you take
subsequently with the "Take New Screenshot" button, or both?
With subsequent screenshots only. It looks like the KScr
On 9 August 2015 at 17:22, Boudhayan Gupta wrote:
> Does this happen on the initial screenshot, or ones that you take
> subsequently with the "Take New Screenshot" button, or both?
With subsequent screenshots only. It looks like the KScreenGenie
window is not able to hide completely.
>> Visit ht
Hi Siddhartha,
On 9 August 2015 at 17:00, Siddhartha wrote:
> An issue I've been facing: the KScreenGenie window also appears along
> with the screenshot. It happens for all the "Area" types AFAICT. PFA
> an example demonstrating this.
Does this happen on the initial screenshot, or ones that you
Hi Boudhayan,
On 9 August 2015 at 15:34, Boudhayan Gupta wrote:
> The release will be tagged from master, and you can consider master to
> be at feature and string freeze as of now. If there are any minor bugs
> if you'd like me to fix (or would like to fix yourself), or if there
> are any i18n i
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 wrote:
> Hi Gregor,
>
> Sorry for the delay in replying; I was busy with college. I've replied inl
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 slow
see below
On 27/04/15 03:43, Boudhayan Gupta wrote:
> I'll target the build problems first: XCB is not detected. Here's how
> I include Qt5X11Extras:
>
> find_package(XCB COMPONENTS XFIXES IMAGE UTIL CURSOR)
> if (XCB_FOUND)
> find_package(Qt5X11Extras ${QT_MIN_VERSION} REQUIRED)
> find_p
On 2015-04-20, Boudhayan Gupta wrote:
> Well, Sune Vuorela and Luigi Toscano got on my back and I ended up
> re-doing the ungrab workaround the proper way, without the dependency
> on private headers, so yay! Try building master now.
Yay. Thanks.
/Sune
>> Visit http://mail.kde.org/mailman/list
;>>> http://wstaw.org/m/2015/04/20/plasma-desktopLJ1852.png Version 5.4.2
>>>
>>> Needed package name on openSUSE is
>>> libqt5-qtdeclarative-private-headers-devel.
>>> As a rule, the names are libqt5-$upstreammodulename-[private-headers]-devel,
>>
hese private-headers
>>> installed:
>>>
>>> http://wstaw.org/m/2015/04/20/plasma-desktopLJ1852.png Version 5.4.2
>>
>> Needed package name on openSUSE is
>> libqt5-qtdeclarative-private-headers-devel.
>> As a rule, the names are libqt5-$upstre
J1852.png Version 5.4.2
>
> Needed package name on openSUSE is
> libqt5-qtdeclarative-private-headers-devel.
> As a rule, the names are libqt5-$upstreammodulename-[private-headers]-devel,
> either explicitly, or via Provides.
>
> Cheers,
> Hrvoje
>>
>> ---
package name on openSUSE is libqt5-qtdeclarative-private-headers-devel.
As a rule, the names are libqt5-$upstreammodulename-[private-headers]-devel,
either explicitly, or via Provides.
Cheers,
Hrvoje
>
> Forwarded Message ----
> Subject: Re: kscreengenie / was: Rev
t;> http://wstaw.org/m/2015/04/20/plasma-desktopLJ1852.png Version 5.4.2
>>
>>
>> Forwarded Message
>> Subject:Re: kscreengenie / was: Review Request 122763: KIPI cleanups
>> Date: Mon, 20 Apr 2015 16:13:57 +0530
>> From: Boudhayan Gupt
ote:
> Hmm. Maybe I have to install another package to have
> QtQuickWidgets/private/qquickwidget_p.h ? Currently I these private-headers
> installed:
>
> http://wstaw.org/m/2015/04/20/plasma-desktopLJ1852.png Version 5.4.2
>
>
> Forwarded Message
> Subject:
Hmm. Maybe I have to install another package to have
QtQuickWidgets/private/qquickwidget_p.h ? Currently I these private-headers
installed:
http://wstaw.org/m/2015/04/20/plasma-desktopLJ1852.png Version 5.4.2
Forwarded Message
Subject:Re: kscreengenie / was: Review
Hi Gregor,
>
> Yes it is on mine. Startup time KSnapshot: instantly, KScreenGenie: 1 second.
> And it
> actually does not capture an image. The result is a white rectangle. The
> mouse cursor is
> included when the checkbox is checked, though. But note that my KF5 build is
> about 1 - 2
> weeks
See below.
On 19/04/15 20:26, Boudhayan Gupta wrote:
>> Loading SendTo menu in a thread
>> ---
>> I tried that also in KSnapshot. See [ksnapshot: Fill SendTo menu async to
>> fix Bug
>> 312495](https://git.reviewboard.kde.org/r/120920/) but at that time this was
>> no
33 matches
Mail list logo
