So, how to fix the above? One could easily fix the API break, but one is
left with broken APIs all over the place. There's no straightforward
deprecation mechanism for QML either, and we've dropped versioned includes.
We haven't actually dropped versioned imports. An unversioned import
just al
On Sun, Dec 18, 2022 at 3:09 PM Thiago Macieira
wrote:
>
> That's bad. But we all know who's to blame here, in both arguments: Apple.
>
> > Try to listen to the people that work with the real, live customers
> > like Nuno and me.
>
> We have. The decision is that we need to make a cut and move on,
Hi,
Between 6.3 and 6.4 there's been an API break in QtQuick's TreeView: its
modelIndex(row,column) function got moved into its base class
(TableView), and the arguments swapped for it, so now it's
TableView::modelIndex(column,row).
This is of course an API break, and needs to be fixed.
On
On Sunday, 18 December 2022 03:25:14 -03 coroberti wrote:
> > What matters to me is that those were the last AVX-incapable CPUs, which
> > allow us to assume that AVX2 is present.
>
> Dear Thiago and Tuukka,
> It seems that you are working under an assumption that if the HW allows it,
> users will
On Sunday, 18 December 2022 03:57:17 -03 Tuukka Turunen via Development wrote:
> Apple's standard license agreement allowes to virtualize two macOS instances
> on macOS.
I didn't know that. Thank you for the information.
That explains much better why cloud and CI providers basically allocate a fu
