QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior

[JonB]

@Christian-Ehrlicher said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

he decoding starts from the back.

I sit and stare at

    hexstring = textStream.readLine();
    ba.append(QByteArray::fromHex(hexstring.toUtf8()));

and just cannot see that!? :(

Though anyway of course it doesn't matter, he needs to fix the character count.

[Christian Ehrlicher]

@JonB said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

and just cannot see that!? :(

Forgot a Tat the start :D

[KroMignon]

@JonB said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

I sit and stare at
hexstring = textStream.readLine();
ba.append(QByteArray::fromHex(hexstring.toUtf8()));

and just cannot see that!? :(

when reading from stream, you got an QByteArray.
You have to transform it to QString to be able to use QByteArray::fromHex().

I would to it with hexstring.toLatin1() but it doesn't really matter, because there are only '0'-'9' or 'A'-'F' or 'a'-'f' bytes.

[Christian Ehrlicher]

@KroMignon said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

when reading from stream

I wouldn't use QTextStream at all but QIODevice::readLine() to avoid the two useless conversions completely :)

[oldevel]

Wow, many thanks for your reply's and suggestions. I will provide further observations shortly.

[JonB]

@KroMignon , @Christian-Ehrlicher
Sorry, I just don't see what either of you are saying. Nothing to do with QByteArray versus QString. I simply don't understand where @Christian-Ehrlicher said:

[T]he decoding starts from the back.

as an answer to why the OP says the first byte he gets, which he & I expect to be the 7F at the left-hand side of the string, comes out as 0x07 [and the second character is 0xF4]

With an odd number of characters in the string, I would have expected the first byte to be 7F and it to go wrong at the right-hand end of the string.

Since you two seem to understand and I do not, we can leave this if you wish...

[KroMignon]

@JonB said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

Since you two seem to understand and I do not, we can leave this if you wish...

If you take a look at QByteArray::fromHex() source code, you will see that the string if read backwards.
This is why he got this.

[Christian Ehrlicher]

@JonB said in QByteArray::fromHex(QString.toUtf8()) presenting undesired behavior:

I simply don't understand where @Christian-Ehrlicher said:

Hehe.
It was the only meaningful explanation for the described problem and when you look at the code (hey, it's opensource ;)) you see that it's the correct one.

[JonB]

@KroMignon , @Christian-Ehrlicher

If you take a look at QByteArray::fromHex() source code, you will see that the string if read backwards.

Indeed, that makes sense for behaviour reported, I merely expressed my surprise as it was not the direction I expected. I expected it would naturally work left-to-right, that's all!

So with a missing byte at the end the code does not allow decoding of all the bytes up to the last one, so you can mostly see what is in there, instead it makes them all wrong if, say, the input is prematurely curtailed, for whatever reason. Potentially a shame/confusing. That's all. I agree the

the documentation is explicit: Input is not checked for validity

means it can do what it likes with this bad input, as I say I was merely surprised that it does turn out to do right-to-left.....

[oldevel]

I gained insight from all your posts. It turns out that simply correcting the line length sorted the problem, thank you.