I see following in call trace:
-webEngineView0x00d92c8381e0 {d_ptr=scoped pointer to a dynamically
allocated object of type "QWebEngineViewPrivate" }QWebEngineView *
-QWidget{data=0x00d941693430 {winid=0 widget_attributes=0
window_flags={i=-2013204480 } ...} }QWidget
+QObject{d_ptr=scope
On segunda-feira, 25 de setembro de 2017 22:44:58 PDT Sudhir Sharma wrote:
> "webEngineView->setUrl(QUrl(QStringLiteral("about:blank")));"
What's the value of webEngineView at this point? Are you sure it's valid?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Op
Hi,
I have compiled 5.9.1 in win 64, and using it in a machine which also has
previous version of QT (4.8) installed.
On starting my application I am getting exception at following line,
"webEngineView->setUrl(QUrl(QStringLiteral("about:blank")));"
Whereas in a fresh machine which only has 5.9.
Thanks very much for the example, Sean. It’s much clearer now that I see
RenderStates in use (for some reason I thought they only applied in Effect)…
There is a pretty serious issue that is blocking me from using Qt3D for
augmented reality, which is that QtMultimedia’s VideoOutput doesn’t work
On Monday, 25 September 2017 03:39:37 PDT iman ahmadvand wrote:
> Hi.
> Nowadays I'm dealing with problem of the symbols absence for some private
> part classes.
> for example in qabstractscrollarea_p.h class
> QAbstractScrollAreaScrollBarContainer
> is not exported while QAbstractScrollAreaPrivate
> Aha, it happens when using a QApplication; the MessageDialog is actually a
> QMessageBox in that case. I can get the same result with the test qml like
> this:
>
> qml -apptype widget messagedialog.qml
>
> (that makes the qml runtime use a QApplication instead of QGuiApplication)
> and maybe w
> On 25 Sep 2017, at 13:17, Murphy, Sean wrote:
>
> And in my real main.cpp I have
> QApplication app(argc, argv);
> QQmlEngine engine;
> QQmlComponent component(&engine, QUrl("qrc:/qml/dashboard.qml"));
> component.create();
> Whereas the project that was generated by Creator when I was tes
> Yes, it should be automatically transient for its parent. For me it works on
> Linux and macOS. So I wonder if we have a bug about this transient-
> parenting in general on Windows. Have you tried any older Qt versions?
Well, the example code you sent me worked correctly on the same version
Hi,
I'd hate to put a dent in your cool, but there's a big fat warning on top
of the private headers - they are private and subject to change without
warning or any promise of compatibility.
___
Interest mailing list
Interest@qt-project.org
http://lists.q
Hi.
Nowadays I'm dealing with problem of the symbols absence for some private
part classes.
for example in qabstractscrollarea_p.h class
QAbstractScrollAreaScrollBarContainer
is not exported while QAbstractScrollAreaPrivate is.
So if you try to access QAbstractScrollAreaPrivate::scrollBarContainers
> On 25 Sep 2017, at 09:28, Daniel d'Andrada wrote:
>
> Hi All,
>
> I wanna have the following (A):
>
> Foo {
>Button {}
> }
>
> or (B):
>
> Item {
>Button {}
>Foo {}
> }
>
> Where "Foo" is an item that is interested only in drag gestures. So when
> one is performed it does its
Hi Filip,
I’m afraid to say “not yet”. We’ve been struggling with getting the
infrastructure in place (with positive updates over the weekend). Currently
there are logistical items to be done (license header updates, etc.), but we
are progressing nicely now.
The aim is to have everything avail
Actually MouseArea.drag.filterChildren is just what I was looking for
(so you can implement option A in pure QML). Sorry for the noise.
- Daniel
On 09/25/2017 09:58 AM, Andrew Ialacci wrote:
I think you can chain the signal calls using signal.connect(otherSignal) and
then set the drag target
I think you can chain the signal calls using signal.connect(otherSignal) and
then set the drag target to null.
I had to implement something like this while writing an MDI windowing system.
Admittedly though I did resort to moving 99% of the geometry manipulation and
event handling to CPP.
I w
Hi All,
I wanna have the following (A):
Foo {
Button {}
}
or (B):
Item {
Button {}
Foo {}
}
Where "Foo" is an item that is interested only in drag gestures. So when
one is performed it does its thing. It ignores clicks, letting them go
to the Button element inside/behind it.
So A
15 matches
Mail list logo