|I appreciate confirmation of the parameters # limit .
I do not see why QT limitation of one process would be a reason to switch OS, especially when
using std::bind "fixes " this limitation.
I have SUCCESSFULLY codded and run several test function using QTConcurrent,
and I am basically back where I started.
I could use some more assistance with this.
The attached code is direct from QT documentation.
What I do not understand is the necessity of highlighted code.
What is the purpose and is there a doc I could RTFM to get some
understanding why this code is necessary.
If I pass the aFunctionWithArguments function arguments at face value I then get
the "type" error ( as posted previously )
Is this something "just QT " or is that "normal" C++
and if so what is the correct terminology of doing this ?
I just call it "SYMBOLS".
My real code gets complicated because I am a passing more the 5 "arguments" and two of them are
pointer and double pointer.
I can run my test function passing struct and have no need for these "SYMBOLS".
I am NOT asking to write my code, I am asking for explanation why
QT is using these "conversions / symbols "
extern void aFunctionWithArguments(int arg1, double arg2, const QString &string);
int integer = ...;
double floatingPoint = ...;
QString string = ...;
QFuture<void> future = QtConcurrent::run(aFunctionWithArguments, integer, floatingPoint, string);