Edward Welbourne wrote:
> Soroush Rabiei
>> 3. Number of months in all years are fixed.
>
> Is there no lunar calendar with occasional extra months ?
Of course there is. Any lunar calendar adjusted for consistency with the
solar year necessarily has occasional intercalar months. The Jewish cale
> On 6 Dec 2016, at 15:44, Shawn Rutledge wrote:
>
>
>> On 3 Dec 2016, at 00:36, Kevin Kofler wrote:
>>
>> Shawn Rutledge wrote:
>>> http://www.galago-project.org/about.php
>>>
>>> sounds like it’s just for “presence” to tell instant-messaging clients
>>> whether you are using the computer o
On 2016-07-13 23:55, Lars Knoll wrote:
On 13 Jul 2016, at 20:10, Marc Mutz wrote:
[...]
It should also be noted that there are two categories of SiCs:
a. those that can be fixed client-side without breaking compat with
older Qt
versions, and
b. those which cannot
IMO, SiCs of type (a) ar
On Fri, Jan 13, 2017 at 01:58:45AM +, Stottlemyer, Brett (B.S.) wrote:
> On 12 January 2017 at 08:39, Lars Knoll wrote:
> >* The module solves a problem our users have
> > - It either implements new and so far non existent functionality
> > - Or it solves an existing problem in a new and bett
Soroush Rabiei
> Sorry for being noisy on this list, but I think we have several issues
> needed discussion before going further.
I should note that Lars still holds to the view that we should keep this
out of QDate: which seems to imply roughly just upstreaming
KCalendarSystem, albeit with the op
Sorry for being noisy on this list, but I think we have several issues
needed discussion before going further.
First we have a design decision to make, the minimal set of
assumptions on calendaring systems. According to my minute research we
can assume following facts on every calendar that is in-
FYI,
I'm tinkering with writing .ico files and tried to visualise the result on
Linux, which gave me an error message:
%> gwenview5 test.ico
QImageReader::read() using format hint "ico" failed: "Unknown error"
A bad Qt image decoder moved the buffer to 22 in a call to canRead()! Rewinding.
Image
Александр Волков wrote:
> 13.01.2017 13:58, Александр Волков пишет:
>> 13.01.2017 13:52, Konstantin Tokarev пишет:
>>> Why not just use QImageWriter?
>> QImageWriter doesn't support wrting miltiple images into one file.
>>
>
> Possible fix: https://codereview.qt-project.org/#/c/182255/
Yep, that
On Friday January 13 2017 13:52:36 Konstantin Tokarev wrote:
>Why not just use QImageWriter?
Because it doesn't append but writes only a single image, the 1st image in the
sequence, suprisingly (and I presume not just on Friday the 13th :)) ?
R
___
De
Hi,
Slight correction: It's not a regression against 5.7, but it is still a
regression [☹] . I'll fix it ASAP for 5.8.1 and
back-port it also to the 5.6 branch.
Simon
From: Development on
behalf of Simon Hausmann
Sent: Friday, January 13, 2017 1:23:47 PM
T
Hi,
While I agree that this (58133) is a bug, I would not classify it as a bug to
halt the entire release. It's neither
a regression or a particularly common scenario to run into, I would argue. That
said, it's a crash, it needs fixing
and I'll fix it.
Simon
__
On Friday January 13 2017 14:01:10 Konstantin Tokarev wrote:
Hi,
> Alternatively you can import QtIcoHandler from Qt 5.6 which is licensed as
> LGPL 2.1
Thanks, that'd be easy, only the license is different, nothing else :)
> Why not just use QImageWriter?
I understand from CodeReview 1822
13.01.2017 13:58, Александр Волков пишет:
13.01.2017 13:52, Konstantin Tokarev пишет:
Why not just use QImageWriter?
QImageWriter doesn't support wrting miltiple images into one file.
Possible fix: https://codereview.qt-project.org/#/c/182255/
___
13.01.2017, 13:29, "René J.V. Bertin" :
> Hello,
>
> Can someone please have a look at the KDE RR below and tell us whether or not
> it's OK to include qicohandler.* the way I propose in the patch under review?
> There are some whitespace changes and I added a preprocessor token to exclude
> i
13.01.2017 13:52, Konstantin Tokarev пишет:
Why not just use QImageWriter?
QImageWriter doesn't support wrting miltiple images into one file.
I wonder is there a bugreport for it?
___
Development mailing list
Development@qt-project.org
http://lists.qt-
13.01.2017, 13:29, "René J.V. Bertin" :
> Hello,
>
> Can someone please have a look at the KDE RR below and tell us whether or not
> it's OK to include qicohandler.* the way I propose in the patch under review?
> There are some whitespace changes and I added a preprocessor token to exclude
> i
On 13 January 2017 at 14:15, Tim Blechmann wrote:
> > All known blockers should be fixed in these packages and we are
> > targeting to release Qt 5.8.0 Tue 17^th January if nothing really
> > serious found during testing. So please inform me immediately if there
> > is some new blocker in the pac
Hello,
Can someone please have a look at the KDE RR below and tell us whether or not
it's OK to include qicohandler.* the way I propose in the patch under review?
There are some whitespace changes and I added a preprocessor token to exclude
ico read support.
My understanding of the GPL legalese
Hi,
I scheduled a test build in the CI against 5.8 (as dev continues to be broken).
The results are public at
http://testresults.qt.io/coin/integration/playground/qtremoteobjects/tasks/web_playground_qtremoteobjects_1484293648911
There are few issues:
1) namespaced build doesn't work
2) licen
19 matches
Mail list logo
