Skip to content
  • 143k Topics
    719k Posts
    E
    @JonB the link to python comes from the here string syntax: the string start just after the triple quote and not at the next line. In others language like perl, the here string start at the next line to preserve the first line indent. C++ 11 introduced a here string like construction and, again, the raw string start at the next line. So this error is in part due to the language syntax for here string.
  • Jobs, project showcases, announcements - anything that isn't directly development
    4k 23k
    4k Topics
    23k Posts
    V
    Everyone who is trying to cross-compile Qt for Orange Pi 3B can follow this tutorial: https://github.com/vverenich/CrossCompileQtForOpi
  • Everything related to designing and design tools

    129 391
    129 Topics
    391 Posts
    J
    In QT Design Studio, Tab Buttons are mostly for navigation within the UI, but each tab doesn’t automatically hide other content. Usually, a StackView or Loader is needed to switch visible content depending on the active tab.
  • Everything related to the QA Tools

    83 223
    83 Topics
    223 Posts
    Z
    @JonB Thank you!
  • Everything related to learning Qt.

    389 2k
    389 Topics
    2k Posts
    Lehomar2vinciL
    Hi there, I'm also looking for teammates (here lonely) if I can help about creative ideas, I'll be proud to be with you (GMT +1, Paris Timezone) Dont be shy and feel free to DM me :) (Having the same name on Discord)
  • 2k Topics
    13k Posts
    JonBJ
    @J.Hilk said in Conditional operator as a statement: is totally legit. Only because int is "promotable" to double. They do not have to the same return type but they at least have to have promotable/convertible return types. The (academic) question is whether that is enforced by the ? : operator itself or whether it is only enforced on (say) assignment of the result to a variable or usage in a condition. The situation we are discussing is the (peculiar): a ? b() : c(); as a statement, so the result is never used. I still imagine it's the : operator which demands the type compatibility even if the result is not used. BTW (I just discovered) the "Standard" says something along these lines: 5.17/3 If the second and third operand have different types, and either has (possibly cv-qualified) class type, an attempt is made to convert each of those operands to the type of the other. The process for determining whether an operand expression E1 of type T1 can be converted to match an operand expression E2 of type T2 is defined as follows: and then, of course, loads of cases.....
  • 4k Topics
    18k Posts
    GrecKoG
    Le [=] n'étant pas nécessaire ici vu qu'il n'y a rien à capturer dans la lambda. connect(obj1, &MyObject::mySignal , this, [](int arg1){ qDebug() << arg1; });
  • This is where all the posts related to the Qt web services go. Including severe sillyness.
    1k 10k
    1k Topics
    10k Posts
    SGaistS
    Hi, I think you can use https://forum.qt.io/category/5/qt-io-webservices category for this type of question (moved there by the way). Are these in your "unread" section ? Are they marked as you following them ?