General and Desktop

@buhtz Hi Christian, sorry for the delay. Indeed DBus messages would cause bubbles. But I think that's the only way on Gnome for the time being. A last resort would be to put these notifications into a separate toplevel window and raise it each time you want to get attention.

@eineskamelles said in QTextDocument and ts_tree_edit: Also one last question, are you sure that charsAdded and charsRemoved have to be added to position? Because when I create a QTextCursor on the added position it says that the index is out of range Yes, position + charsAdded is a valid cursor position pointing to immediately after the last character inserted as part of the edit. position + charsRemoved is not a valid position in the modified document, of course. If that doesn't work for you please post an example. @eineskamelles said in QTextDocument and ts_tree_edit: I have measured the time it takes for undo() and redo() methods and together I wouldn't do that. The interaction between the undo stack and the contentsChange signal is problematic, and will break in subtle ways, for example if you use edit blocks. You could do such things in response to the undoCommandAdded signal, but that is probably not helpful for your use case.

also i try the same application with weston --backend=drm-backend.so to enable the wayland then run the application in another termial with this command export XDG_RUNTIME_DIR=/run/user/1000 export WAYLAND_DISPLAY=wayland-1 export QT_QPA_PLATFORM=wayland it will work fine.

@Geometry Dash Thank you for the feedback 👍 I chose a desktop application because this is a technical/internal project, requiring the use of Qt and deep integration with existing systems (file system, hardware, offline-first). It's not aimed at the general public like a web application, so installation or update friction is not a top priority.

@JonB said in QWidget: Must construct a QApplication before a QWidget: If your repo release of Qwt is Qt5 you really aren't going to get anywhere if you are using Qt 6! They may both come from a repo but they are not intended to be used together. Surprised you didn't get a linker error or something. More suprised, it even runs normally serveral days ago, before some updates of Qt6. I've tested qwt-qt6, it works.

@JetSerge hi and welcome to devnet, Did you check the bug report system to see if something known ? If not, please open a ticket providing a minimal compilable reproducer.

Hi, You description fits the definition from the event filters documentation. One thing to remember: it should be fast. Otherwise you are going to make your application sluggish.

@Ronel_qtmaster it is a requirement. I can not change it. Thanks for your reply.

A tiny Qt GUI app showing 13 MB is normal, Qt brings along a lot of runtime stuff. If you want to shrink it, you need to use a release build and only include the modules you actually use. Static builds can make it even smaller. You won’t get it tiny like a console app, but you can shave off a good bit of that size.

if you want your thumbnails to align uniformly while keeping their aspect ratio, one approach is to create a fixed-size background (canvas) for each icon and then draw your scaled image on top of it, so you get a letterboxing effect and all items appear the same size. Additionally, in Qt, setting QListView::setUniformItemSizes(true) on your QListWidget can help enforce consistent item spacing, which works well when arranging items TopToBottom or LeftToRight. For the selection border and padding, make sure your QListWidget::item:selected style has some margin or padding defined so the border doesn’t sit right against the image. Combining these techniques should give you a neat, uniform icon grid with text below............

@Ronel_qtmaster Thank you for your guidance. This resolved the issue completely.

This one is quite simple so it can easily be recreated in raw QML too by animating 2 circles' opacity and size. If you have more animations (by number and/or complexity) this approach won't scale easily, looking into the Qt Lottie module would be preferable indeed (note that it is only available with the Commercial License or the GPL License, not the LGPL one).

@SGaist I have downloaded from the Shining Light Productions link. Thanks again.

@Nucleos The backtrace pointing to specific C++ code is not necessarily an indication that the source of the error is there; memory errors can cause impact at a seemingly unrelated location a lot of time after the original error was made (e.g how can Wayland code crash when it is not running) - C++ is just fun like that! That said, I can reproduce your crash though at this form it is not sufficiently minimal to be made into a bug report. Couple of stupid questions: Are you using COSMIC Desktop as your compositor? Do you have an IME enabled (e.g fctix5 or ibus)?

@Christian-Ehrlicher I previously suggested to OP above at https://forum.qt.io/post/834564 that they should use either a command-line argument or a new environment variable, both of which can be done explicitly in their Creator when running the program....

@Bobstar89 There is nothing "unexpected" here. Widgets do not have to be added to a layout to "appear". If they have been added with a parent but no layout they appear (I think) at coordinates (0, 0) of the parent. Either: Do nothing to you code. Just do not comment out layout.addWidget(self.cb_platform). By the time the widget is shown it will have been added to the layout. You have no reason to comment that out to see what it looks like without that line! Or: Call self.cb_platform.hide() to hide it and then later .show() when you want it shown. Or: If you don't like that follow @aha_1980's suggestion, don't pass self to its constructor and allow the later layout.addWidget(self.cb_platform) to set parentage only when you add it to a layout. In general when you are going to add a widget a layout it's "optional" whether to pass its parent explicitly to constructor, I tend not to.