I have a moderately complex window (more than 50 QWidget- and QLayout-derived
components). I have decided that it would be nice to have two versions: a
vertical layout and a horizontal layout. But it's not just a matter of
QVBoxLayout vs QHBoxLayout.
I have developed a new .ui file with the
When calling QWidget->render() (or the like), is there a way to get it to
render at a different size? I have a widget that I am trying to capture to a
png file, but I let the user decide what dimensions they want it to be saved
at. I can easily make a QPixmap of desired size, but when I call
Hi Giuseppe,
When you say the QML APIs for Qt3D depend on this behaviour, you are
talking about appending to the default property right? Or are the APIs
depending in the fact that every QQmlListProperty has its contents
concatenated (I can't recall an example where this could be used)?
Best
On Wednesday, 14 August 2019 14:36:18 PDT Benjamin TERRIER wrote:
> Le mer. 14 août 2019 à 22:05, Thiago Macieira a
> écrit :
> > On Wednesday, 14 August 2019 12:17:44 PDT Benjamin TERRIER wrote:
> > > The new add-ons modules could be provided as GPLv3 + GPLv2 + LGPLv3.
> >
> > Just a nitpick:
Il 14/08/19 22:05, Thiago Macieira ha scritto:
I don't know if there's anything that is GPL-3.0 (without 2.0). There may be.
Quick, incomplete list, from the back of my head:
* QtVirtualKeyboard
* The WebGL QPA plugin
* The WebAssembly QPA plugin
* QtCharts
are all GPL3 (not 2).
My 2 c,
--
Same here.. Used to be commercial with a previous company.
Couldn’t justify the rates for commercial licenses... And could never justify
the "back license" fee
Scott
-Original Message-
From: Interest On Behalf Of David M. Cotter
Sent: Wednesday, August 14, 2019 1:42 PM
To: John Weeks
Ulf,
I reported the bug here: https://bugreports.qt.io/browse/QTBUG-77529
I will try to propose a fix which has no side effect on Qt3D.
Best regards,
Unai
Le mer. 14 août 2019 à 11:25, Ulf Hermann a écrit :
> Hello,
>
> > If I create a class with a QQmlListProperty and then initialise it
Le mer. 14 août 2019 à 22:05, Thiago Macieira a
écrit :
> On Wednesday, 14 August 2019 12:17:44 PDT Benjamin TERRIER wrote:
> > The new add-ons modules could be provided as GPLv3 + GPLv2 + LGPLv3.
>
> Just a nitpick: there's no need to have GPL-3.0 and LGPL-3.0 at the same
> time.
> So the
i’m in a similar boat. i’m sure there are others who are NOT on this list who
are also in the same boat.
> On Aug 14, 2019, at 1:22 PM, John Weeks wrote:
>
> We are a small company selling a very large and complex application which is
> now based on Qt open source. At the time we first
“This is wrong to say that the only alternative to Commercial + GPLv3 is
Commercial only.”
I did not say the _only_ alternative. Some new things are LGPL exactly to grow
the user base. Qt for Python being one of such.
Yours,
Tuukka
From: Benjamin TERRIER
Date: Wednesday, 14
On Wednesday, 14 August 2019 12:09:02 PDT Roland Hughes wrote:
> If you do not need the latest bells and whistles, drop back to Qt 4.8
No, don't. That is not receiving security fixes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
On Wednesday, 14 August 2019 12:17:44 PDT Benjamin TERRIER wrote:
> The new add-ons modules could be provided as GPLv3 + GPLv2 + LGPLv3.
Just a nitpick: there's no need to have GPL-3.0 and LGPL-3.0 at the same time.
So the combinations are GPL-2.0+LGPL-3.0 and GPL-2.0+GPL-3.0.
I don't know if
On Wed, Aug 14, 2019 at 12:57:27PM -0700, Thiago Macieira wrote:
> On Wednesday, 14 August 2019 12:09:02 PDT Roland Hughes wrote:
> > If you do not need the latest bells and whistles, drop back to Qt 4.8
>
> No, don't. That is not receiving security fixes.
To make this a valid line of reasoning
We are a small company selling a very large and complex application which is
now based on Qt open source. At the time we first considered porting to Qt
(version 4.3?) the license was very expensive for small company (six
programmers) and the evaluation period simply wasn't adequate to deciding
On Wednesday, 14 August 2019 13:18:12 PDT André Pönitz wrote:
> On Wed, Aug 14, 2019 at 12:57:27PM -0700, Thiago Macieira wrote:
> > On Wednesday, 14 August 2019 12:09:02 PDT Roland Hughes wrote:
> > > If you do not need the latest bells and whistles, drop back to Qt 4.8
> >
> > No, don't. That
Hello,
> If I create a class with a QQmlListProperty and then initialise it with
> an array in some QML file, then subclass the QML type in a second QML
> file and try to override the array there, when creating an instance of
> the child class, the list contains the arrays concatenated instead
Hi everyone,
Since we are talking about the future of Qt these days, I would like
to know The Qt Company free software policy with Qt.
Today, most of Qt modules are released under 3 free software licenses:
LGPLv3,
GPLv2 and GPLv3. Some modules are released only under GPLv3.
If my memory is good,
Il 14/08/19 11:23, Ulf Hermann ha scritto:
In the following example, I would expect the list to contain 2 elements
instead of 5. What are your thoughts? Should I fill a bug report and try
to provide a fix?
Yes, that would be nice. Keep in mind that the default property should
still behave the
+1 on this
i am in the process of porting my legacy project to Qt and am afraid that i’ve
made the wrong choice. i’m just one guy and i bet my whole business on the
availability of what i need from Qt under LGPL
i’m already using a third party HTTP server so i’m not affected by this but
Sorry but I'll ask the obvious question: you bet your entire business
without paying for a license?
Have I misunderstood you?
On Wed, 14 Aug. 2019, 7:01 pm David M. Cotter, wrote:
> +1 on this
>
> i am in the process of porting my legacy project to Qt and am afraid that
> i’ve made the wrong
On Wednesday, 14 August 2019 09:18:05 PDT Benjamin TERRIER wrote:
> So I would like that someone could officially confirm if all new modules
> will be
> released under GPLv3 only. Or if it is something that is decided on a per
> module
> basis.
It's decided on a per-module basis, based on the
Ah. In our case, the QLineEdit is inside (and parented by) a widget that
provides the background of the window. That parent widget can accept focus, so
I guess our cases are not quite the same.
> On Aug 14, 2019, at 9:35 AM, Murphy, Sean wrote:
>
>> I used the QLineEdit focusOutEvent()
it’s a labor of love, i make about $2000 per month on it, so about $24k per
year, and that just about covers my expenses and let’s me eat out sometimes. I
occasionally have 2 others help me (3 developers). if i had to pay, it would
cost $16k per year? that makes the business pointless. i’m
> Ah. In our case, the QLineEdit is inside (and parented by) a widget that
> provides the background of the window. That parent widget can accept
> focus, so I guess our cases are not quite the same.
Ok, good! I thought I missed something. In my case, that is a problem since the
user can click
14.08.2019, 21:04, "David M. Cotter" :
>i’m ALLOWED to use the free version, right? or did i misunderstand how LGPL
>works?
You are allowed to use it if you comply with LGPL terms.
In case new modules are licensed as GPL-only and you don't want/can't comply
with GPL,
you won't be allowed to
If you do not need the latest bells and whistles, drop back to Qt 4.8
https://doc.qt.io/archives/qt-4.8/opensourceedition.html
That version is rather prominent in the medical device world, because of
the issues you bring up here.
On 8/14/19 1:36 PM, David M. Cotter wrote:
+1 on this
i am
Not so unusual given the license Roulette which was going on.
On 8/14/19 1:36 PM, interest-requ...@qt-project.org wrote:
Sorry but I'll ask the obvious question: you bet your entire business
without paying for a license?
Have I misunderstood you?
--
Roland Hughes, President
Logikal Solutions
Le mer. 14 août 2019 à 20:36, Tuukka Turunen a
écrit :
>
>
> Hi,
>
>
>
> Qt’s approach to open-source is publicly described, but perhaps a bit
> hidden, check for example:
>
>- Section 3 of https://www.qt.io/faq/
>- https://wiki.qt.io/Qt_Project_Open_Governance
>-
Hi,
Qt’s approach to open-source is publicly described, but perhaps a bit hidden,
check for example:
* Section 3 of https://www.qt.io/faq/
* https://wiki.qt.io/Qt_Project_Open_Governance
* https://www.qt.io/licensing/
We have been releasing new add-on modules under GPLv3 and
I used the QLineEdit focusOutEvent() event.
> On Aug 13, 2019, at 1:21 PM, Murphy, Sean wrote:
>
>> Hmm, about that extra step, to remember the filter stuff, since you already
>> have a custom line edit class, why not embed the MouseFilter class inside it?
>> I mean, the filter does not have
30 matches
Mail list logo
