Skip to content
Qt 6.11 is out! See what's new in the release blog
  • 145k Topics
    725k Posts
    M
    I get this error in my browser when the .wasm file is loading, causing it to fail to load. (Qt 6.9.3 + emsdk 3.1.70 + qmake) Through lots of trial and error, I figured out that it's happening when using emscripten::val, or maybe EM_JS, in a .cpp file that is located in a subfolder (relative to the .pro file). Moving the file up to the main directory yields a wasm file that works normally. Has anyone seen this and have any more details on what's causing it and what is a better fix than moving the file? My .pro file is pretty basic and I don't see any reason the location of the file should matter.
  • Jobs, project showcases, announcements - anything that isn't directly development
    4k 23k
    4k Topics
    23k Posts
    Mike Trahearn 0M
    Check out my LinkedIn Profile for: Project history and work experience Informative posts and articles about Qt and QML Ways that I could help you and your team!
  • Everything related to designing and design tools

    132 397
    132 Topics
    397 Posts
    SGaistS
    Hi, I think the wiki has the starting point Hope it helps
  • Everything related to the Software Quality Tools

    96 266
    96 Topics
    266 Posts
    C
    @Emma-2000 said in Squish for Java, select an item in a list box: I’ve run into a similar issue with long JavaFX lists where the target item isn’t initially visible. Using the component’s available items/model instead of relying only on scrolling seems much more reliable, especially when the test input changes dynamically. Agreed on using the model and toolkit API to access or even scroll a particular object into view. (Squish for Java tries to automatically scroll an object into view upon mouseClick(). And one can pass Button.NoButton (https://doc.qt.io/squish/java-convenience-api.html#java-convenience-function-parameters) to mouseClick() to trigger the scrolling attempt without performing a mouse click.) The approach with obj.items.length, obj.items.get(i) and assigning obj.value looks particularly useful for making the test independent of the item’s position in the list. obj.items.get(i) requires specifying the index of the item, which I intuitively understand to be the "position in the list". Perhaps by "position" you meant the location on the screen? If so, yes, hardcoded positions are better to be avoided. (Squish is using screen positions for sending events, etc. - but it determines/calculates these screen locations at runtime.) Ah, after further consideration, you probably meant iterating over the items until the desired one is found. Alright.
  • Everything related to learning Qt.

    401 2k
    401 Topics
    2k Posts
    Nils SjobergN
    Nice..now he knew whether to perform certification
  • 2k Topics
    13k Posts
    L
    Qt for HarmonyOS development with 6.12.0 https://wiki.qt.io/Qt_for_HarmonyOS_development_with_6.12.0 https://lists.qt-project.org/pipermail/development/2026-August/047432.html #Qt #HarmonyOS #OpenHarmony #Huawei
  • 4k Topics
    18k Posts
    H
    [image: acc63b82-54bc-40d4-a5d1-005d45c1cd23.png]
  • This is where all the posts related to the Qt web services go. Including severe sillyness.
    1k 10k
    1k Topics
    10k Posts
    SGaistS
    Ok, akismet triggering is not always clear. Beside this issue, what was your question about ?