THANKS!!! That’s what I needed. Yeah, documentation onthis is lacking in the
QCryptHash...
Scott
-Original Message-
From: Marian Beermann [mailto:pub...@enkore.de]
Sent: Thursday, January 18, 2018 4:26 PM
To: Scott Bloom ; interest@qt-project.org
Subject: Re: [Interest] QCryptographicH
QMessageAuthenticationCode should work for you.
Somehow the docs manage to not divulge this, but it is HMAC (iirc).
On 19.01.2018 01:17, Scott Bloom wrote:
> I just realized in working the back end , he was sending hmac-hash from the
> php server... but calling it hash
>
> That’s where the
I just realized in working the back end , he was sending hmac-hash from the php
server... but calling it hash
That’s where the confusion is.
Is QCA coming to core? Or will it always be a "user side build"?
Scott
-Original Message-
From: Marian Beermann [mailto:pub...@enkore.de]
SHA-2 does not take a salt.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Is there a way to set the salt for a sha256 hash?
Scott
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
What is the best way to implement it?
At the moment I have at least these two options:
1. Use normal QML mechanism for dragging (MouseArea's drag) but on x/y
changes of draggable item do Qt.callLater to adjust x/y manually.
2. Implement dragging manually using MouseArea and PathInterpolator
On Wed, 17 Jan 2018 11:59:41 -0800, Thiago Macieira wrote:
> True. Maybe it has never occurred to them that the API would be needed.
> You can help make it happen by adding this API yourself too.
In the case of QSkinny we are not talking about some APIs it is a
fundamentally different philosophy
