Hi, sorry for just kind of resetting the thread, but we had a quick
discussion with Marc and Tor Arne.
There's an additional constraint that, at least on iOS/macOS, that the
OS/platform callback mechanisms depend on UI libraries (AppKit and
UIKit).
While making that work in QtCore could *maybe*
> QtNetworkauth leaves the QDesktopServices::openUrl() usage/non-usage
> at the user's discretion, and thus that currently won't force a Gui
> dependency.
(Ah shoot. Correcting myself, in the new qtnetworkauth class we do
need to call QDesktopServices::openUrl() too to forward any unhandled
ma 6. toukok. 2024 klo 11.05 Tor Arne Vestbø via Development
(development@qt-project.org) kirjoitti:
>
> There’s some overlap here with the more modern features of intents,
> activities, etc, which we are hoping to add proper APIs for at some point, so
> I suggest not doing any public API
Hi,
I'm collecting thoughts on how to make developing Qt REST /client/
applications a smoother experience.
Here I'm thinking about a "typical" client application that wants to
talk with "typical" REST servers
as they exist today. As it stands today, the main options are
XMLHttpRequest on QML
+1
Leave reviewing to Ivan you don't even have to run tests.
ti 15. kesäk. 2021 klo 14.19 Alex Blasche (alexander.blas...@qt.io) kirjoitti:
>
> Hi,
>
> I'd like to nominate Ivan Solovev as an approver for the Qt Project.
>
> Ivan has been working on various parts of the Qt6 port and has
Hi Gunnar,
But what about the QQml_removeValueTypeProvider: was asked to remove
provider 0x2b4c2ac but it was not found
messages? Don't you get that with 5.4? Did you change something in your patch
for 5.4?
I get this on the 5.3.1 (not on 5.1.1) on my linux, right at the end of test:
PASS
Juha, does that resolve the issues for you? Gunnar Roth, does that fix the
Yes it does, tests pass on 5.3.1. Big thanks Chris and Matt!
Going back to the original issue I'd need reference from 5.1.1 where
tests won't run, I get same issue as Gunnar:
file:///data/item.1.qml:3:1: Item is not a
Hello,
It appears that the QQuickValueTypeProvider instances are continuously
recreated (spinning at 100% and locking the incubator thread, which the main
thread is waiting on). Lars or Simon, are you able to guess what might
cause this issue? The implementation of qmlClearTypeRegistrations
Hello,
apologies for cross-posting. I find this such a fundamental issue that I feel
at least having the best possible understanding of it worth it (if any
exists, which is also
a valuable information in itself). I am happy to help if there is
anything I could check.
thanks,
Juha
---
Hello,
Specialists
On Wed, Nov 26, 2014 at 6:08 PM, Juha Vuolle juvuo...@gmail.com wrote:
Hello,
apologies for cross-posting. I find this such a fundamental issue that I
feel
at least having the best possible understanding of it worth it (if any
exists, which is also
a valuable information in itself). I am
10 matches
Mail list logo
