> On 26/05/21 15:09, Lars Knoll wrote:
> > The hope is that we can change that for Qt 6. To make this possible, we
> > have changed not only parts of the public API, but completely redone its
> > internal architecture, especially how multimedia connects to the platform
> > specific backends. Apa
> > If it matters: I disclaim any copyright for the attached
> > files.
>
> Thanks for the snippet. I think this should be perfectly doable. Connect to
> the signal, then map the QVideoFrame and copy out the Y channel.
One ask that may not be captured anywhere: currently, it is impossible to h
> > 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
> > hear this. I previously used this for read-only frames for analysis, i.e.
> > Barcode reading and object detection. How do we do that now?
>
> You can get full access to the video data from a QVideoSink through th
> There are still open issues and gaps in the implementation that need fixing,
> but the code is now in a decent enough shape to merge it back to dev and
> continue on that branch. We will however now have everything ready in Qt
> Multimedia for the 6.2 feature freeze, and will be working with a
My applogies for that. I do remember a time when the ads weren't there. So that's what contributed to my error.
And a sincere thank you!
Sent: Tuesday, May 25, 2021 at 11:11 AM
From: "Riitta-Leena Miettinen"
To: "development@qt-project.org" , "Jaso
>
> I agree with Jason: Doing the "no LTS for FOSS" at the moment of the
> 5.15->6.0 change was really a foul play, imho.
I'm currently attributing it to a license decision that for any
other release (say if there was a 5.16) would be fine, but in reality
was temporally coupled to the release of 6
> Benjamin TERRIER
> > Subject: Re: [Development] Renamed: Running a service for Qt community
> >
> > On Thu, 20 May 2021 at 17:18, Jason H <mailto:jh...@gmx.com> wrote:
> >
> >> Anyway, these issues aren't insurmountable, apparently they can be changed
> >> I would like to get back to doing more of our development discussions out
> >> in the open
> >> (like it should be), but right now IRC is not something I want to go back
> >> to for
> >> that.
> >
> > I also think that having development related discussions in internal Teams
> > channels
>
On Thu, 20 May 2021 at 01:40, Kai Köhne
mailto:kai.koe...@qt.io]> wrote:
>
> > -Original Message-
> > From: Development
> > mailto:development-boun...@qt-project.org]>
> > On Behalf Of Jason H
> > Sent: Wednesday, 19 May 2021 17:26
> > To: g
> So, how many people and entities do we have in the Qt community that have the
> capacity, competence, and credentials to run a service? I personally would
> very much like to see certain aspects of the community at large to be less
> entangled with The Qt Company. The qt-project.org page is a
For mode detail about the situation, I consulted:
https://www.vice.com/en/article/m7ev8y/freenode-open-source-korea-crown-prince-takeover
https://www.kline.sh/
In the past my use of IRC was limited by firewalls. If at all possible,
whatever is moved to, I would request be web-accessable (https).
F
> Can we agree to keep the bashing out of this channel?
You raise important questions. First, what is "bashing", and where is it
appropriate? Or, as I see my behavior, where is being critical of Digia
appropriate?
As a long-time Qt user (first commercial license was for 3.3.3) I've seen it go
> Hi!
>
> On Wed, 19 May 2021 at 12:30, Jason H wrote:
> >
> > Aren't all the kids these days moving to Discord?
>
> Discord is not free software, so it does not align well with a free
> software project.
QtCentre is not free software
forum.qt.io is not free so
Aren't all the kids these days moving to Discord? Slack is inefficient as the
history is rolling unless you pay for more.
I would worry about moving it under Digia (tQtCo), because I'd expect them to
encumber the access to it(paywall, ads, tracking, etc*). I don't trust them.
Perhaps the KDE pe
> Sent: Wednesday, May 12, 2021 at 12:00 PM
> From: "Frank Hemer"
> To: development@qt-project.org
> Subject: Re: [Development] Commercial LTS Qt 5.15.4 released
>
> On Mittwoch, 12. Mai 2021 17:51:51 CEST Thiago Macieira wrote:
> > On Wednesday, 12 May 2021 08:30:52 PDT Frank Hemer wrote:
> > >
I think what Konstantin was getting at was the silliness that you're only doing Commerical LTS releases now.
I hoped that Commericialization of LTS release was a mistake that would not have be repeated.
Sent: Wednesday, May 12, 2021 at 9:33 AM
From: "Tuukka Turunen"
To: "Konstantin Ritt"
C
> Hello,
>
> In QtDeclarative, can a QV4::ReturnedValue or a QV4::Value be converted into
> an ExecutableCompilationUnit?
>
> I'm trying to work on a patch for QJSEngine to allow importing modules from
> C++ (similar to Node.js: import fs from "fs")
> The planned method is something along the
> Sent: Wednesday, March 03, 2021 at 12:44 PM
> From: "Giuseppe D'Angelo via Development"
>
> Il 03/03/21 17:12, Allan Sandfeld Jensen ha scritto:
> > They are only halfway there in C++20, AFAIK it is missing the standard
> > library
> > parts, which means it is not really usable for most peopl
I saw Lars's Qt6 talk on youtube, where he said Qt6 requires C++17. He also
mentioned the new QFuture:: then() function... This is an improvement, but it
makes Qt code look like Javascript in 2015.
In C++20 there are async/await mechanisms. Ideally ask that then() code word be
replacing by 'awa
I'm still trying to wrap my head around this proposal and I'm skeptical that it
can be done at all.
I think there are two occasions where evaluation must be instant. The first is
if your write property handler has any emits in it, and the second is if there
are any other properties that depend
Just thinking outloud, but would it be possible to have a conversion function
that takes a map of lamdas?
Where I am going with this, is that it would be cool to have some serialization
function that looks like:
map.convert(QMap {
{"QByteArray": [](QByteArray const& ba)
{
return QSt
B.
- This will break so many things in a big way. It does not reflect the
reasonable assumption that for reasonable cases you'll get a reasonable
response. I do agree it is the proper loss-less way, but people shoving
extended chars in to byte arrays do so intentionally, even if haphazardly. Fo
:42 AM
> From: "Ville Voutilainen"
> To: "Jason H"
> Cc: "Lars Knoll" , "Qt development mailing list"
>
> Subject: Re: [Development] Qt Multimedia as Add-on in Qt 6
>
> On Fri, 22 May 2020 at 17:19, Jason H wrote:
> > I object, a
Will this have repercussions in the Maintenance tool?
I don't really think that calling Multimedia an "add on" is a reflection of
reality, post 1994.
For mobile kits (iOS, Android) these are essential features. Sorry, Qt just
can't get away with drawing rectangles and text in 2020. I fear this is
https://www.youtube.com/watch?v=cHrrR3KhvUk
Thanks for the insight into what is coming up. I had a minor panic attack
though, which seemed to be shared with the first person to ask a question. If
the property bindings are lazy evaluated, then all my QML code will be broken.
I actively exploit t
> Sent: Monday, April 27, 2020 at 8:05 AM
> From: "Jani Heikkinen"
> To: "development@qt-project.org"
> Subject: [Development] Qt 6.0.0 initial schedule
>
> Hi,
>
> It is time to start freezing Qt 6.0.0 initial schedule. I have had some
> discussion and based on those here is the initial sched
> Sent: Friday, April 24, 2020 at 4:14 PM
> From: "Giuseppe D'Angelo"
> To: "Jason H"
> Cc: development@qt-project.org
> Subject: Re: [Development] Proposal: Deprecate QVector in Qt 6
>
> On 4/24/20 9:03 PM, Jason H wrote:
> >> In fact,
> Sent: Thursday, April 23, 2020 at 12:05 PM
> From: "Giuseppe D'Angelo via Development"
> To: development@qt-project.org
> Subject: Re: [Development] Proposal: Deprecate QVector in Qt 6
>
> On 4/23/20 5:04 PM, Julius Bullinger wrote:
> > Another suggestion: Get rid if the aliases; use the fully
I think this question is better suited to the qt-interest mailing list.
It has been decades since I did Win32 programming, but I would assume that you could ask Windows to find the window for you and give you the HWND. I don't think you can map from process to HWND, you'd have to map HWND to pr
Though I have not tried it, I would suggest Ansible and
https://bugreports.qt.io/browse/QTIFW-166 , notably
https://code.qt.io/cgit/qbs/qbs.git/tree/scripts/install-qt.sh
I use the install script and it was cake. However, I don't know how much longer
this will be supported with the changed Lars
Recently this has caused me much consternation. I think QtQuick everything
should have a parent, and a visual parent, though I appreciate how tedious this
would be. They should be the same except when they can't and having separate
properties would highlight that.
> Sent: Monday, February 03,
Well, I for one do not welcome our new std:: overlords. After many years of
using C++ (since 98) and diving deeper into it, I think Qt and the C++
committee are two completely separate audiences. I cringe at stl code. I once
asked a question on how to reverse something, and what followed was som
I just want to say that the qthttpserver is the most impactful contribution to
Qt for me in along time.
Having a http server in Qt has allowed saved me so much work, provide so many
additional integrations with ease.
* would use again.
Given hoe much positive impact it has had, I would like
/r/ThereWasAnAttempt
> Sent: Tuesday, January 28, 2020 at 12:53 PM
> From: "Giuseppe D'Angelo via Development"
> To: development@qt-project.org
> Subject: [Development] QtPDF did not change license
>
> Il 28/01/20 18:37, Jason H ha scritto:
> > - the p
So I've had a night to think about and react to this.
I want Qt to be successful and make lots of money in addition to taking over
the world. I can appreciate this approach as a way to drive sales. After all,
anything that gets Qt for Mobile more complete is very much appreciated. ;-)
However I
I hope these changes mean that you'll be able to support mobile properly.
I'm still waiting on a response from you about the future of Qt on mobile.
> Sent: Monday, January 27, 2020 at 9:34 AM
> From: "Lars Knoll"
> To: "Qt development mailing list"
> Subject: [Development] Changes to Qt offer
Question: Will this have any overlap/impact on Qt Remote Objects?
https://doc.qt.io/qt-5/qtremoteobjects-index.html
While the docs says it is not RPC, if it's using similar concepts there might
be overlap?
> Sent: Monday, December 16, 2019 at 10:39 AM
> From: "Ulf Hermann"
> To: "development@q
I, for one, welcome our new Norwegian overlord.
> Sent: Monday, December 09, 2019 at 6:33 AM
> From: "Morten Sørvig"
> To: "Qt development mailing list"
> Subject: [Development] Stepping down as Qt for macOS maintainer (but don't
> worry)
>
> Hello all,
>
> I’d like to formally step down as Qt
> - Removing QFTP
> ○ This is about QFTP backend in QNetworkAccessManager
> ○ There are still public users, but how many?
> ○ Proposal: Disable it in 6.0 and check for amount of complaints
> § If limited (as expected) remove in 6
If not _javascript_, then what? Python? This is the first I've heard of this. Just wondering what it is if not _javascript_?
Sent: Monday, November 11, 2019 at 3:10 AM
From: "Dmitriy Purgin"
To: "Qt development mailing list"
Subject: [Development] QML 3 and _javascript_
Hi all,
as
I am trying to get 3D Force Touch (finger pressure) working in my Qt App. I've
been doing a lot of detective work and it almost works. I am going to share
what I know to hopefully figure out what I am missing/what Qt is missing.
There seems to be some support in QTabletEvent
(https://doc.qt.io/
> I think that this discussion is pointless.
I don't think any discussion is pointless. At the very least I learn of others'
opinions, and on occasion, adopt them :-). Even if we don't change we at least
never reached a threshold that we agreed to for change, which, is something.
And not least
> > And it's not "just our style".
>
> LLVM uses the same style for stars and ampersands. Who else?
That's another reason I prefer T *v; because you never see T& v, it's always T
&v;
QRect(const QPoint &topLeft, const QSize &size)
QRect(const QPoint &topLeft, const QPoint &bottomRight)
boolc
You're staring down the business end of a Saturn-V...
I for one, never liked
QObject* x, y;
because x is a pointer, and y is not. It seems like they should both be
QObject*s.
Meanwhile:
QObject *x, y;
makes it very clear (clearer?) that x is a pointer and y is not.
Parenthesizing things shows just
> Also the implicit size of longish texts is usually irrelevant as in most
> situations the layout needs a height-for-width value. IIRC Qt/Quick does
> not even has a concept for how to deal with this type of constraints.
There is fontSizeMode: Text.Fit, .HorizontalFit and .VerticalFit. Horizonta
> I’m all for a more declarative coding style also in C++.
> I’m wondering if we are re-inventing part of Reactive Programing a la
> ReactiveX with QProperty, though?
>
> The above looks similar to (sodium-cxx):
>
> cell_sink surname("John");
> cell_sink lastname("Smith”);
> cell fu
> Sent: Thursday, September 26, 2019 at 11:44 AM
> From: "Simon Hausmann"
> To: "Mitch Curtis"
> Cc: "development@qt-project.org"
> Subject: Re: [Development] Property bindings in Qt 6
>
> Hi,
>
> Yeah, custom setters are required.
>
> One option would be to say that such properties are impl
Bummer that the software stack says GNOME.
https://developer.puri.sm/Librem5/Software_Reference.html#software-reference
If I were Qt (I'm not) I'd look at preparing my own software stack... Who ever got the Nokia N9 (MeeGo) code? I loved that phone!
Sent: Wednesday, September 11, 2019
> > Suggestions:
> > pack, wad (another indirect Doom reference), bale, herd, doss,
> > transfigure (probably too long)
>
> I cannot resist to suggest QTransmogrifier 😊 [1]
> Seriously, QBind is akin to GUI data binding and SQL parameter binding but
> more specialized so I would just pick a more
> My only remaining comment is QBind is rather ambiguous.
> We already have "bind" used as for SQL parameters. Bind is also used for IP
> ports, Boost uses "bind" for connections. "Data binding" is another thing as
> well usually to bind data to UI elements.
>
> Could it be called something else?
My only remaining comment is QBind is rather ambiguous.
We already have "bind" used as for SQL parameters. Bind is also used for IP
ports, Boost uses "bind" for connections. "Data binding" is another thing as
well usually to bind data to UI elements.
Could it be called something else?
___
> > Can Qt set a "no private destructor!" rule?
>
> No.
>
> Private destructors have a purpose.
Would a workable re-wording be "always provide a public means of destruction"?
To be clear, I am not sure what the actual issue is, why it's private, or why
shiboken can't handle it. In the immediate
ical vision for Qt for Python
>
> Hello Jason,
>
> I will comment inline.
>
> On 8/19/19 3:52 PM, Jason H wrote:
> > I tried PySide 2, and was extremely disappointed that not all the classes
> > are supported. What's worse it PyQt supports the classes that are
I tried PySide 2, and was extremely disappointed that not all the classes are
supported. What's worse it PyQt supports the classes that are not supported.
Having that kind of errata is devastating to the confidence in a project.
Qt6/PySide6 must have parity from day 1.
Next, the biggest flaw is
27;s
a miracle that my code works at all.
> Sent: Monday, May 20, 2019 at 7:08 PM
> From: "NIkolai Marchenko"
> To: "Jean-Michaël Celerier"
> Cc: "Jason H" , "Qt development mailing list"
> , "Mutz, Marc"
> Subject: Re: [Devel
> Ok, QList as an alias for QVector takes care of the technical issues I
> have with using inheritance. It doesn't address my concerns regarding
> breaking QList behaviour. What purpose is served to call something QList
> that is in fact a QVector? Please spell it out for me, as I don't see
> it.
My only conern about QList/QVector is a minor one: that the api be more accomodating to cross-language people. push()/append(), size() and length/length().
Now that Qt is thoroughly supporting Python, and JS, and C++ , and implicit conversions, having an API that is normal for any of the language
> 11.04.2019, 04:05, "Richard Weickelt" :
> > On 10.04.2019 23:21, Marco Bubke wrote:
> >> Sounds you want flatpak. ;-)
> >
> > All those run-time extracted application container formats might be nice
> > solutions for GUI applications which is apparently the main target of Qt.
> > But my observat
I whole heartedly disagree. Everything should always be stored in UTC. Not GMT.
Why? Because dates, and particularly times, are not that simple. UTC does not observe Daylight Saving time, but local timezones sometimes do, and those saving time zones do not all kick in at the same time.
I thi
> On 18/03/19 12:11, Pierre-Yves Siret wrote:
> > This can be done with QQmlFileSelector :
> >
> > QQmlApplicationEngine engine;
> > QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine);
> >
> > #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
> > qmlFileSelector->setExtraSe
I, in US/East Coast, am not.
Sent: Friday, March 15, 2019 at 9:51 AM
From: "Pendleton, Corey"
To: "development@qt-project.org"
Subject: [Development] Website Issues
To Whom It May Concern,
I am having https errors accessing both forum.qt.io and wiki.qt.io.
Thanks!
Corey
CONFID
The verbiage in the example is wrong:
code_that_might_through_exceptions();
should be:
code_that_might_throw_exceptions();
Took me a moment to figure out just what it meant.
> Sent: Thursday, March 07, 2019 at 12:09 PM
> From: "Tor Arne Vestbø"
> To: "Volker Hilsheimer"
> Cc: "Qt develop
> Sent: Tuesday, February 12, 2019 at 9:54 AM
> From: "Volker Hilsheimer"
> To: "Jason H"
> Cc: "Vitaly Fanaskov" , "development@qt-project.org"
>
> Subject: Re: [Development] New API design for file system operations
>
>
>
What are the costs of thread start-up?
Why is this not a QRunnable (In my experience Runnables start faster than treads - though it may be anecdotal)
How does it interact with thread pools?
I cringe when I see Promises in 2019. Node/JS uses them because they (until recently) only had one thr
> The question for me is: why would an application (that is not a file
> explorer) want to do any of this? I honestly don’t see the use case.
When I filed the bug against KIO not having a "trash" feature it was because I
was working in digikam (photo library) in KDE - this is MANY years ago (20
> Sent: Tuesday, February 05, 2019 at 11:58 AM
> From: "Thiago Macieira"
> To: development@qt-project.org
> Subject: Re: [Development] Enum classes in signals?
>
> On Tuesday, 5 February 2019 08:43:03 PST Jason H wrote:
> > While I prefer enum classes myself,
While I prefer enum classes myself, I just had to connect to a signal with one
in it. This was unfortunate as I was attempting to use the old connection
syntax SIGNAL()/SLOT() macros. I was not aware that the old syntax were being
deprecated? What is the policy on this?
Should signals not use e
> By all means, let's make sure the internals are efficient for the more
> common languages and scripts; but it's way past time to start doing
> Unicode properly, so that all cultures are well-served by default, when
> the software folk are using is built on Qt,
I don't think anyone knows what "pr
> From: "Arnaud Clère"
> > And I don't want to add QUtf8String until SG16's char8_t gets settled.
> > It'll probably be settled by C++20, which means we can probably work on
> > this during Qt 6 lifetime, possibly even 6.1 or 6.2.
>
> It makes sense to avoid future incompatibilities with the st
> Sent: Monday, January 21, 2019 at 9:51 AM
> From: "Arnaud Clère"
> To: "Allan Sandfeld Jensen" , "development@qt-project.org"
>
> Subject: Re: [Development] Qt6: Adding UTF-8 storage support to QString
>
> > -Original Message-
> > From: Allan Sandfeld Jensen
> >
> > On Dienstag, 15
> Sent: Tuesday, January 15, 2019 at 4:44 PM
> From: "Allan Sandfeld Jensen"
> To: development@qt-project.org
> Subject: Re: [Development] Qt6: Adding UTF-8 storage support to QString
>
> On Dienstag, 15. Januar 2019 19:43:57 CET Cristian Adam wrote:
> > Hi,
> >
> > With every Qt release we see h
27;s a runnable, is
this happening on multiple threads (or cores? - if available) Are there
multiple frames "in flight"?
From: Jason H
Sent: Wednesday, January 9, 2019 4:28:01 PM
To: Val Doroshchuk
Cc: Qt development mail
elping.
Maybe what I need to do is to make the cv::Map a QVariant and store it as
metadata and use QVideoFrame availableMetaData()?
--------
From: Development on behalf of Jason H
Sent: Tuesday, January 8, 2019 6:33:14 PM
To: Jason H
Cc: Qt developmen
or if these are shortcomings in the Qt API?
Sent: Monday, January 07, 2019 at 5:22 PM
From: "Jason H"
To: "Jason H"
Cc: "Pierre-Yves Siret" , "Qt development mailing list"
Subject: Re: [Development] QAbstractVideoFilter, the pipeline and QImage
l, houghLines, toVideoFrame]
Many thanks in advance.
Sent: Monday, January 07, 2019 at 10:57 AM
From: "Jason H"
To: "Jason H"
Cc: "Pierre-Yves Siret" , "Qt development mailing list"
Subject: Re: [Development] QAbstractVideoFilter, the pipeline and QI
::Mat->QImage, QImage->QVideoFrame] where each format step is the (inputFormat -> outputFormat)
Just my 0.02BTC.
Sent: Wednesday, January 02, 2019 at 12:33 PM
From: "Jason H"
To: "Pierre-Yves Siret"
Cc: "Qt development mailing list"
Subject: Re: [Developm
multiple VideoOutputs (and filter pipelines) from the same source
-- Maybe an element for no video output pipeline?
Am wrong in thinking any of that doesn't already exist or is a good idea?
Sent: Saturday, December 22, 2018 at 5:10 AM
From: "Pierre-Yves Siret"
To: &quo
I sent a message on interest@ but no one replied so I'm escalating it here. I
am making a series of filters, but I'm encountering performance issues. I think
it's because of lack of my understanding, or detail in the docs.
The filter pipeline starts with a file or camera device, and various filt
This is probably hijacking your post, but I've always found it bad style to
have different conventions for C++ and QML.
//C++ convention
int Class::memberF()
{
}
//QM convention:, compressed is used:
Rectangle {
onVisibleChanged: {
}
}
I'd like to get everything down to one
It's probably a seperate issue, but incase it's related, the Help in QtCreator an online is also broken:
```
bool QImage::load(const QString &fileName, const char *format = nullptr)
Loads an image from the file with the given fileName. Returns true if the image was successfully loaded; otherwi
I request removal of artemis_poo...@aol.com for spam. Email can be forwarded to
the appropriate party.
Have others gotten a direct reply?
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
First use Qt interest mailing list. Since this is a developer list let's throw this out there:
Next why is an **app** **implementing** a lock screen? It would be far better for Qt to integrate with whatever authentication mechanisms provides. For example:
if (QAuthProvider::mechanisms(QAuthPro
Hello all,
For anyone who is interested, I just wanted to point out that Slashdot has a
poll on the CoC fad:
https://slashdot.org/poll/3103/what-do-you-make-of-programming-languages-and-open-source-organizations-adopting-a-code-of-conduct
___
Develo
getting my approval. I will always
resist an ambiguous judgements on ambiguous standards. The process should be
transparent to those involved in it, such that you should know how it will turn
out before entering into the process. I don't think ambiguity serves anyone
justly.
> Sent: Mo
Lydia,
First, let me say I've stated my support of the KDE CoC. Thank you for your
effort in it.
But then you make a statement in your post script that demonstrates exactly
what I'm talking about. You stated "some emails in this thread sadly make me
see part of the project in a different lig
ject: Re: [Development] QUIP 12: Code of Conduct
>
> On Friday, 26 October 2018 09:48:11 PDT Jason H wrote:
> > My fundamental problem about the Contributor Covenant[1] was initially and
> > solely the fallout from the Linux Kernel fiasco. But then I learned that it
> > was
or Covenant the punishability of the potential harm of people not contributing can escalate to stupid proportions.
I have nothing against KDE's code. It strives to add positivity.
I am very much against Qt's CoC being drafted from Covenant. Covenant is focused on oppression and excluding ppl
archenko"
To: jh...@gmx.com
Cc: "Christian Kandeler" , "Qt development mailing list"
Subject: Re: [Development] QUIP 12: Code of Conduct
Just to clarify: she sought to remove _maintainer_ of the project :) At that point the guy was doing most of the work.
On Fri, Oct
My fundamental problem about the Contributor Covenant[1] was initially and
solely the fallout from the Linux Kernel fiasco. But then I learned that it was
drafted by Coraline Ada Ehmke, who sought to have a contributor removed [2]
from a project preemptively. The contributor did nothing wrong wi
+1 this. I have no problems with the KDE CoC.
> Sent: Thursday, October 25, 2018 at 1:39 PM
> From: "André Pönitz"
> To: "Volker Krause"
> Cc: development@qt-project.org
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> On Thu, Oct 25, 2018 at 09:51:00AM +0200, Volker Krause via Develo
> Sent: Thursday, October 25, 2018 at 11:38 AM
> From: "Volker Hilsheimer"
> To: "Jason H" , "Qt development mailing list"
>
> Cc: "Mitch Curtis"
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> > On 25 Oct 2018, at
> Sent: Thursday, October 25, 2018 at 11:13 AM
> From: "Edward Welbourne"
> To: "Jason H" , "Mitch Curtis"
> Cc: "Qt development mailing list"
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> Jason H (25 October 2018 1
Consolidated reply to multiple threads:
Mitch, you wrote:
> To me it seems like you guys are saying:
>> "I don't care if this person treats me like crap because they sure can code."
> I'm happy for you if you've gotten this far in life and decided that you like
> being insulted in exchange for s
incident, from the list active users at random. Keep choosing until 3 users
have indicated they would participate. That would be the best way to avoid most
of the concerns I questioned about.
> Sent: Wednesday, October 24, 2018 at 1:21 PM
> From: "Edward Welbourne"
> To:
oject to attract controversy. It's an open source project without politics. Well, at least it _was_.
Sent: Wednesday, October 24, 2018 at 12:20 PM
From: "Marco Bubke"
To: "Jason H" , "Ulf Hermann"
Cc: "development@qt-project.org"
Subject: Re: [D
But I did not expect your message to
be the way it was.
> Sent: Wednesday, October 24, 2018 at 11:42 AM
> From: "Aleix Pol"
> To: development
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> On Wed, Oct 24, 2018 at 5:10 PM Jason H wrote:
> >
> > I am wh
Under the Code of Conduct, Can Aleix Pol receive discipline for his/her/their
message?
> Sent: Wednesday, October 24, 2018 at 11:42 AM
> From: "Aleix Pol"
> To: development
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> On Wed, Oct 24, 2018 at 5:10 PM
I am whole-heartedly against a Code of Conduct. While well-intentioned, anyone
following the shit-show that is the Linux kernel code of conduct fiasco, I also
think would be against the code of conduct as well.
Immediately after imposing the Code of Conduct, past tweets by contributors and
the
+1. Make sure that you are accounting for the full font height, see
QFontMetrics::ascent() and descent()
> Sent: Wednesday, October 17, 2018 at 1:23 PM
> From: "Allan Sandfeld Jensen"
> To: development@qt-project.org
> Subject: Re: [Development] Why on Linux using FreeType engine fonts are
> r
A pixel is a pixel, regardless of DPI.
However things matter when you use point sizes (which assumes 72 points per
inch) there are also Screen.devicePixelRatio (
http://doc.qt.io/qt-5/qml-qtquick-window-screen.html#devicePixelRatio-attached-prop
) to contend with. I haven't had to worry about
1 - 100 of 159 matches
Mail list logo