> We have that, in that you can mark a reply as finished immediately and
> then it will continue to load it synchronously. But that's still
> taking a slightly slower path and counts as a remote resource (which
> restricts the behavior slightly, such as requiring qmldir files and
> restricting plug
> It used to be that the QQmlEngine docs said to set a custom
> QNetworkAccessmanager for intercepting file access, but this had three
> important drawbacks
> 1) You have to use a custom URL everywhere
> 2) You take the slow path when you don't actually need to
>
Is there any plan for allowing the
On quinta-feira, 25 de julho de 2013 12:25:13, Alberto Mardegan wrote:
> On 07/24/2013 06:47 PM, Alan Alpert wrote:
> > Discussed at Qt CS as the mechanism for both file selectors and
> > providing import control was a new QQmlAbstractUrlInterceptor class.
> > You can provide a subclass of this to
On quinta-feira, 25 de julho de 2013 09:36:33, Bubke Marco wrote:
> Hi
>
> There are now many new feature proposals popping up on the mailing list.
> Sometime there is a link to a wiki page, JIRA etc.. You can easily get
> lost. The result are more hard designable (we working on the qml designer)
On quinta-feira, 25 de julho de 2013 09:17:36, André Somers wrote:
> static inline bool qFuzzyComparePossibleNulls(double p1, double p2)
> {
> if (qFuzzyIsNull(p1)) {
> return qFuzzyIsNull(p2);
> } else if (qFuzzyIsNull(p2)) {
> return false;
> } else {
> r
Instead of qFuzzyCompareMightBeNull, why can't we have a function that returns
the number of representable numbers between two floats?
boost has a similar function, math::float_distance(a, b)
Qt style API could then be something like:
unsigned qFloatDistance(float a, float b);
You can then comp
Hi
There are now many new feature proposals popping up on the mailing list.
Sometime there is a link to a wiki page, JIRA etc.. You can easily get lost.
The result are more hard designable (we working on the qml designer) features
and Qml has more than enough already. So I propose something li
On Thu, Jul 25, 2013 at 6:34 AM, André Somers wrote:
> Would it be an option to _add_ a qFuzzyCompareMightBeNull or something
> like that then for cases like Juan describes where you don't know if one
> of the two values might be zero or not? There is no reason to change the
> behaviour of the cur
On quinta-feira, 25 de julho de 2013 07:34:19, André Somers wrote:
> Would it be an option to _add_ a qFuzzyCompareMightBeNull or something
> like that then for cases like Juan describes where you don't know if one
> of the two values might be zero or not? There is no reason to change the
> behavio
