Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. FYI QtConncurrent - partially solved - CLOSED

FYI QtConncurrent - partially solved - CLOSED

Scheduled Pinned Locked Moved Unsolved General and Desktop
1 Posts 1 Posters 106 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Anonymous_Banned275
    wrote on last edited by
    #1

    I am posting this to put partial closure on the QtConcurrent issue .
    ( I am still far from implementation of QFutureWatcher )

    I am not trying to be smart ass , but I WAS pretty close resolving the original issue IF I payed attention to the error .

    As far as I am concerned - the issue is in terminology - and at this point i AM NOT interested in discussing it - I need to move on with my code.

    It is up to the group....

    but here is hint

    we have "function with arguments "
    then we have this "assignment "
    int integer = ....
    and then SYMBOL "integer" is passed to ":run"
    and such symbol is called "TYPE" - IN ERROR OUTPUT !!
    ...no more argument ...but type...

    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);

    CLOSED

    It has been a painful education lesson

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved