On 13 Feb 2020, at 13:53, Maurice Kalinowski
mailto:maurice.kalinow...@qt.io>> wrote:
Hi,
I think moving the implementations into one git repo would be a good move. In
that case you could also move the qml state machine bindings from qtdeclarative
(See src/imports folder).
I don’t think mer
Hi,
I think moving the implementations into one git repo would be a good move. In
that case you could also move the qml state machine bindings from qtdeclarative
(See src/imports folder).
I don’t think merging the implementations is a good idea, I find they serve
different purposes. Just my t
Hi,
I think moving the implementations into one git repo would be a good move. In
that case you could also move the qml state machine bindings from qtdeclarative
(See src/imports folder).
I don’t think merging the implementations is a good idea, I find they serve
different purposes. Just my tw
: [Development] Migrate QStateMachine from Qt Core
What has lead to considering that they could eventually be removed ?
Couldn't they be split off in a separate library put in the marketplace or
github for instance if they're a thorn ?
No reason to throw away code that works, is there ?
O
What has lead to considering that they could eventually be removed ?
Couldn't they be split off in a separate library put in the marketplace or
github for instance if they're a thorn ?
No reason to throw away code that works, is there ?
On Thu, Feb 13, 2020 at 10:58 AM Karsten Heimrich
wrote:
Hi,
we would like to remove the QStatemachine API's from Qt Core. We identified 2
options to do this:
* Move into QtScXML and keep both the implementation
* rename the module to reflect that it contains 2 different state machine
implementations
* Move into Qt5Compat
* in the long
