Il 28/05/20 16:18, Matthew Woehlke ha scritto:
While that may be true, changing it now is going to break*every* user
that uses these methods to generate compound transformations... and
it'll be a silent break. I would be*very* surprised if that doesn't
generate more bug reports.
I 100%
On 27/05/2020 11.09, Giuseppe D'Angelo via Development wrote:
Sure, augmenting the docs would help. But the whole
point of the API is for its usage to be straightforward. If you do
QTransform t;
t.translate();
t.rotate();
t.scale();
auto result = t.map(foo);
the "obvious" meaning should be
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
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*.
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
On Tuesday, 26 May 2020 10:33:21 PDT Edward Welbourne wrote:
> While I'm a linear algebraist ... and aware that the orthodoxy of
> graphics programming does things "a bit differently" than linear
> algebraists do, but allegedly for good reasons (that I might one day
> learn). It's just the same
On 26/05/2020 13.33, Edward Welbourne wrote:
It turns out that either way round works
fine, as long as you're consistent. Which QTransform appears to be; and
its docs correctly describe it the way it is.
They are? It was *not at all* clear to me in what order the transforms
would be applied.
On Tuesday, 26 May 2020 09:17:05 PDT Edward Welbourne wrote:
>> (Matrix multiplication isn't commutative.)
Thiago Macieira (26 May 2020 18:42)
> This more or less summarises all I remember from matrix classes from high
> school.
While I'm a linear algebraist ... and aware that the orthodoxy of
On Tuesday, 26 May 2020 09:17:05 PDT Edward Welbourne wrote:
> (Matrix multiplication isn't commutative.)
This more or less summarises all I remember from matrix classes from high
school.
> I'll try to work out whether QMatrix / QTransform are consistent about it
Thanks, Eddy.
--
Thiago
Thiago Macieira (26 May 2020 18:06) wrote:
> Neither QMatrix nor QTransform have seen any change since the Qt 5.0
> repository import that was related to the underlying math. Only licensing
> and C++ updates.
>
> The task https://bugreports.qt.io/browse/QTBUG-84441 is claiming there's
> some wrong
On 26/05/2020 12.06, Thiago Macieira wrote:
On Tuesday, 26 May 2020 08:59:09 PDT Thiago Macieira wrote:
Neither QMatrix nor QTransform have seen any change since the Qt 5.0
repository import that was related to the underlying math. Only licensing
and C++ updates.
The task
On Tuesday, 26 May 2020 08:59:09 PDT Thiago Macieira wrote:
> Neither QMatrix nor QTransform have seen any change since the Qt 5.0
> repository import that was related to the underlying math. Only licensing
> and C++ updates.
>
> The task https://bugreports.qt.io/browse/QTBUG-84457 is claiming
14 matches
Mail list logo
