On Mittwoch, 4. Dezember 2019 12:23:00 CET Lukast dev wrote:
> Hello,
>
> is there some Qt solution for producing traces used for performance
> analysis?
>
> There is on-going work for LTTNG and ETW in Qt I noticed, e.g. here
> https://codereview.qt-project.org/c/qt/qtbase/+/185287. Can that
On 12/5/19, Olivier Goffart wrote:
> That will not be working anymore if the MyType is only worward declared.
> The user will have to do one of these:
> 1. #include "MyType.h" in the header
> 2. Q_DECLARE_OPAQUE_POINTER(MyType *)
> 3. Q_MOC_INCLUDE("MyType.h") : that's not yet implemented
On Thu, Dec 05, 2019 at 06:12:53PM +0100, Giuseppe D'Angelo via Development
wrote:
> Il 04/12/19 12:56, Volker Hilsheimer ha scritto:
> > IIRC, then I added that in the early Qt 2 days, anticipating that with
> > Qt/Embedded we might see our widgets landing on touch screens “any moment
> > now”.
Il 05/12/19 19:10, Uwe Rathmann ha scritto:
You could argue that a good style API allows to increase all sizes by
overloading the virtual methods, but this is very tedious and I doubt,
that you can do everything this way.
Not necessarily; a style could have on itself the "equivalent" of
On 12/5/19 6:12 PM, Giuseppe D'Angelo via Development wrote:
In this light, what's the idea of a global minimum size useful for?
It is/was useful for widget applications running on devices with touch
screens, where the default metrics from the styles are too small.
You could argue that a
Hi Shawn,
FWIW I did try to make that point during the session, since you
weren’t there to do it yourself, that you would like to have
something like a table of QVariants instead of only colors (to
include things like icons and border line widths and radii), and
also that the ColorRole enum
Il 04/12/19 12:56, Volker Hilsheimer ha scritto:
IIRC, then I added that in the early Qt 2 days, anticipating that with
Qt/Embedded we might see our widgets landing on touch screens “any moment now”.
The idea was to have a global setting that ensured that widgets and other
interactables (such
Hi,
Reviving an old thread as I am currently working on QMetaType.
QMetaType is a low level API of Qt, normally a developer shouldn't use it much
in its application, and the goal for Qt6 is that there is even less to know
about it. In short, the goal was to remove the use for
Hi,
Am 05.12.19 um 14:25 schrieb Shawn Rutledge:
So I’m tempted to think that we could try to extend QPalette to store other
data types in addition to colors, but it doesn’t look possible to maintain
existing API or implementation enough to be worthwhile; and it would tend to
become too much
> On 5 Dec 2019, at 09:14, Uwe Rathmann wrote:
>
> Unfortunately the session about styles at the QtCS (
> https://wiki.qt.io/Qt_Contributors_Summit_2019_Program#Future_of_QStyle_for_widgets_and_controls
> ) had been moved to a time slot where I had already left.
>
> One thing I had planned to
Hello,
Part of a infrastructure renewal-process on datacenter there will be a planned
maintenance break during the weekend 6th - 8th December.
This will possibly affect to some services and might cause inoperability. We
will try to minimize downtime and do the changes late on evening / early in
On 12/4/19 4:07 PM, Volker Hilsheimer wrote:
That’s cool! Sadly, many of our widgets (for instance, none of the
item views), and none of our quick controls respect the globalStrut
property.
QApplication is about widgets, while Qt/Quick is usually QGuiApplication
and should be no argument
12 matches
Mail list logo
