> On 27 May 2020, at 17:22, Riitta-Leena Miettinen
> wrote:
>
> Hello,
>
> How about using a similar approach to that used for documenting the CMake
> commands for each module in Qt 5.15?
>
> That is:
>
> • Create a qdoc file in each module that contains the breakages for
> that
On Wednesday, 27 May 2020 03:42:19 PDT Oswald Buddenhagen wrote:
> > this is not something we can subject our users to.
>
> orly? kde had been doing that for quite a while.
And I fixed QtCore to do the same.
The only reason not to include the moc output in your .cpp is if you don't
have one (a
Hello,
How about using a similar approach to that used for documenting the CMake
commands for each module in Qt 5.15?
That is:
* Create a qdoc file in each module that contains the breakages for that
module and contains the \ingroup command migrate2qt6, or something like that.
*
On 5/27/20 3:58 PM, Matthew Woehlke wrote:
*Nothing* there clearly states, at least to my reading, whether the
"new" transform happens*before* or*after* any existing transforms that
the QTransform is already doing.
IMO, changing this to clarify that would help significantly.
Sure,
Hi,
I think the documentation is actually clear on the order by the scale()
example. I'm not sure whether we should at explicitly the concept of
intrinsic transform:
https://en.wikipedia.org/wiki/Euler_angles#Definition_by_intrinsic_rotations
The current QTransform documentation always states
Hi,
We should start documenting the API changes that Qt 6.0 brings soon. This will
allow getting people getting an overview, help early adopters, and will give us
time to improve the documentation before the release.
Now I see that there are different paths taken:
- Eskil and others have
Matthew Woehlke (26 May 2020 18:15) wrote:
>>> The documentation is not clear if the scale, rotate, etc. methods of
>>> QTransform apply *before* or *after* whatever the QTransform is already
>>> doing. The bug report indicates that they are applied *first*.
>>>
>>> Given the potential for
On 27/05/2020 04.34, Edward Welbourne wrote:
Matthew Woehlke (26 May 2020 18:15) wrote:
The documentation is not clear if the scale, rotate, etc. methods of
QTransform apply *before* or *after* whatever the QTransform is already
doing. The bug report indicates that they are applied *first*.
Hello everyone,
I'm really happy to announce that Qt for Python 5.15.0 is finally out :)
At the same time, due to all the changes we did in 5.14.2
we decided to do another release after all the feedback we got
with 5.14.2.1, so that means that 5.14.2.2 is also out :D
You can check the
On Wed, May 27, 2020 at 08:21:48AM +, Fabian Kosmale wrote:
the only way to get this to work is to include the moc file in the
same cpp file. While doing this inside of Qt is possible,
this is not something we can subject our users to.
orly? kde had been doing that for quite a while.
Matthew Woehlke (26 May 2020 18:15)
> The documentation is not clear if the scale, rotate, etc. methods of
> QTransform apply *before* or *after* whatever the QTransform is already
> doing. The bug report indicates that they are applied *first*.
>
> Given the potential for breaking existing code
The task:
Currently, when using QMetaMethod::parameterType, we end up doing a costly
string comparison.
In order to get rid of the property cache in QML, we need faster way to obtain
the metatype of
method parameters and return types. This also has some benefits outside of QML,
as it should
12 matches
Mail list logo
