ow...@qt-project.org.
Nice.
That's what most people call a "spam".
Regards,
Konstantin
пт, 24 февр. 2023 г. в 22:34, Konstantin Ritt :
> How can one develop Qt for VxWorks with this Commercial source
> package, having no paid account?
> Please stop announcing these annoyi
How can one develop Qt for VxWorks with this Commercial source
package, having no paid account?
Please stop announcing these annoying things to those who were subscribing
to Qt development ML.
Regards,
Konstantin
пт, 24 февр. 2023 г. в 18:35, List for announcements regarding Qt releases
and deve
Ignoring a large part of the community IS a problem.
Most people won't say they aren't ok with something. Until it is too late
to say anything at all.
Regards,
Konstantin
вт, 27 сент. 2022 г. в 23:02, Elvis Stansvik :
> Den tis 27 sep. 2022 kl 21:52 skrev Elvis Stansvik :
> >
> > Den tis 27 sep
That's not about Qt development, that's about commercial Qt fork
development.
For commercial users, you have a dedicated commercial-only mailing list(s).
I’m sure you can configure your email client to send all emails with sender
“Konstantin Ritt” to the bin if these messages are irr
Please stop announcing this kind of updates through the development mailing
list!
Konstantin
вт, 27 сент. 2022 г. в 14:20, Tarja Sundqvist :
> Hi all,
>
>
>
> we have released Qt 6.2.6 LTS Commercial today. Please see the blog post:
>
> https://www.qt.io/blog/commercial-lts-qt-6.2.6-released
>
This becomes more and more non-intuitive.
let a: font = f // copy f because a is value-typed?
let b = a// copy because a is typed, and b's type is inferred
from a?
let c = f// ref because f is JS-ish type
function foo(arg) {
return arg
}
let d = foo(b) // ref becau
pplicable bug fixes go to dev and are picked to all active branches.
> The fix to QTBUG-102962 was merged to 6.3 branch at the end of April, so
> the fix is in Qt 6.3.1 released in June, as well as in the latest Qt 6.3.2
> release as well as the soon-to-be released Qt 6.4.0 release.
>
>
&
It is probably the most destructive and annoying thing you did!
I'll try to rephrase what you said in that announcement: "Dear community,
please stick to unstable, semi-functional versions of Qt, test them and
report bugs you've found (for free), so we could better support our
valuable customers (
The bug is fixed now.
Regards,
Konstantin
вс, 6 мар. 2022 г. в 16:18, Konstantin Ritt :
> Volker:
>>
>> On Fri, Mar 4, 2022 at 8:56 PM Konstantin Ritt wrote:
>>
>>> Oh well, my codereview.qt-project.org account is also inaccessible.
>>> This is not
> Regards,
>
> Andy
>
>
>
> *From:* Development *On Behalf Of
> *Konstantin
> Ritt
> *Sent:* Friday, March 4, 2022 1:43 PM
> *To:* Konstantin Shegunov
> *Cc:* Qt development mailing list
> *Subject:* Re: [Development] Maintainance Tool
>
>
&g
>
> Volker:
>
> On Fri, Mar 4, 2022 at 8:56 PM Konstantin Ritt wrote:
>
>> Oh well, my codereview.qt-project.org account is also inaccessible. This
>> is not about your attitude towards RU gov, but your attitude towards me
>> personally.
>>
>> [image:
> The problem is not the open source, it's that providing the downloads is a
> business (it has a cost for the company offering them, for example). Then
> business rules apply.
>
> The same way that obtaining sources for (L)GPL content you got as a binary
> is
> also a business obligation and must
and what the Qt company wants
> to achieve in the end? What is the purpose?
>
> So far, it looks more like a clowning: "the circus is gone, but the clowns
> remain."
>
> Qt Company can't stick your tongue out of the USA ass? :)
>
> I had a higher opinion of Qt C
, it looks more like a clowning: "the circus is gone, but the clowns
> remain."
>
> Qt Company can't stick your tongue out of the USA ass? :)
>
> I had a higher opinion of Qt Company up to this point ...
>
> This is not serious somehow, some kind of kindergarten. LOL
to access something you have purchased
> then let me know and I will get someone to get in touch with you directly
> about this. Otherwise, for the time being, this IP block will be in place.
>
>
>
> Regards,
>
> Andy
>
>
>
> *From:* Development *On Behalf Of
&g
I don't care. I need some explanations here, at public dev ML.
Regards,
Konstantin
пт, 4 мар. 2022 г. в 15:27, Konstantin Shegunov :
> Hi,
> I imagine you're using a russian IP address, so this[1] should shed some
> light on the matter.
>
> Kind regards,
> Konstantin.
>
> [1]: https://forum.qt.
> Installation from this IP address is not allowed
Are you joking? What's going on there?!
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Recreating QGuiApplication is not a common case, ever.
Plus no one said the QPixmap cache would be shared across QGuiApplication
instances. I don't think that was the intention. In fact that could be used
to access some data of another "run" meant to be destroyed/erased/forgotten.
Using QThreadSto
Wrong list? AFAIK, this mailing list is about developing Qt, not about
promoting some closed-source products ;p
Regards,
Konstantin
ср, 12 мая 2021 г. в 15:05, Tarja Sundqvist :
> Hi all,
>
>
>
> We have released Commercial LTS Qt 5.15.4 today! Please read more
> information from the release bl
ing access to QFuture’s
> internals might be useful, but this is not something we would recommend to
> do to all users. That’s why, I think, adding an API that gives access to
> QFuture’s d-ptr (as it was suggested earlier) might be an option.
>
>
>
> Best regards,
>
> Son
I was implementing a similar feature few years ago and had the same problem
with QFuture internals --
https://codereview.qt-project.org/c/qt/qtbase/+/210243
As there was no interest in making those better, I had to hack it in a way
I won't promote here ;p
But since QFuture took a new life with QPro
Tend to agree with Thiago.
If there is a decision to close 5.15 sources, there'll be no more work from
external/unpaid contributors.
Regards,
Konstantin
пн, 4 янв. 2021 г. в 15:21, Thiago Macieira :
> On Monday, 4 January 2021 07:55:03 -03 Tuukka Turunen wrote:
> > We can arrange access for ext
> I think we then had discussions when moving from Qt 4 to Qt 5, that we
will start requiring RTTI.
However this was never promoted, and now you're saying people who ported
their projects with no-rtti to Qt5 had to enable rtti years ago or expect
crashes?)
Thanks to Alberto for pointing this issu
I facing a discussion like this every couple of months ;)
Yes, we should have a b with accent, cause it is exactly what the
programmer asked QString for; it is not our fault if b with accent is not
what he meant to get after replace.
QString (like any other tool) must not be used blindly or with z
in your .pro file:
CONFIG += lrelease
QMAKE_LRELEASE_FLAGS += -removeidentical
LRELEASE_DIR = $$OUT_PWD/GeneratedFiles/i18n
EXTRA_TRANSLATIONS += \
$$files($$[QT_INSTALL_TRANSLATIONS]/*.qm) \
$$files($$PWD/i18n/*.ts)
Regards,
Konstantin
ср, 13 мая 2020 г. в 13:47, David C. Partri
Ah I see Q_DISABLE_COPY(QScopeGuard), so perhaps that's the docu issue.
Regards,
Konstantin
пт, 13 мар. 2020 г. в 18:38, Konstantin Ritt :
> I just noticed the documentation says
> > The callable shouldn't throw when executed, copied or moved.
> , which brings a quest
I just noticed the documentation says
> The callable shouldn't throw when executed, copied or moved.
, which brings a question: is there really a particular reason to copy
QScopeGuard instance? what the expected behavior for the instance copy
then, call f in some other place?
Regards,
Konstantin
р, 19 февр. 2020 г. в 18:26, Konstantin Ritt :
> Should we ever try to work around issues caused by broken CPUs? Maybe we
> should warn the user instead (with big red banner) and decline to install
> anything at all?
>
> > (or buy Intel)
>
> Or let's maybe also try to work
Should we ever try to work around issues caused by broken CPUs? Maybe we
should warn the user instead (with big red banner) and decline to install
anything at all?
> (or buy Intel)
Or let's maybe also try to work around Meltdown and Spectre on i, just for
symmetry? ;)
Regards,
Konstantin
ср,
Just checked the implementation (thanks to woboq, once again) and you're
right. These are completely unacceptable.
Konstantin
пн, 8 июл. 2019 г., 20:28 Thiago Macieira :
> On Monday, 8 July 2019 10:53:42 -03 Konstantin Ritt wrote:
> > > See my reply to Marc: users want US-ASCII
пн, 8 июл. 2019 г., 16:43 Thiago Macieira :
> On Monday, 8 July 2019 04:38:28 -03 Konstantin Ritt wrote:
> > Perhaps there is a particular reason for the user to manipulate binary
> data
> > as if it were a string? So give him that string, QString.
>
> See my reply to M
пн, 8 июл. 2019 г., 5:44 Thiago Macieira :
> On Sunday, 7 July 2019 23:26:40 -03 Konstantin Ritt wrote:
> > As we have string views now, I'd vote for deprecating the string
> > manipulation methods in QByteArray. I doubt we could make QByteArray a
> true
> > vector o
вс, 7 июл. 2019 г., 12:58 André Hartmann :
> Hi Thiago,
>
> > But QByteArray is encoding-indeterminate since it can carry any type.
>
> Correct, it is often used as "generic raw data array", e.g. in QFile,
> Q*Socket, QSerialPort, QCanBusFrame etc. Here we really need to treat
> the data as-is, w
I doubt QByteArray really fits "text" scope.
As for QLocale, I think it is a material for the "unicode" scope; same for
QUnicodeTools, QUnicodeTables, QTextBoundaryFinder and maybe BiDi impl from
QtGui.
Regards,
Konstantin
пт, 7 июн. 2019 г. в 19:01, Edward Welbourne :
> Hi all,
>
> Just to sa
пн, 27 мая 2019 г. в 11:46, Edward Welbourne :
> сб, 25 мая 2019 г., 12:30 Mutz, Marc via Development
> >>>> Repeat after me: default ctors do _not_ establish a valid value.
>
> As an aged C programmer I can respect that ;^>
>
> On 2019-05-25 17:24, Konstantin R
сб, 25 мая 2019 г., 20:42 Mutz, Marc via Development <
development@qt-project.org>:
> On 2019-05-25 17:24, Konstantin Ritt wrote:
> > сб, 25 мая 2019 г., 12:30 Mutz, Marc via Development
> >> Repeat after me: default ctors do _not_ establish a valid value.
> >
> &
сб, 25 мая 2019 г., 12:30 Mutz, Marc via Development <
development@qt-project.org>:
> Further to the question about default ctors for such "obvious" stuff as
>
> On 2019-05-21 10:27, Mutz, Marc via Development wrote:
> > class QRect {
> >int x, y, w, h;
> > public:
> >QRect
вт, 21 мая 2019 г., 14:25 Mutz, Marc via Development <
development@qt-project.org>:
> On 2019-05-21 13:03, Konstantin Ritt wrote:
> > вт, 21 мая 2019 г., 11:32 Mutz, Marc via Development
> > :
> >
> >> And while the partially-formed
> >> state
вт, 21 мая 2019 г., 11:32 Mutz, Marc via Development <
development@qt-project.org>:
> And while the partially-formed
> state can be extended to non-pimpled classes easily:
>
> class QRect {
> int x, y, w, h;
> public:
> QRect() = default;
> };
> QRect r; // part
Writing and proposing a patch would take less time than discussing pros and
cons here.
Konstantin
пн, 13 мая 2019 г., 12:31 Konstantin Shegunov :
> On Mon, May 13, 2019 at 2:42 AM Christian Gagneraud
> wrote:
>
>> On Mon, 13 May 2019 at 07:47, Konstantin Shegunov
>> wrote:
>> > Doesn't this i
what about the other corner case:
`
~Some() {
const auto children = someChildren();
for (auto child : children) {
if (!child->isDepleted()) {
// 'detach' and let it die alone, some later...
child->setParent(nullptr);
QObject::connect(child, &Chil
Just wandering, what `QObject:: children ()` shall return? ;p
Konstantin
пт, 3 мая 2019 г., 22:09 Konstantin Ritt :
> Ivan,
>
> note that observer_ptr is mostly like
>
> templateusing observer_ptr = T*;
>
>
> so what about
>
>
> layout2->addWidget(
Ivan,
note that observer_ptr is mostly like
templateusing observer_ptr = T*;
so what about
layout2->addWidget(layout->addWidget(make_unique("right")))->setFlat(true);
?
Regards,
Konstantin
пт, 3 мая 2019 г., 21:41 Иван Комиссаров :
> Thiago, can you please elaborate how you see this?
>
Please read the QDateTime docs accurately.
Konstantin
вт, 9 апр. 2019 г., 15:11 Pouya Shahinfar :
> Although QDateTime has a full set of methods for working with date and
> times in Qt, It could lead to misunderstanding. How? Well when you are
> saving a date or time in this class you do not kn
> - Introduce some iterator that iterates over unicode code points.
QStringIterator
> We *should* have a string type (I don't care what you call it) that acts
> on strings indexed by Unicode characters, not in terms of a
> representation. Whether that string type internally uses UTF-16 or
> UT
> https://utf8everywhere.org/ states *"UTF-16 is the worst of both worlds,
being both variable length and too wide"*
https://utf8everywhere.org/ *states bullshit. try reading an alternative
sources.*
Regards,
Konstantin
ср, 16 янв. 2019 г. в 13:20, Edward Welbourne :
> Marco Bubke (16 January
+1 for []()
Regards,
Konstantin
чт, 10 янв. 2019 г. в 15:51, Vitaly Fanaskov :
> I vote for shorter form as well.
>
> But the documentation should be extended with the Philippe's second
> example. Trailing return type is rarely required, but we cannot omit
> parameters list in this case, becau
It didn't.
Regards,
Konstantin
пт, 12 окт. 2018 г. в 13:59, Giuseppe D'Angelo via Development <
development@qt-project.org>:
> Hello,
>
> Il 12/10/2018 12:48, b...@valdyas.org ha scritto:
> > Which of course breaks source compatibility. It's bad enough to have to
> > adapt one's codebase; but t
Can we have both OpenSSL 1.0.x and 1.1.x supported when configured with
-openssl-runtime and choose 1.0 or 1.1 with -openssl-linked? Anyhow?
Regards,
Konstantin
2018-02-13 14:13 GMT+03:00 Konstantin Tokarev :
>
>
> 13.02.2018, 14:09, "Edward Welbourne" :
> > On Friday, 9 February 2018 10:04:30 P
changing the parameter's default value *is* binary compatible.
Regards,
Konstantin
2018-01-16 20:35 GMT+04:00 Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com>:
> > The "just change" introduces a binary incompatibility - right ?
>
> I don't think it does: the QString is constructed on the
Plz use https://bugreports.qt.io/ for bug reports and feature requests.
Qt Development ML is for discussions around Qt development, not even about
development with Qt.
Regards,
Konstantin
2018-01-13 22:27 GMT+04:00 Denis Shienkov :
> The problem was in Qt::AA_EnableHighDpiScaling option.
>
>
> Then what module should it be in?
My +1 for QtNetwork (unless we're going to move QSsl related code to a
separate Qt module)
Regards,
Konstantin
2017-08-23 10:25 GMT+04:00 Lars Knoll :
> Hi,
>
> I’ll look into it. But it’ll take a few days.
>
> Cheers,
> Lars
>
> > On 18 Aug 2017, at 22:11, T
I don't see any need in distinguishing different OAuth implementations for
Qt -- once we have an "officially supported" Qt module, it'll be a default
opt-in for the user's code.
+1 for QtOAuth as a separate module
Regards,
Konstantin
2016-08-13 11:28 GMT+04:00 Sune Vuorela :
> On 2016-08-12, Fr
> The QtGamepad module is a technology preview of the API which provides
classes and functions to access *CAN and ModBus*.
;)
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/devel
Hi,
Did you file a bug report? ML is not really the right place for reporting
bugs.
Briefly, the CJK characters in your text are covered by some fallback font
for which the font metrics are slightly different, so that the line height
is the sum of a max ascent, max descent, and max leading (see
Q
Yet another question: when we write Item { id: item; width: 5cm }, what
would item.width return? value expressed in logical pixels?
Konstantin
2016-02-18 15:05 GMT+03:00 Sorvig Morten :
>
> > On 18 Feb 2016, at 12:35, Nikita Krupenko wrote:
> >
> > 2016-02-18 12:50 GMT+02:00 Hausmann Simon <
>
2016-02-11 3:47 GMT+04:00 Thiago Macieira :
> On quinta-feira, 11 de fevereiro de 2016 03:00:02 PST Konstantin Ritt
> wrote:
> > > CaseSensitive => no case folding, no
> > > normalisation
> > > CaseSensitiveNormalize
2016-02-11 1:36 GMT+04:00 Thiago Macieira :
> On quarta-feira, 10 de fevereiro de 2016 19:46:49 PST Knoll Lars wrote:
> > They should only compare true with full case folding rules. This is
> > something we have so far not implemented in Qt; as you noted below we're
> > still using simple case fol
2016-02-10 23:46 GMT+04:00 Knoll Lars :
> Hi Thiago,
>
> On 10/02/16 19:27, "Development on behalf of Thiago Macieira" <
> development-boun...@qt-project.org on behalf of thiago.macie...@intel.com>
> wrote:
>
>
>
>
>
> >Hi all
> >
> >(especially Konstantin!)
> >
> >When reviewing a change, I notic
My +1.
Konstantin
2015-10-27 10:37 GMT+03:00 Eskil A. Blomfeldt via Development <
development@qt-project.org>:
> Hi,
>
> According to the data from Google Play, there are currently only 7.4% of
> active devices on Android versions 15 and below (< 4.1).
>
> https://developer.android.com/abou
Maybe JSON.stringify(obj) is what you need?
Konstantin
2015-11-07 21:52 GMT+04:00 Luke Parry :
> Is it possible to override the toString method for native c++ QObject
> types for use in QML scripts?
>
> e.g. using
>
> Q_INVOKABLE QString toString() const;
>
> This doesn't appear to work because
2015-10-17 8:58 GMT+04:00 Thiago Macieira :
> On Saturday 17 October 2015 07:14:58 Konstantin Ritt wrote:
> > 2015-10-17 6:23 GMT+04:00 Thiago Macieira :
> > > On Saturday 17 October 2015 03:34:51 Konstantin Ritt wrote:
> > > > - QString::fromRawData(u"hello w
2015-10-17 6:23 GMT+04:00 Thiago Macieira :
> On Saturday 17 October 2015 03:34:51 Konstantin Ritt wrote:
> > - QString::fromRawData(u"hello world", 5) /* { d=nullptr, b=.., s=5 } */
> -
> > explicitly means "no owning, deep-copy when necessary"
>
> And
If QString in Qt6 could be { QArrayData *d; ushort *b; int s }, then it
supersedes QStringView in all aspects:
- QString(u"hello world", 5) /* { d=.., b=.., s=5 } */ - still has a
superpower of COW, etc
- QString::fromRawData(u"hello world", 5) /* { d=nullptr, b=.., s=5 } */ -
explicitly means "no
>
> > You're misrepresenting the argument. QString doesn't support other
> encodings
> > because UTF-16 is the best for the task at hand and we have too much
> legacy to
> > support. Because of that, QCollator only supports UTF-16.
>
> I buy the legacy argument but I don't buy that utf 16 is the be
2015-10-15 17:52 GMT+03:00 André Somers :
> Op 15-10-2015 om 14:52 schreef Konstantin Ritt:
> >
> >
> > For everything but US-ASCII / Latin-1, UTF-8 isn't faster than UTF-16
> > (feel free to compare their complexity against UTF-32).
> > And why "pure C
2015-10-15 11:00 GMT+03:00 Bubke Marco :
> On October 15, 2015 08:45:30 Knoll Lars
> wrote:
>
> > On 14/10/15 23:51, "Bubke Marco" wrote:
> >
> >>On October 14, 2015 23:10:26 Thiago Macieira
> >>wrote:
> >>> Qt does not have to provide a comparator that operates on something
> >>>other than
> >
My first instinct was suggesting MS to support Unicode in their console...
but then I tried to reproduce the described issue on OS X and succeeded.
qDebug() << "this is сообщение на русском";
which I'd expect to be treated like a byte array, gives me
this is сообщение на русском
though
qDebug()
2015-06-23 20:47 GMT+04:00 Giuseppe D'Angelo :
> On Tue, Jun 23, 2015 at 12:17 PM, Knoll Lars
> wrote:
> > Qt 5.7:
> >
> > * New compiler baseline with gcc 4.7 and VC++ 2012
> > * Enable and use the C++11 features supported by these compilers
> > unconditionally
> > * WEC7 not supported anymore,
#define Q_OBJECT \
public: \
Q_OBJECT_CHECK \
QT_WARNING_PUSH \
Q_OBJECT_NO_OVERRIDE_WARNING \
static const QMetaObject staticMetaObject; \
virtual const QMetaObject *metaObject() const; \
virtual void *qt_metacast(const char *); \
virtual int qt_metacall(QMetaOb
2015-05-23 21:51 GMT+04:00 m...@rpzdesign.com :
> Konstantin:
>
> Maybe you could add some useful guidance to your response.
>
Sure I could.
> The point of interest is that it must be a QObject derived return.
>
> Maybe a pointer to a QObject.
>
QObject doesn't allow deep-copy, so yes a pointe
2015-05-23 21:20 GMT+04:00 mark diener :
> Hello:
>
> I came across a use case where I wanted to return a QAbstractListModel from
> a Q_INVOKABLE in a C++ QObject based class.
>
> The explicit constructor for QAbstractListModel requires a construction of
> these classes that forces the Q_INVOKABLE
2015-05-21 10:16 GMT+04:00 Rutledge Shawn :
>
> So I’d add both frame and frameCount to Image, which would be enough in
> this example, and then you don’t need the ImageDocument for such a simple
> use case.
>
Doesn't this mean Image becomes a light-weight variant of ImageDocument?
How will image
2015-05-20 19:27 GMT+04:00 Иван Комиссаров :
>
>
> 2015-05-20 15:18 GMT+03:00 André Somers :
>>
>> I think that it makes sense to attempt to load a header if it exists.
>> If not... Not sure. Probably need to read the entire file in order to
>> determine what it contains?
>>
>
> Any other opinion
2015-05-19 22:12 GMT+04:00 Rutledge Shawn :
> I think the new API should have multi-page support. It would be useful
> for pdf, djvu, multi-page tiff, and for looking at individual frames of
> animated gif, png, etc., to the extent that we write plugins for those.
>
IIUC, this already covered by
To make the settings persistent, you have to set
http://doc.qt.io/qt-5/qml-qt-labs-settings-settings.html#application-identifiers
(note however that settings Qt.application.name & Co won't probably help in
this case (bug?)).
Konstantin
2015-05-13 22:18 GMT+04:00 Federico Buti :
> Hi,
>
> I've i
I guess this came from QSslEllipticCurve.
+1 for not doing that until it really affects release build [with
non-broken compilers].
Regards,
Konstantin
2015-05-13 17:45 GMT+04:00 Matthew Woehlke :
> On 2015-05-13 04:25, Marc Mutz wrote:
> > Hi,
> >
> > I'd like to suggest the following addition t
Any links/code/docs?)
Konstantin
2015-04-30 0:26 GMT+04:00 Sandro Andrade :
> Hi there,
>
> Some time ago, I started the development of QtModeling : a qt add-on
> aimed at providing metamodeling features and the basic infrastructure
> for dealing with software models. It already has a lot of int
2015-04-24 16:33 GMT+04:00 Marc Mutz :
> Hi,
>
> While implementing qHash() overloads for gui/math3d classes, I found that
> QQuaternion gained several methods for 5.5 which I don't like:
>
> *EulerAngles():
>
> They are missing a QEulerAngles class. Instead, they deal with (float,
> float,
> floa
2015-04-24 16:32 GMT+04:00 Gunnar Sletta :
>
> > On 24 Apr 2015, at 14:33, Marc Mutz wrote:
> >
> > Hi,
> >
> > While implementing qHash() overloads for gui/math3d classes,
>
> Why are we doing this? a QHash makes very little sense me..
>
Completely agreed.
Konstantin
__
In case you're on Qt 4.x, look at QFont <-> QString and QFont <->
QDataStream (|de)serialization. I recall there was a bug fixed in ~5.3,
though I don't know if it was backported to 4.x.
Konstantin
2015-04-18 14:34 GMT+04:00 René J.V. :
> Hello,
>
> The specific question: how/where is (QFontEng
Just FYI,
http://www.daveperrett.com/articles/2012/07/28/exif-orientation-handling-is-a-ghetto/
http://webmasters.stackexchange.com/questions/16684/ipad-and-iphone-browser-rotating-images-on-site
(note that OS from Apple is a bit "special")
and the CSS3 working group discussion:
http://lists.w3.or
2015-04-23 16:04 GMT+04:00 Alberto Mardegan :
> On 04/23/2015 02:34 PM, André Somers wrote:
> > What is the problem with using
> >
> > Image {
> > source: "someImage.jpg"
> > autorotate: true
> > }
> >
> > Again: note that QImage != QML Image
> >
> > I don't like globals if they can be
>
> On Thursday, 23 April 2015 00:11:23 CEST, Alberto Mardegan wrote:
> > as long as the behaviour was configurable with a single line
> > change (a static method on QGuiApplication, maybe?).
>
Stop polluting QGuiApplication! Seriously.
We already have a complete solution -
https://codereview.qt-
Konstantin
2015-04-22 15:32 GMT+04:00 Alberto Mardegan :
> On 04/22/2015 09:39 AM, André Somers wrote:
> > I'm with Konstatin on this one: it seems like a regression to me. It
> > would be a useful feature to add, but then add it in such a way that it
> > is actually clear what it does, the user
tPath);` should not loose the metadata when the format has
not been changed (at least).
Regards,
Konstantin
2015-04-20 8:37 GMT+04:00 Konstantin Ritt :
> I failed to find an official announcing for the EXIF-based auto-rotation
> of QImage-s (correct me if I'm wrong), so it looks just l
I failed to find an official announcing for the EXIF-based auto-rotation of
QImage-s (correct me if I'm wrong), so it looks just like a behavioral
regression to me, nothing more.
IMO, we should revert the behavior to pre 5.4 and give the control over the
image aspects to the user, not to an arbitra
AFAICT, there is no any more occurrences except in qt_mac_p.h
Same for QColor qcolorForThemeTextColor(ThemeTextColor themeColor), BTW.
Regards,
Konstantin
2015-04-16 21:39 GMT+04:00 René J.V. :
> Hi,
>
> Is the old QFont qfontForThemeFont(ThemeFontID themeID) from Qt 4 still
> used somewhere in
2015-04-08 15:28 GMT+04:00 Eirik Aavitsland <
eirik.aavitsl...@theqtcompany.com>:
>
> Good stuff, and libpng gets updated to 1.6.17 here
> https://codereview.qt-project.org/109973
>
> - Eirik Aa.
>
Someone have to upstream the WinCE and WinRT specific patches to libpng.
Konstantin
>
> On 04/0
> QEventLoop: Cannot be used without QApplication
Says everything.
Show your code.
Regards,
Konstantin
2015-03-30 23:21 GMT+04:00 raven-worx Software :
> Hi,
>
> i get the following print outs to the console and absolutley have no clue
> why:
>
> SHIMVIEW: ShimInfo(Complete)
> QEventLoop: Cann
2015-03-19 18:23 GMT+04:00 Thiago Macieira :
> On Thursday 19 March 2015 15:05:38 Konstantin Ritt wrote:
> > 2015-03-19 8:42 GMT+04:00 Thiago Macieira :
> > > On Thursday 19 March 2015 04:54:09 Konstantin Ritt wrote:
> > > > Hi guys.
> > > >
> >
2015-03-19 8:42 GMT+04:00 Thiago Macieira :
> On Thursday 19 March 2015 04:54:09 Konstantin Ritt wrote:
> > Hi guys.
> >
> > What do you think about moving gif and ico plugins from qtbase
> > to qtimageformats?
>
> Why? What's the reason?
>
Well, we have
[Not really in-topic but still...]
Can we also introduce a flag with meaning like "this change doesn't require
clean build"?
For example, when the approver gives his +2 to a simple change in the .h
file, he can also turn that flag on -- iff all staged changes has this flag
on, then CI does incremen
Hi guys.
What do you think about moving gif and ico plugins from qtbase
to qtimageformats?
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Here is where Sean opens a "3D modelling for dummies" courses :P
Closer to the original topic: there is a SceneLoader that loads a scene
(i.e. obj/dae/blender) and adds the loaded scene elements to the Qt3D
scene, retaining the original relationships (so that all materials assigned
to the mesh wil
Maybe a bit off-topic: can we introduce our own (probably customizable)
memory allocation API, something like Apple's CFAllocator [1], and move Qt
internals to use it instead of malloc/realloc/free (and maybe instead of
some new/delete-s, based on some policies)?
Then we could let the user to deci
How did you configure it? Did you run configure.bat?
Regards,
Konstantin
2015-02-24 10:42 GMT+04:00 Gunnar Roth :
> Hello,
> i am trying to build qt5.5 from git on windows . i do not want to make a
> deveolper build but want to build the code as i normally do.
> After creating the configure.exe,
2015-02-21 22:05 GMT+04:00 Richard Moore :
>
> On 21 February 2015 at 17:34, Konstantin Ritt wrote:
>
>> 2015-02-21 21:30 GMT+04:00 Richard Moore :
>>
>>> Here's an outline of stuff I'd like to see get done in the Qt 5.6 time
>>> frame:
&g
2015-02-21 21:30 GMT+04:00 Richard Moore :
> Here's an outline of stuff I'd like to see get done in the Qt 5.6 time
> frame:
>
> * Complete removal of openssl 0.9.8 support
>
> This has been unsupported for a while and was really only retained since
> it is the only version apple ship on OS X (tho
2015-02-19 9:52 GMT+04:00 Thiago Macieira :
> We might not be able to rely on it being there on all systems, but we could
> provide a configure switch that lets distributors say "yes, I confirm it's
> always there, so don't bundle a copy".
>
> Similarly, we can provide a switch that says "all loca
1 - 100 of 226 matches
Mail list logo
