General and Desktop

@mrjj How to add and delete rows in table by clicking spinbox up and down arrow? Please help me through python code.

The list issues both signals because both conditions have occurred (probably also issued currentItemChanged(), currentRowChanged() and itemClicked()). If you only want to act on one then only connect to one. The current item and the current selection are not the same thing in general. You can turn off/adjust tracking the selection with setSelectionMode()

Yes, you are completely right my QVBoxLayout that holds them is called MainLayout. But calling self.MainLayout.setSpacing(0) doesn't do anything. I am not sure if I understood the documentary correctly though, this might not be the right way to call this method. Anyways, i got it to work with the .setContentsMargin(0,0,0,0) method, for anyone who might have the same issue. Thanks a lot for the quick help!

Hello! I have created my own tool called winrtdeploy to copy assets directory and the manifest file from Qt directory. winrtdeploy.exe --source=$$(QTDIR)/bin/assets --destination=$$shell_quote($$DESTDIR) --verbose Now, this issue is resolved. Thank you.

i have the same problem. had same problem for over a year now just running in debugger Qt Creator 9.0.1
* Based on Qt 6.4.0 (Clang 13.0 (Apple), arm64) macOS Ventura on M1 see this bug

@SGaist Hard to understand, but ok I'll try to understand Thanks.

Hi, Two things that stand out: use the function pointer version of connect to use it with a lambda your lambda will just add an empty item to your list widget and leak a QLineEdit object every time you call it.

Hi, If you want absolutely everything, the best is to read qmake's sources.

Place a separate QScrollBar on the right side. Register it via QAbstractScrollArea::setVerticalScrollBar().

Actually this did help. Thanks a lot. I had find_package(Qt6 6.2 REQUIRED COMPONENTS Sensors ) in the CMakeLists.txt of the plugin but after adding 'Sensors' to the 'REQUIRED COMPONENTS' in the CMakeLists.txt of the project using the plugin it works now.

@Stefanoxjx Great you made it. The empty item is supposed to work as spacer. You may need it down the road.

Ok I see how to do it thank you for your help :)

@jsulm When focus in/out event occured for lineedit widgets on modal, i am emitting signals. Connecting it to a slot in mainwidget.cpp. the slot: mainwidget.cpp: void MainWidget::KeyboardOpen() { keyboard->show(); } void MainWidget::KeyboardClose() { keyboard->close(); } mainwidget.h Keyboard *keyboard = new Keyboard; It opens the keyboard widget. I want the keyboard widget allways on top with allowing interaction with modal window.

@CornerDoor said in lots of same thread '??? (in QtCore) load address': my qt built process has 125 threads like that Do you mean your Qt application spawns 125 threads?

@Bonnie said in QEvent not triggered: ui->lineEditTop->installEventFilter(this); Hey man you are the life saver. thank you very much:) I was searching this for several days.

@SGaist Yes I tried it. It didnt work and keyboard started working weirdly. not all buttons were fitting the screen.

K&R is a book about C. C has no classes or inheritance (unless you ugly fake it), so the term doesn't originate from there. C++ is multiparadigm language. OOP is just one of supported styles. So is functional, data oriented and others. C++ was inspired by a lot of languages before it, like Simula, Smaltalk, Modula-2 and others. Different people related to different languages used different terms to mean the same things. It's just your normal word soup. Get used to it as it's not going away. Subclassing, inheriting and deriving means the same thing. Subclass, child class and derived class means the same thing. Superclass, parent class and base class means the same thing. As for the original question - my personal opinion is that neither copying nor modifying existing projects is a good application design method. I would say you should rather design your app first, list steps needed to implement exactly what you had in mind and then implement it step by step, verifying at each step if it matches your design. You can use examples and code snippets for each step, but mostly as a guidance and not as the basis for everything. Copy/pasting and modifying entire example projects as pieces of your software is not a good way to write an application. Renaming stuff and gluing together things that were never meant as anything more than simple examples of some API usage is a way to make so called "spaghetti code" that's only good for throwing away.