@StudentScripter Yes, you can do that. And it shows you how they implemented stuff.

@JonB said in converting from float or double to QString results in output being 0:

Warning: The QString content may only contain valid numerical characters which includes the plus/minus sign, the character e used in scientific notation, and the decimal point. Including the unit or additional characters leads to a conversion error.

In which case RTFM is the rule of the day! but I'm lazy.

@UvQtcYZJuD7J5VW7 said in QByteArray to LabVIEW Byte Array conversion:

I need to include Labview extcode.h

Yes, that's right.

and when I include it, I get errors about my compiler (platdefines.h doens't recognize my compiler when I'm in Qt Creator).

Then you just need to address the error.

If you use MSVC, it will work fine out-of-the-box.

If you want to use MinGW, you can modify platdefines.h and add these 2 lines to define your compiler:

... #elif defined(__GNUC__) // <-- Add this #define Compiler kGCC // <-- Add this #else #error "We don't know the Compiler" #endif

@TomHoe said in Int16 to QByteArray:

didn't knew that '!' is the same as 0x21..

See http://www.ascii-code.com/

'!' == 33 == 0x21 == 0b00100001

@TomHoe said in Int16 to QByteArray:

Is there a way to rewrite it to regular hex codes ? Or does every controller understand this notation ?

Again, '!' == 33 == 0x21 == 0b00100001

Those are different ways of displaying the same bytes. The controller does not see any "hex" or "notation"; it only sees the sequence of 0's and 1's.

I recommend you learn about how bits/bytes are stored in computer memory: http://statmath.wu.ac.at/courses/data-analysis/itdtHTML/node55.html

@Dan90 You are assigning a value to a pointer, but data is actually an array of "unsigned char":

unsigned char *data = 0b10000000;

Instead you should do (C++11):

unsigned char data[] = { (unsigned char)0b10000000 };

Thanks, that should do it!

@JKSH Copy that. Thanks a lot for your kind help.

Thank you very much :-)

You gave me the right hint.

There was a cast before which I did not see.
And since everything was casted to int MySQL deleted the Zeros after the '.'

Now everything works fine and thanks for the other variation :-)

@mcosta Hi,

I'll certainly take a look at it. So I guess it's not only changing the font xD

Thank you.