- User Since
- Oct 19 2016, 11:08 AM (189 w, 16 h)
Apr 26 2020
Apr 1 2020
LGTM, is the new function available since old CUPS versions? Just to make sure it won't break usage with old versions.
Mar 13 2020
Well I still think that this applet rewrite is very useless, very little care about their printers, it's the print jobs that matter, still the patch looks fine, although I see the buttons showing up before the selection is fully expanded.
Mar 12 2020
Dec 2 2019
Dec 1 2019
Well I think your approach is probably the best to this, I'd only change the sanitize loop to use iterators and erase as afair they are a little faster.
But the remove old jobs code would also need fixing to account with the dups
Oh, now I see the problem with this, I tried many times reproduce but never managed to see the issue with the dups IDs.
Nov 5 2019
Aug 27 2019
Ok, while not an ideal change, these options aren't the kind of options that should be changing that often so I'm ok. Thanks
Aug 26 2019
Yes, the idea is to be up to date, the issue it seems to be that some CUPS installations keep asking the server password on each query instead of having it cached.
Apr 1 2019
Mar 21 2019
Mar 18 2019
Feb 20 2019
I ended up compiling it using vcpkg toolchain directly on Windows, which showed this isn't required.
Feb 15 2019
I'm not entirely sure this is really needed on Windows, but when cross-compiling this allowed to search for the katehighlightingindexer.exe which wouldn't run because I was on Linux...
Feb 1 2019
Jan 10 2019
Sep 23 2018
Sep 17 2018
Sep 10 2018
Sep 9 2018
Well the issue will probably depend on the server,
for example Apache2 with Nextcloud it returns forbidden for both operations,
in Cloudlyst which does:
you get a file with a different file name as URL.
Since 'ç' is extended ASCII this "fails" only because URL are sopposed
to use only printable ASCII chars
Sep 8 2018
Ping? This is a pretty obvious fix, desturl is QString which later becomes latin1 loosing characters...
Jul 10 2018
Jul 9 2018
Jun 6 2018
Mar 21 2018
LGTM I only confused about why do you need QRegExp :P
AFAIK this is the wrong way of handling signals, don't recall exactly what the problem is, but Qt documentation says to create a pipe, attach a QSocketNotifier to it, and write data to it when the signal is caught, then the QSN signal will call qApp->quit();
Mar 17 2018
Mar 8 2018
Feb 21 2018
OK, thanks I'll probably make it mandatory for 1.1.0 as it's a simple dep and the less ifdefs the better
oops my bad
Thanks, I've been thinking into making this dependency mandatory, could you please tell me why would you like to build without AppStream or are you just fixing the bug? thanks