According your first picture you're missing a layout on the widget.

@SGaist looking at the QCamera example gave me a lot of info to fix my issue. I was using the QCamera wrongly. Too many start/stop followed by lock/unlock etc. Now the image is captured correctly.

Check the generated code to see what it does differently than yours.

Since applications using burger menus usually have a very distinctive style I didn't want to make any assumptions. The look of the menu is up to you to style, it only implements the functionality. Same goes for the burger icon, you can set it to whatever you want, either the one included in the project or your own. There's an example in the repo showing how to style it. As for actions - you can add an existing QAction or let the widget create one for you using any of the overloads of addMenuAction. In any case it returns a QAction* and you can connect to its triggered signal just as you would with any other action in the built-in Qt menus. Alternatively you can tag these actions in any way you want and only make a single connection to the BurgerMenu::triggered signal. You will get an action that was triggered as a parameter. One way to tag an action is by using QAction::setData or you can just store the action pointers somewhere when creating them and identify the action by the pointer, text, some property or whatever fits you. on_actionName_triggered() looks like a slot name created for the the auto-connection feature. If you want to use it you can do that too (although I wouldn't reccomend it). Just create your actions in the designer via its action editor and make your slots names match, just like you would with any normal menus/actions. The only caveat is that you need to manually add these actions to the menu from code, as there's no way to do that in the designer, but that's not a huge problem. So those are a couple of the most straightforward options out of couple more. It's deliberately left very flexible so you can use it however fits your overall application design best.

@sierdzio Ok now it's much clearer, thank you again. It looks like there is a lot of documentation to read, but apparently most things I have in mind should work. Still, for some reason, I feel QWidgets will perform faster. I'll try to make some tests and get back here. Thank you again!

@VRonin I want to do some heavy changes/customisations... stuff I cant do in CSS... Like moving expand button to opposite of tree, changing location of checkbox, changing indentation of child items. How can I control indentation of child items? I need it now :/ I keep getting "invisible" hitboxes as my child item is moved to left visually but hitboxes are drawn in original places :/// Ideas? I just realized there is "setIndentation"... sigh............ Ok that kinda works, how can I set indentation per row? :D

@VRonin Yeah you are right. Usually my custom widget has another widgets (like another label for text, button for submit etc.) so I used setItemWidget. But your way better for only images.

@Chris-Kawa That would work for multiple QOpenGLWidgets in the same application. My use case involves sharing the context of one QOpenGLWidget with that of a QOffscreenSurface

@Pythonic-person said in Widgets with SizePolicy there is no effects: Do you mean taking the main window size and then change the widget size with the code? You either use one of the provided layout mechanisms, develop you your only layout implementation, or you do all the resizing of contained widgets yourself 1990's style. If you wish to do it yourself then you need to override the resizeEvent() of the container widget and resize the contained widgets yourself using whatever logic you see fit.

@JonB Thanks.. found out, that i needed to create a new Pointer in the Declaration of the .h File.. Means.. TGS_Widget_AssetList * _assetList; Wasn´t enough... I needed to do: TGS_Widget_AssetList *_assetList = new TGS_Widget_AssetList(this); or auto *_assetList = new TGS_Widget_AssetList(this); Now it works.. i will update my initial post here

@ChrisW67 Thank you so much for your recommendations! I will try.

@new-qt_user-2022 All the best! Feel free to post new questions if you'd like further help.

@SGaist Merci pour vos conseils à l'avenir , j'éviterai de faire ce genre d'erreur . Bonne fin de journée.

@timob256 said in How to embed Ogre3d in qt5 as a widget: QWindows not unit setLayout ? install in element, not posible. Don't know what this means. this->setLayout(gl_layaout[3]); // this not work !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Don't know what this means. All your widgets are created with parent as their parent, instead of this. Since I wrote earlier But why are you using parent here? Shouldn't it be this? do you not think this applies to your case? Why? You are creating your widgets with a parent of parent of QTOgreWindow, and then this->setLayout(gl_layaout[3]); setting the layout on this. I don't get what you are trying to do or why. UPDATE I see you have now taken this question to https://forum.qt.io/topic/132674/how-do-i-put-a-qlayout-in-a-qwindow. It's always helpful to others if you cross-reference posts like this. I see now that my "But why are you using parent here? Shouldn't it be this?" is not applicable to QWindow. I will post into your other thread.

@JonB it works bro thank you problem fixed when i tried this before it doesn't open the window at all ... just flashing but now i understand why it's working Thank you <3

@Christian-Ehrlicher Hi Seems to call it from QPushButton::sizeHint() but I failed to find way to trigger it without altering text. I guess for full disclosure the source is needed and single step :9 I use wobog for it.

@JoeCFD Thank you, will investigate this avenue too!

Thank you for the answer. Setting a child did enable the layout selection. I don't understand the logic behind that at all but ok. QcmEntryGuess are QWidget I've created on the side. They're only a QLabel nested in two layout Althought my QGridLayout is still only consisted of one row. I'm probably missunderstanding one of its property

Correct.

@BDC_Patrick said in Get all Widgets of Type <Type> ?: But, this only works, if i put the code directly into the construct function of the Window itself (after ui->setupUi...). Why? It's QObject::findChilden(), you can use it for any widget. But, i thought more of a Function in a seperated file, that all Windows can make use of. If you really want it in a separate file then pass the parent widget as a parameter. Are you using Qt's support for cross-language?

@Pl45m4 no but I don't know how to do that sizeHint() can return the right size in a layout.and I have a valid parent.

@JonB Thank you for your feedback. Going thorugh the existing children lists and filter the widgets in specific code is surely a bit more efficient with regards to speed, but that's not the kind of optimisation I was looking for. Some frameworks have a dirty flag for instance that triggers an evalution by the graphics system when it is due for evaluation (on 20ms ticks for instance). The polish/unpolish functions could benefit from a better documentation. I have a stylesheet only at the QApplication level, I empty all other stylesheets that are set by QtDesigner - I use the only for that. I use the same "style()" because it works and it probably is a small performance gain. I haven't tried polishing the application itself, and I suppose that is an overkill for just updating a few widgets. The default implementation of (un)polish does nothing, but QStylesheetStyle does. It seems to wrap the baseStyle(), which is likely something like QWindowsStyle or QFusionStyle which do nothing. But that's doing exactly what is needed then, only the stylesheet impacts the layout and the QStylesheetStyle handles that. QWidget::ensurePolished works recursively, but polishes only "unpolished" QWidgets in the end. Upon examination of the QStylesheetStyle code, it seems that unpolishing may not be needed. So I am removing that from the "recursive" implementation and I'll see if it's ok. It seems to avoid quite a few unnecessary operations! Update: polishing "recursively" is just enough.

Thank you for your advice. I did as you said and it seems it's working well.

@Dariusz said in How to properly delete threads& objects in them ?: So in general, moving object to another thread does not set the thread as it parent does it. No because the function is called moveToThread and not moveToThreadAndDoOtherStuffLikeSettingaParent

@Christian-Ehrlicher Now I got it It does not have size for the contents of window and if we put layout to it then it will try to keep content inside it It is shown in ui file and because it has no content on given portion so it wont display anything Thank You

@TUStudi Well, it's not necessarily that: you can create an item via void QTableWidget::setItem(int row, int column, QTableWidgetItem *item) instead.

I made it work by removing this flag: Qt::WindowDoesNotAcceptFocus

@jsulm, I apologize, I should've mentioned it in the original post: one of the requirements of the project is that we can not use any 3rd party library for the text editor, except for Qt. From what I see in the QScintilla github, it is ported to Qt on top of the TextEdit widget, so I will look further into their implementation to figure out how they've done it.

@Eric-Singer Because my suggestion is not to limit the size of the parent but rather to limit what the layout reports as the minimum size required. minimumSize() returns the minimum amount of space the widget needs to provide so that the layout can fit all the widgets inside it. maximumSize() is the size beyond which the layout can't reasonable grow the widgets inside. Maximum size is not useful for this case. Your problem is that the parent widget grows too much and it grows because the minimum size of the layout grows i.e. the minimum amount of space required to lay out the widgets inside grows. If you return a fake limit, one that is smaller than the sum of all the widgets inside, the parent will be able to keep its size despite all the children in the layout not fitting (visually they will be cropped). You could, for example, return the minimum of the base implementation's value that calculates it based on the content size and some constant value of yours, beyond which you don't want to grow. To be honest that's pretty much what a scroll area does and I think the suggestion given by @SGaist is a better one as it already does that work for you.

Hi, How are these widget managed from a data saving point of view ?

@ricardovaras_99 said in What library should I use for animation in Qt Widgets Application?: And I want to simulate water level increasing on a tank. Do you want to animate the water level (in other words, make the level rise or fall at a specific speed in real time)? Or do you just want to display the water level? (in other words, make the picture show the latest level)? If you want the latter, have a look at the Qt Quick Coffee Machine demo: Video: https://resources.qt.io/videos/built-with-qt-qt-quick-coffee-machine-demo-qtws17 Code: https://doc.qt.io/qt-5/qtdoc-demos-coffee-example.html

In one of my project, a bit of resolution seems to be lost when scaling (150%). It is plotting a complicated graph for signal processing. We are thinking whether we can just plot the graph according to the scaling factor (e.g. running the math calculation ourslef and generate a graph double the size for high resolution etc) and not to scale this part of the widget by using the high dpi setting.