You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QBackendProcess, Crimson.QBackend.Connection, and any other artifacts of the QML API from before instantiable types (and connection at import time) don't work anymore, and can't work. The connection still fully supports clients/backends in separate processes; it doesn't care at all.
Those should be removed and cleaned up, and we should figure out other API for QML applications that aren't launched by Go / backend/qmlscene. The QML plugin currently gets connection info from a context property, commandline argument, or environment variable.
One thought is that it's possible to configure/setup the backend from QML as long as that happens before the main Crimson.QBackend import is ever used. That's not too hard with the use of a Loader from the root object..
There should also be better/documented Go-side API for this.
The text was updated successfully, but these errors were encountered:
QBackendProcess
,Crimson.QBackend.Connection
, and any other artifacts of the QML API from before instantiable types (and connection at import time) don't work anymore, and can't work. The connection still fully supports clients/backends in separate processes; it doesn't care at all.Those should be removed and cleaned up, and we should figure out other API for QML applications that aren't launched by Go /
backend/qmlscene
. The QML plugin currently gets connection info from a context property, commandline argument, or environment variable.One thought is that it's possible to configure/setup the backend from QML as long as that happens before the main
Crimson.QBackend
import is ever used. That's not too hard with the use of a Loader from the root object..There should also be better/documented Go-side API for this.
The text was updated successfully, but these errors were encountered: