Re: [Interest] Qt 5.13 Beta 2 ?
Hi Jani, thx for the info ekke Am 16.04.19 um 07:34 schrieb Jani Heikkinen: > Hi, > > We are targeting to get the beta2 out as soon as possible. All blockers are > fixed but we have some issues with creating all packages. Let's see if we > managed to get the beta2 out already today or then later this week > > br, > Jani > > > From: Interest on behalf of Thiago Macieira > > Sent: Monday, April 15, 2019 8:47 PM > To: interest@qt-project.org > Subject: Re: [Interest] Qt 5.13 Beta 2 ? > > On Monday, 15 April 2019 01:39:29 PDT ekke wrote: >> Hi, >> >> any ideas when Qt 5.13 Beta 2 will come out ? >> >> was scheduled for 2019-04-02 >> >> I'm waiting to test BLE on Windows: >> https://bugreports.qt.io/browse/QTBUG-74394 > From last week's release team minutes: > > Qt 5.13 status: > - Unfortunately no beta2 packages yet, couple of issues still without a fix in > blocker list (https://bugreports.qt.io/issues/?filter=20729) >* Fixes are available but not in yet > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel System Software Products > > > > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.13 Beta 2 ?
Hi, We are targeting to get the beta2 out as soon as possible. All blockers are fixed but we have some issues with creating all packages. Let's see if we managed to get the beta2 out already today or then later this week br, Jani From: Interest on behalf of Thiago Macieira Sent: Monday, April 15, 2019 8:47 PM To: interest@qt-project.org Subject: Re: [Interest] Qt 5.13 Beta 2 ? On Monday, 15 April 2019 01:39:29 PDT ekke wrote: > Hi, > > any ideas when Qt 5.13 Beta 2 will come out ? > > was scheduled for 2019-04-02 > > I'm waiting to test BLE on Windows: > https://bugreports.qt.io/browse/QTBUG-74394 From last week's release team minutes: Qt 5.13 status: - Unfortunately no beta2 packages yet, couple of issues still without a fix in blocker list (https://bugreports.qt.io/issues/?filter=20729) * Fixes are available but not in yet -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Creating C++ objects in JavaScript with operator new
You can expose the C++ object to metatype, then register the MetaObject using
qmlRegisterType<>() to the Qml types. You then should create a Component and
instanciate the component into an actual object:
I strongly suggest you read this:
https://doc.qt.io/qt-5/qtqml-javascript-dynamicobjectcreation.html
property Component myComponent: MyClass
{
property bool allComponentValue: otherIdBinding.visible
}
function doSomething()
{
var myobject = allComponentValue. createObject(myparent, {});
}
The QObject, need the parent and initial property (you can create binding using
Qt.binding(function(){ return OtherBindingId.value; })
This should cover how to create object. You will need to destroy the object by
either the parent or by destroying it manually.
You can also generate an object from Qml code directly:
Qt.createQmlObject()
The new is lacking too much information to create the QObject properly.
-Original Message-
From: Interest On Behalf Of Richard Weickelt
Sent: April 15, 2019 4:10 PM
To: interest@qt-project.org
Subject: [Interest] Creating C++ objects in JavaScript with operator new
Hi,
is there an easy way to register a QObject-derived class in the QML type system
so that I can instantiate it from within JavaScript code using operator new?
function someJavaScriptFunction(){
var myObject = new MyClass("blabla");
// ...
}
Right now I am registering another class as a proxy which then registers the
constructor function for my class. This looks overly verbose and clunky. Is
there a simpler way?
class MyClass : public QObject
{
Q_OBJECT
public:
MyClass(QObject* parent = nullptr, const QString& someParam = "");
Q_INVOKABLE bool someMethod() const;
static void registerAsJSType(QJSEngine* engine); };
class MyClassCreator : public QObject
{
Q_OBJECT
public:
Q_INVOKABLE MyClass* createObject(const QVariantMap& arguments); };
void MyClass::registerAsJSType(QJSEngine* engine) {
QJSValue creator = engine->newQObject(new MyClassCreator());
engine->globalObject().setProperty("_MyClassCreator", creator);
engine->evaluate("function MyClass(param) { return
_MyClassCreator.createObject({ someParam: param }); }"); }
MyClass* MyClassCreator::createObject(const QVariantMap& arguments) {
QString someParam = arguments.value("someParam").toString();
return new MyClass(qmlEngine(this), someParam); }
Thanks
Richard
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
[Interest] Creating C++ objects in JavaScript with operator new
Hi,
is there an easy way to register a QObject-derived class in the QML type
system so that I can instantiate it from within JavaScript code using
operator new?
function someJavaScriptFunction(){
var myObject = new MyClass("blabla");
// ...
}
Right now I am registering another class as a proxy which then registers the
constructor function for my class. This looks overly verbose and clunky. Is
there a simpler way?
class MyClass : public QObject
{
Q_OBJECT
public:
MyClass(QObject* parent = nullptr, const QString& someParam = "");
Q_INVOKABLE bool someMethod() const;
static void registerAsJSType(QJSEngine* engine);
};
class MyClassCreator : public QObject
{
Q_OBJECT
public:
Q_INVOKABLE MyClass* createObject(const QVariantMap& arguments);
};
void MyClass::registerAsJSType(QJSEngine* engine)
{
QJSValue creator = engine->newQObject(new MyClassCreator());
engine->globalObject().setProperty("_MyClassCreator", creator);
engine->evaluate("function MyClass(param) { return
_MyClassCreator.createObject({ someParam: param }); }");
}
MyClass* MyClassCreator::createObject(const QVariantMap& arguments)
{
QString someParam = arguments.value("someParam").toString();
return new MyClass(qmlEngine(this), someParam);
}
Thanks
Richard
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt + Android + OpenSSL
15.04.2019, 21:16, "Nuno Santos" : > Hi, > > I’m trying to use SSL websocket on a Qt 5.12 Android app. > > When I run the app it is complaining about the missing functions. > > W qt.network.ssl: QSslSocket: cannot resolve DTLSv1_2_server_method > W qt.network.ssl: QSslSocket: cannot resolve DTLSv1_2_client_method > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_new > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_free > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_set_ssl_ctx > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_set_flags > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_finish > W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_cmd > W qt.network.ssl: QSslSocket: cannot resolve SSL_set_alpn_protos > W qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_alpn_select_cb > W qt.network.ssl: QSslSocket: cannot resolve SSL_get0_alpn_selected > W qt.network.ssl: QSslSocket: cannot resolve DTLS_server_method > W qt.network.ssl: QSslSocket: cannot resolve DTLS_client_method > W qt.network.ssl: QSslSocket: cannot call unresolved function > DTLS_client_method Note that these warning messages don't necessary mean a problem for you. For examples, if your application doesn't use DTLS or HTTP/2 protocol negotiation you can ignore DTLS and ALPN warnings. > I’m providing OpenSSL 1.0.1s as an ANDROID_EXTRA_LIBS param. > > Does anybody know if the problem here is the fact that OpenSSL is too old? > > Thanks in advance! > > Regards, > > Nuno > , > > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest -- Regards, Konstantin ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt + Android + OpenSSL
Thiago, Thanks for your insights. I usually tend to postpone this updates because of the time I need to invest in rebuilding the libs. I always end up stumbling in some weird building problem… Does anyone knows what’s the quickest way of building OpenSSL for Android? Best, Nuno > On 15 Apr 2019, at 19:30, Thiago Macieira wrote: > > On Monday, 15 April 2019 11:12:44 PDT Nuno Santos wrote: >> I’m providing OpenSSL 1.0.1s as an ANDROID_EXTRA_LIBS param. >> >> Does anybody know if the problem here is the fact that OpenSSL is too old? > > Yes, the problem is OpenSSL's age. Yours is apparently too old to support > DTLS > 1.2 (and apparently DTLS at all). > > In any case, for OpenSSL, *ANY* version except the very latest[*] is too old. > Upgrade now. And next month. And the one after that. Ad aeternam. > > [*] latest of 1.0.x or of 1.1.x, since 1.0.x is still supported until Dec 31 > of this year. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel System Software Products > > > > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt + Android + OpenSSL
On Monday, 15 April 2019 11:12:44 PDT Nuno Santos wrote: > I’m providing OpenSSL 1.0.1s as an ANDROID_EXTRA_LIBS param. > > Does anybody know if the problem here is the fact that OpenSSL is too old? Yes, the problem is OpenSSL's age. Yours is apparently too old to support DTLS 1.2 (and apparently DTLS at all). In any case, for OpenSSL, *ANY* version except the very latest[*] is too old. Upgrade now. And next month. And the one after that. Ad aeternam. [*] latest of 1.0.x or of 1.1.x, since 1.0.x is still supported until Dec 31 of this year. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] Qt + Android + OpenSSL
Hi, I’m trying to use SSL websocket on a Qt 5.12 Android app. When I run the app it is complaining about the missing functions. W qt.network.ssl: QSslSocket: cannot resolve DTLSv1_2_server_method W qt.network.ssl: QSslSocket: cannot resolve DTLSv1_2_client_method W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_new W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_free W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_set_ssl_ctx W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_set_flags W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_CTX_finish W qt.network.ssl: QSslSocket: cannot resolve SSL_CONF_cmd W qt.network.ssl: QSslSocket: cannot resolve SSL_set_alpn_protos W qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_set_alpn_select_cb W qt.network.ssl: QSslSocket: cannot resolve SSL_get0_alpn_selected W qt.network.ssl: QSslSocket: cannot resolve DTLS_server_method W qt.network.ssl: QSslSocket: cannot resolve DTLS_client_method W qt.network.ssl: QSslSocket: cannot call unresolved function DTLS_client_method I’m providing OpenSSL 1.0.1s as an ANDROID_EXTRA_LIBS param. Does anybody know if the problem here is the fact that OpenSSL is too old? Thanks in advance! Regards, Nuno___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Qt 5.13 Beta 2 ?
On Monday, 15 April 2019 01:39:29 PDT ekke wrote: > Hi, > > any ideas when Qt 5.13 Beta 2 will come out ? > > was scheduled for 2019-04-02 > > I'm waiting to test BLE on Windows: > https://bugreports.qt.io/browse/QTBUG-74394 From last week's release team minutes: Qt 5.13 status: - Unfortunately no beta2 packages yet, couple of issues still without a fix in blocker list (https://bugreports.qt.io/issues/?filter=20729) * Fixes are available but not in yet -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] How to hide the QSGGeometryNode?
Hi,
Il 15/04/19 13:11, Denis Shienkov ha scritto:
Yes, now I use this in a form of:
boolCurveNode::isSubtreeBlocked()const
{
returnQSGGeometryNode::isSubtreeBlocked()||!m_visible;
}
voidCurveNode::setVisible(boolvisible)
{
if(m_visible==visible)
return;
m_visible=visible;
if(!m_visible)
m_dirtyState|=DirtySubtreeBlocked;
else
m_dirtyState|=DirtyOpacity;
}
Please make a minimal testcase. The code above seems incomplete (e.g. no
calls to markDirty to update those dirty bits).
HTH,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] How to hide the QSGGeometryNode?
> Did you try already to use isSubTreeBlocked?
Hi. Yes, now I use this in a form of:
bool CurveNode::isSubtreeBlocked() const
{
return QSGGeometryNode::isSubtreeBlocked() || !m_visible;
}
void CurveNode::setVisible(bool visible)
{if (m_visible == visible)return;m_visible = visible;
if (!m_visible)m_dirtyState |= DirtySubtreeBlocked;else
m_dirtyState |= DirtyOpacity;
}
but, when I call the setVisible(true) infide of updatePaintNode(), then I
got an assert:
ASSERT: "shadowNode" in file scenegraph\coreapi\qsgbatchrenderer.cpp, line
1293
and, the node does not appeared again as a visible.
пт, 12 апр. 2019 г. в 12:09, Giuseppe D'Angelo via Interest <
interest@qt-project.org>:
> Hello,
>
> Il 12/04/19 09:19, Denis Shienkov ha scritto:
> > I have an own class, derived from the QQuIckItem. This class contains a
> > multiple child QSGGeometryNode-s. Each node has own fragment && vertex
> > shader. Each node draws a curves, which are specified by a points set to
> > a vertex array. So, I need possibility to hide any selected
> > QSGGeometryNode (i.e. do not draw it).
> >
> > How to do it in a right way?
>
> Did you try already to use isSubTreeBlocked?
>
> HTH,
> --
> Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
> KDAB - The Qt, C++ and OpenGL Experts
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
[Interest] Qt 5.13 Beta 2 ?
Hi, any ideas when Qt 5.13 Beta 2 will come out ? was scheduled for 2019-04-02 I'm waiting to test BLE on Windows: https://bugreports.qt.io/browse/QTBUG-74394 thx for infos ekke ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
