On woensdag 19 februari 2020 00:51:12 CET Thiago Macieira wrote:
> Also https://bugreports.qt.io/browse/QTBUG-70606, which is when I reported
> the
> problem to AMD, but we did not introduce a workaround since we didn't know it
> was this widespread.
We for sure encountered it very, very often
I kept out of this for the longest time, especially because people have been
quoting my blog post, but I give up now.
On zaterdag 8 juni 2019 18:14:36 CEST Giuseppe D'Angelo via Development wrote:
>
> Then, it comes a moment when "upstream" stuff has more and more
> advantages -- more speed (a
On dinsdag 21 mei 2019 02:04:42 CEST Quinn Romanek via Development wrote:
> Is there any current support/plan to support HDR pixel formats within Qt?
Dmitry prepared a number of patches to make it possible to display HDR images
in Qt:
Implement openGL surface color space selection in Angle
On zondag 21 april 2019 10:43:37 CEST Allan Sandfeld Jensen wrote:
> It seems a lot of new Windows API is UWP specific. For instance for HDR
> support I need to read the luminance level for SDR content in HDR mode, and I
> could only find UWP API for that.
We had to patch Qt a lot to make HDR w
On vrijdag 12 oktober 2018 14:31:33 CEST Konstantin Ritt wrote:
> It didn't.
Then what else made it necessary to suddenly add lots of #include
lines?
--
https://www.krita.org
signature.asc
Description: This is a digitally signed message part.
___
De
On vrijdag 12 oktober 2018 15:57:35 CEST Mathias Hasselmann wrote:
> Hi Boudewijn,
>
> these kind of refactorings are neccessary to keep code maintainable I fear.
Well... If code stops building from Qt 5 to another Qt 5, that means that
thousands of projects have to change their code. Thousands
in a way that people who
are not CS phd's can understand. std completely and utterly fails
in that. Parts of Qt's docs are bad enough, but there's nothing in
cppreference.com that would pass muster for my gsoc students.
--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.
iving it, if not, I wonder what the
right direction would be.
--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
___
Development m
I just found that qtbase-opensource-src-5.6.1-1.tar.xz
unpacks to qtbase-opensource-src-5.6.1, which completely
breaks any automated system like mxe (mxe.cc) which depends
on the foldername being the same tarball name.
Was this intentional, or just an oversight?
--
Boudewijn Rempt | http
On Wed, 27 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote:
On Wednesday 27 April 2016 08:50:48 Boudewijn Rempt wrote:
[snip]
As a Debian developer, you might also consider that you should never
ever package Krita 3 for Debian with a Qt 5.6 without this fix. You'd have
to carry the
Krita (and later on,
OpenToonz).
--
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thu, 5 Nov 2015, Thiago Macieira wrote:
It gets worse if you have KF5-based image format plugins, since kimg_eps.so
links to QtPrintSupport. Fortunately, none of them today link to other KF5
libraries, but can we continue to count on that?
Well, the KRA and OpenRaster image format plugins t
f that library/plugin
>
In Krita, we use Vc to abstract away all this stuff -- we code our
vectorization optimizations using Vc and then Vc takes care to select the best
alternative run-time. I don't know how well it would fit with Qt, but I'm very
glad with it:
http://code.compen
e policy and a bunch of opinions and other
> > non-arguments. Honestly, this discussion we're having right now has
> > been the only productive one.
>
> I think the above pretty much invalidates all your arguments.
>
> Now, to put it politely, fuck off.
>
Or, pu
On Monday 10 September 2012 Sep, Shaw Andy wrote:
> > On domingo, 9 de setembro de 2012 13.25.29, Boudewijn Rempt wrote:
> > > The solution for a bug can never be to wilfully break existing
> > > applications!
> > > What can I as an application dev
On Sunday 09 September 2012 Sep, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 11.46.31, Boudewijn Rempt wrote:
> > > Preferably, it should be fixing it once and for all.
> >
> > Well, given that Digia actually seems to have a patch for the bug in
> &
On Sun, 9 Sep 2012, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
>>> Note that this also applies for Qt 4.8. If the support is broken there and
>>> causing issues like Ariel is describing, it's definitely a P1 that needs
>>> fixing. If we can't muster the
n... Isn't the the problem that
in Qt4, the puck sends mouse events in the wrong way?
> 2) Create a commandline --enable-wacom
> 3) Remove Wacom altogether
>
> OTOH I have few resources to offer more that the bug reporting and
> testing on the 40+ workstations i have.
I
On Thursday 06 September 2012 Sep, Thiago Macieira wrote:
> On quinta-feira, 6 de setembro de 2012 09.13.01, Boudewijn Rempt wrote:
> > > But since I made the suggestion to remove it: if we can't get it tested
> > > and get it to work, just disable the support. No code
seems clear that nobody knows :-(.
> But since I made the suggestion to remove it: if we can't get it tested and
> get it to work, just disable the support. No code needs to be removed. Just
> make the loading of the Wacom DLL always fail.
So, basically, QTabletEvent will sti
I would have more bugs if I tried to do tablet handling on my
own, like in the Qt 3.x days.
And what are you going to do with api's like QTabletEvent? Remove those as
well? I thought that moving to Qt5 was supposed to be smooth and easy. You
cannot chop off api like that...
--
Boudewijn
applications like Maya, Nuke, Mari or Photoshop Elements also use QTabletEvent?
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
___
Development mailing list
Development@qt-project.org
http://lists.q
On Thu, 16 Aug 2012, Thiago Macieira wrote:
>> - A complete API for reading/writing Open Document Format files.
>
> Outside the scope. You should just use the Calligra libs.
>
> If the Calligra libs can be slimmed down, they could be accepted as addons.
>
>> - An API for reading and writing .gz, .
excellent.
>
>
> From: development-bounces+alexandros.dermenakis=nokia@qt-project.org
> [development-bounces+alexandros.dermenakis=nokia@qt-project.org] on
> behalf of ext Boudewijn Rempt [b...@valdyas.org]
> Sent: Monday, July
either -- it most likely is just a
mess.
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
he!
> Good one João!! :-D
Now I am as well :D But I have to admit that it did spoil my dinner :-). Maybe
because stuff like this really doesn't sound too out of this world!
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
__
#x27;ve been had for the straight man, right :-) I admit it...
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
omething dreamed by those
guys who wrote the app you're trying to maintain or something you wrote
yourself four weeks ago but had forgotten about.
Lovely.
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
___
one reason for Qt to exist and that is other people's code. Don't
mess with that, especially not for merely cosmetic reasons.
I don't want to have to change ten year old coding style habits -- I want to
improve my application, fix bugs, add features and keep my users hap
equences: I know of one application
that was hit by optimizations in QPainter between Qt 4.5 and Qt 4.6 where a
huge part of the core engine had to be rewritten.
1) 8389 instances of qreal, 2845 of QRectF, 6601 of QPointF, 253 of QLineF.
--
Boudewijn Rempt
http://www.valdyas.org, http://www.krita.org
?
>
I had to use it in the Hyves Desktop because none of the other sound options of
Qt would work both on Windows XP and on Vista... And we didn't care that much
about X11, because 98% of our users were on Windows, 2% were using OSX and the
rest (mainly the developers at Hyve
32 matches
Mail list logo
