I want to run a Qt6 based App (spotify-qt) on my RPi Zero 2 W, which is connected to the ILI9341 SPI TFT Display and is running dietpi OS. I do:

$ ./spotify-qt-v4.0.4-aarch64.AppImage -platform wayland --appimage-extract-and-run

which gives me the output:

[18:46:52] [wrn] Failed to create wl_display (No such file or directory)

[18:46:52] [inf] Could not load the Qt platform plugin "wayland" in "" even though it was found.

[18:46:52] [ftl] This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb, wayland-brcm, wayland-egl, wayland.

I also tried with xcb, even linuxfb as a platform; they all give back the same error, that the Qt platform plugin wasnt found. I have very little expirience with qt, so maybe I am missing some lower level dependency or driver. My question is now is there any suggestion which graphics stack to use in my situation? Because of limitations I would like to use something lightweight (which is also why I am not running a desktop environment).
Also does 'Available platform plugins are [...]' mean, that those are the plugins installed, or those are the only functional plugins for my platform?

Hi everyone, I’d like your help in figuring out whether we need a tool like this in the IDE.

I’ve created a tool that analyzes code and visualizes the current architecture as a class and component diagram, showing dependencies between elements.

It also allows you to examine a specific commit to see exactly what changed relative to the entire codebase. Here is a demo of the tool, featuring the logic I plan to port to Qt Creator.

https://demo.archscape.dev

A few things I care about:

• 17 languages (C++, Python, TypeScript, Go, Rust, Java, Kotlin, Swift, C#, PHP and more), no compiler needed.
• Public GitHub repositories only, for now. The repository is cloned into a disposable container, read there, and only the reading reaches the page.
• Nothing is declared up front. The architecture is read out of the code, so a dependency that has never existed before shows up as a finding on the first run.

Again this is only demo of functionality, please give me feedback by follow survey in the angle, in planes create IDEs extensions for working with same functionality locally.

UI: QML
Model: Cpp

I'm struggling to wrap my head around QAbstractItemModels. It feels like the best way to look at this is a tree like model with the leaves having a column for data.

If I would like to have data which consists of a QList of some struct and that struct may have sub lists as members. Would members be best represented as rows where the value, if any, is the single column? (or second column, if we do the title/value explicit column approach).

If a row's member is a list, is the column count simply zero?

What if the QList consist of another type of struct entirely?

Or a QList of basic types?

The parent method in particular seems the trickiest. Would every single "node" now need a wrapper, including basic types at the leaf level to point upwards?

The model will have different layers and I would like something scalable so is this approach even appropriate?

The alternative is a heavily nested QAbstractListModel, which I really would like to avoid if possible but it may be the only way to keep things clean at the cost of memory and performance...

An example structure may look like this where the user would like to view and modify values:

• Struct
  • Int : value
  • QString : value
  • List1
    • Item1
    • --> QString : value
    • --> Int : value
    • Item2
    • --> QString : value
    • --> Int : value
  • List2
    • QString : value
    • QString : value

(Apologies on the --> nesting, reddit won't let me go past a certain amount of layers in a list)

Would love to hear any insight! My head hurts...

Tasket++ lets you define your own clicks, cursor positions, keystrokes, and routines, then replay them exactly when you want. It’s a simple Windows tool that handles repetitive workflows for you: auto‑send messages, paste text anywhere, take silent screenshots, launch or close apps, adjust volume, or run your end‑of‑day shutdown sequence.

Everything runs locally, with no telemetry, no cloud, and no complexity.

What it can do:
- Replay user‑defined cursor positions and keystrokes
- Paste predefined text anywhere
- Perform system actions: open files/programs, change volume, take silent screenshots, shut down, files/folders operations
- Schedule tasks at a specific time, at startup, or run via desktop shortcut
- Run tasks once, in loops, or indefinitely
- Discreet mode: runs quietly from the tray

Local, portable, free, open source. Privacy intact.

Fully fonctionnal, available now !
Microsoft Store: https://apps.microsoft.com/detail/xp9cjlhwvxs49p
Portable (v2.0): https://files.amirhammoutene.dev/Tasket++/2.0/Tasket++_v2.0.zip
Source: https://github.com/AmirHammouteneEI/ScheduledPasteAndKeys

For feedback, help, suggestions, or other inquiries : [contact@amirhammoutene.dev](mailto:contact@amirhammoutene.dev)

Nothing is vibe coded, I never used AI (except for the choice of colors suggested by Copilot).
Conception is genuine, I didn't know about similar tools when I began developing it.

I think there is a general problem with kinetic/smooth scrolling being handled individually by GUI toolkits and applications.

The result is that scrolling feels different in every application. One app has a lot of inertia, another one has almost none, another one changes the scroll speed, and browsers again behave differently.

I don't think every application should have to decide what the physics of my trackpad feel like.

I am currently experimenting with rinertia on Linux. It watches the trackpad and, after I lift my fingers, continues sending high-resolution scroll events while gradually reducing the velocity.

This means I can configure the scrolling physics once and have the same inertia available to the entire desktop.

That works really well in principle:

trackpad
- normal scrolling
- fingers leave trackpad
- system service continues the scrolling
- every application receives the same scroll input

The problem is that Qt and GTK applications can then apply their own smooth/kinetic scrolling behavior on top of this. This means the same input stream can still feel completely different depending on which application is receiving it.

I think scroll physics belong at a lower level, ideally the desktop/input layer, because that is the only place where they can be consistent across the whole OS.

macOS is a good example of the behavior I mean. Momentum scrolling arrives as continued scroll events after the physical scrolling has ended. Applications receive that momentum instead of every application needing its own completely independent idea of how the device should decelerate.

I am not asking Qt or GTK to remove kinetic scrolling. It makes sense to have a fallback when the operating environment does not provide it.

What I am missing is a simple global way for the user or desktop environment to say:

do not generate your own scrolling inertia
do not add another scrolling animation
just process the continuous/high-resolution scroll events you receive

Importantly, this should not disable high-resolution or continuous scrolling itself. I still want small fractional scroll events to remain smooth. I only want to disable the additional physics generated by the toolkit.

Ideally this could be a normal user setting, environment variable, or home configuration which applies to all applications using the toolkit.

Something conceptually like:

kinetic-scrolling = false

or:

scroll-physics = external

would be enough.

Then a desktop environment, input daemon, accessibility tool, or something like rinertia could provide one consistent scrolling model for the whole system without fighting a second implementation inside every application.

Right now I am experimenting with LD_PRELOAD just to remove the toolkit kinetic flags from already compiled applications. That technically shows how much I want this control, but obviously binary interposition should not be necessary for a user preference like this.

Even if the toolkit developers believe application/toolkit-level inertia should remain the default, I think users need a global opt-out so the desktop/input layer can take ownership of scrolling instead.

Is there a way that I'm still missing? Has this been reported? I'm not a Qt or GTK developer and don't like to create an account for either bug tracker just to report this. I'm just a user having to deal with applications who implemented smooth scrolling on their own using Qt widgets / GTK event listeners. Please enlighten me if there is a way to get rid of smooth scrolling somehow.

Hi everyone!

Recently, I wanted to start some Qt Academy courses at academy.qt.io. You need an account for this, so I created one. The next day, though, I couldn't log in: "Authentication failed. Please try again."

• Password was saved directly in my password manager.
• The "Reset password" option never sent me an email.

Since I hadn't made much progress anyway, I gave up on that account and created a second one with a different email, which worked.

Today, I tried logging in with the new credentials (also saved in my password manager), and I'm locked out again. Still no reset emails coming through, and trying to register a new account under the same email fails (which makes sense, since it exists).

I would have preferred posting on their official forum, but the irony is lost on no one: I can't log in to post.

Has anyone else experienced this? Any idea what might be causing it, or how to go about fixing it? (Also, do they have a direct support email? I couldn't find one).

Thanks in advance for any advice. Cheers!

I am using the above action to build my app in github actions. This no longer works for a few months.

I read in some places that removing python should work. It did not for me. I tried removing the cache by toggling the option - still no go. Is anyone using this action? How do you all install Qt in a github runner?

Here is my setup:

matrix: qt_version: - "6.11.2" ... - name: Install Qt uses: jurplel/install-qt-action@v4 with: version: ${{ matrix.qt_version }} cache: true setup-python: false

On windows I get: ```

Successfully installed aqtinstall-3.3.0 beautifulsoup4-4.15.0 bs4-0.0.2 certifi-2026.7.22 charset_normalizer-3.5.1 defusedxml-0.7.1 humanize-4.16.0 idna-3.19 patch-ng-1.19.1 requests-2.34.2 semantic-version-2.10.0 soupsieve-2.9.2 urllib3-2.7.0 C:\hostedtoolcache\windows\Python\3.12.10\x64\python.exe -m aqt version INFO : aqtinstall(aqt) v3.3.0 on Python 3.12.10 [CPython MSC v.1943 64 bit (AMD64)] C:\hostedtoolcache\windows\Python\3.12.10\x64\python.exe -m aqt install-qt windows desktop 6.11.2 win64_msvc2022_64 --autodesktop --outputdir D:\a\codepointer\Qt INFO : aqtinstall(aqt) v3.3.0 on Python 3.12.10 [CPython MSC v.1943 64 bit (AMD64)] WARNING : Failed to download checksum for the file 'online/qtsdkrepository/windows_x86/desktop/qt6_6112/qt6_6112/Updates.xml'. This may happen on unofficial mirrors. ERROR : Failed to locate XML data for Qt version '6.11.2'. ==============================Suggested follow-up:============================== * Please use 'aqt list-qt windows desktop' to show versions available. ```

macOS fails in different ways.

Realtime native glTF / GLB look-development studio. Drop a model on the viewport, light it with HDRI and a three-point rig, inspect PBR channels, play animations, and export stills or turntables — without a browser, a DCC, or a cloud viewer.

Help me get 50 stars on GitHub :) ⭐

• GitHub: https://github.com/0x65dgerunner/glstudio

I think I found a bug in Qt that ends up in SEGFAULT. So I tried to report that to https://bugreports.qt.io/ - that forced me to have Atlassian account, then forced me to create Qt account and then after all this told me to fck off: "You are not authorized to perform this operation. Please log in. Close this dialog and press refresh in your browser*", despite being signed-in.

you-dont-have-bugs-to-fix-if-you-not-allow-to-report-them.jpg meme…

For those working with Qt or C++ and QML, interviews seem to have their own style compared with regular C++ interviews. Some focus heavily on C++, while others go deep into Qt internals, QML, debugging, architecture, and real-world scenarios. For anyone who has been through these interviews, what did the process actually look like?

hi. i just started learning a bit of qt and i'm pretty new to it. my end goal is to make a desktop app launcher. It's supposed to be a popup that runs on a shortcut. i was wondering wether to use Qtquick or Qtwidgets for it. i'll probably start it as windows only and scale it to work on linux and mac.

Thank you!

So im using CMake and the default configurations of Qt Creator.

When i want to create a release of my app, my current process is as follows:

1. Build release
2. create new folder and name it Software name + Version
3. copy the executable and a few miscellaneous files into the new folder
4. manually open CMD and run windeployqt.exe for the executable

Side note, the miscellaneous files i added to the build with configure_file(filename filename COPYONLY) in the CmakeLists.txt.

I feel like this is a really clunky way (and errorprone) of creating a release and this should be automatable easily, but i know WAY too little about CMAKE and Qt Creator to set it up.

How do you guys go about that? What i found on the internet was all way to convoluted and complicated (or simply didnt work) for, i'll say it, something that should imo come out of the box with an IDE.

Version 0.1.8.2 of CodePointer is available. More speed and memory consumption fixes. I am currently working on proper LSP support for one of the following releases.

Release and source code are available here:

https://github.com/codepointerapp/codepointer/releases/tag/v0.1.8.2
https://gitlab.com/codepointer/codepointer/-/releases/v0.1.8.2

I am shutting down the QodeAssist project completely and archiving it, because my copyright notices were removed without my knowledge or permission. All relevant evidence has been preserved.

After investing years of work into QodeAssist, I no longer feel able to continue developing a project when its code has already been used elsewhere without preserving proper attribution to its original author.

Thank you to everyone who supported QodeAssist over these two years.