Did you ever find documentation for the pyside6 specific sections and options for the toml file? I'm also looking for that now as I'm at the point of needing to deploy my project. I use Qt Creator rather than doing things by hand using Makefiles and the like.

I. Introduction Hi, I’m Julien, french founder living in Paris, and I’m working on a tech project with a clear objective: saving lives. The project is Simstrike: an early-stage startup aiming to build a next-generation training tool, with dual-use applications. The idea: to build an innovative immersive tool combining high-precision optical detection, advanced tracking and real-time 3D simulation. After a year of intense work on market validation, network building and early POCs, I am now looking for a Co-founder (full remote to begin with) to take full ownership of the main software development and turn this vision into a performant, market-ready product. If you feel ready to take the technical lead of an ambitious startup, this is the right moment. II. Overall Responsibilities Design and document a complete, coherent and modular software architecture. Contribute to the creation of functional prototypes, with measurable results and tested in realistic conditions. Identify technical bottlenecks and propose pragmatic, prioritised solutions. Cleanly integrate external software bricks (IR cameras, lasers, RF, Unreal Engine, tracking/mocap, etc.) into the overall architecture. Ensure clear and regular communication on progress, risks and needs. Contribute to the R&D roadmap and to strategic product decisions. III. What You Will Build (Key Missions) 1. Software Architecture & Development (C++ / Qt) Core architecture: define and implement a robust, modular and performant software architecture in C++ for the desktop application. Cross-platform development: develop the main application (ideally macOS and Windows), owning the full C++ / Qt technical pipeline. 2. Design and User Experience (UI/UX) UI/UX vision: define the overall interface design, delivering a modern, smooth and professional experience tailored to a complex tool. Prototyping & iteration: build fast interactive prototypes to validate ergonomics, navigation and user workflows, then iterate based on field feedback. 3. Node-based Editor (Core of the Product) Editor design: develop from scratch an in-house editor based on a visual system of nodes and connections, allowing users to define scenarios, logic, events, conditions, etc. Scalability: design an architecture that makes it easy to integrate new features and node types over time. 4. Product & Technical Leadership Strategic partnership: work directly with the founder on product vision, functional requirements and roadmap evolution. Technical decisions: be responsible for key architectural choices (patterns, frameworks, tools) and actively challenge decisions to maximise product quality. IV. Profile (Skills & Mindset) (I care less about “years of experience” than about the quality of the projects you’ve built (portfolio, demos, personal tools, etc.) and your motivation to join a startup to build something new.) Strong command of modern C++ and Qt. High level of autonomy, proactivity and ability to translate user needs into elegant technical solutions. Used to building fast prototypes and iterating in a structured way. Strong interest in UI/UX and clean, ergonomic interfaces. Experience or strong interest in performance and optimisation topics (responsiveness, real-time, memory efficiency). Desire to join an early-stage project and commit for the long term. Location: ideally based in France / Europe (similar time zone), full remote at first, with regular in-person meetups. Commitment: target to move towards near full-time in the short/medium term. V. What We Offer A key role in building the software: what you develop becomes the foundation of the final product. Equity / shares in exchange for early-stage commitment. Significant technical and creative freedom on architecture and implementation choices. A true co-founder relationship, not a “regular dev job”. A natural medium-term path towards a CTO (Chief Technology Officer) or Lead Software Architect role. Compensation in equity at the beginning, with the intention to add a salary as soon as we secure initial funding / significant contracts. VI. Application Process Phase 1: Detailed presentation of the project and vision, technical discussion and portfolio / past projects review. Phase 2: Alignment on responsibilities, level of involvement and terms of the agreement / shareholders’ pact. How to Apply Please send your application by email to: julien@simstrike.fr Required: Up-to-date CV Portfolio / projects (GitHub, GitLab, demos, screenshots, etc.) Optional but appreciated: A short motivation letter explaining why you want to join Simstrike and what you would like to build here. Thanks for reading me :)

Using QT Designer might be the simpler route if the main goal is to keep the workflow smooth with Python. QT Design Studio projects often need manual adjustments before they run properly under PySide6.

I'm just getting started with Squish 9.1.1 and I read the following in the documentation. The Squish IDE ignores the Debug and Interpreters pane preferences. Squish uses the Python installation it is shipped with or an external Python installation set by squishconfig. See Squish Docs. This makes me wonder why the Debug and Interpreters panes are available in the IDE. Is this some experimental feature that will be supported in the IDE in a future release? I'm just curious. Would be nice if anybody has some information. Thanks in advance.

Hey @RahmanTaleshi, please reach out to academy@qt.io if you have not already, and we will get this sorted. We are aware of some issues we are not investigating with challenge enrolments.

Hi @Mystery. Although your topic is quite old, I thought it made sense to comment on it, as this is a question that many ask themselves, and the Qt website doesn't provide an answer. Of course, it's not their role. I am going to answer this question as someone deeply involved in medical device software development - most of the time with Qt. We're ISO 13485 (medtech software) certified and often participate in or solely create documentation according to the IEC 62304 standard. Actually, this is somehow connected to the recently introduced EU CRA, because SBoMs will be basically a standard not only for medical apps. It's important to know that Qt on its own isn't certified. Some tools, like Qt Safe Renderer, are. BUT, Qt does a lot of jobs to ensure their software is of the highest quality, which is very useful for SoUP documentation. They do professional issues management, track changes, have static code analysis and unit tests so you can include it all in your documentation. What we usually do for dependencies (whether they are Qt modules or anything else) is: SBoM (Software Bill of Materials) - a detailed inventory that lists all your components (both internal and external) and their dependencies that make up the entire system. This is now required by the FDA in electronic format (like CycloneDX) as well! Vulnerabilities assessment - practically speaking, an Excel table where you go through the known vulnerabilities of the components and you assess whether they can do harm to your device. It all depends on what kind and what class of device it is. You can have two types of vulnerabilities -> cybersecurity ones and functional ones. All of them can be exploited if you are not careful. I will not focus on Quality Assurance and Validation of your internal components - code you write on your own, but rather on the dependencies. More specifically the modules you mentioned. Generally speaking, those are GUI modules so the risk is rather limited, but you have to assess them anyway. In your SBoM you might want to document: Dependency name Its supplire Version Hash (not necessarily) Software level of support End-of-support date License You can also go extra and explain what's the purpose of the particular dependency, but SBoM is not a place for that. It's probably to be done in Software Detailed Design documents. [image: c6a4f89d-540d-4dad-83de-e7fee3adde20.png] Then assessment: Component | Version | Vulnerability | Discovery method (you can, for example go over Qt's Gerrit or public vulnerabilities trackers like NVD, CISA KEV etc) | Applicability | Potential effects (if applicable) | Dangerous situation (if applicable) | Method of control (if applicable) | Evaluation (Detectability, Severity, Probability) | Recommended actions. Hope my answer is not overwhelming. I've tried to be as high-level and practical as possible without going into too many details. There is a lot of other work to be done around it, like the plan to handle vulnerabilities, but it's probably not a topic for this forum. In practice, all medical documentations really differ company to company. I wrote once about Software of Unknown Provenance in Medical Devices.

[image: dc2880e7-0937-4483-91de-5cc6b1e0664b.png] 项目升级QT6后启动 ASSERT failure in class QFactoryLoader *__cdecl QtGlobalStatic::ApplicationHolder<struct `anonymous namespace'::Q_QAS_qtlsbLoader>::pointer(void) noexcept(false): "The application static was used without a QCoreApplication instance", file C:/Users/qt/work/qt/qtbase/src/corelib/kernel/qapplicationstatic.h, line 59 这是什么原因造成

@AlexBlasche hi, I just relogged in and had a message that a jira admin had approved my e-mail domain - I guess the issue is that I use a custom domain for e-mails and this was causing issues? It looks like I can comment on tickets now so this might have been resolved Thanks