@SGaist That's a fair question and to answer that it's because on the actual dock widget itself, in the production code, there are two widgets that get placed inside the dock widget itself. The topFrame contains the layout for the QTabWidget as you have pointed out. The code that is not present, botFrame contains another QGridLayout. These two then get placed inside the QGridLayout which is the layout of QGroupBox. Then to answer Why am I subclassing a layout to put widgets in it? I guess this is a personal decision and can be argued either way. For now, I will say that you are correct, that the Widget should manage the way the GridLayout adds widgets to them. However, I will argue that since QGridLayout is it's own class; the Widget does not "own" the widgets, rather, the layout owns the widgets since QWidget does not have a addWidgets function in it. Therefore, QGridLayout owns and is responsible for the Widgets that it owns. Hence the decision that the QWidget is the parent, which has a QGridLayout, which the QGridLayout as the Child, has the widgets that belong inside of it. This is a programming decision that I made with these arguments.

@YouDoItWrong said in Random crash on window resize.: By "bugreport" you mean code and error in this "head topic forum post"? No, bug report in Qt bug tracker: https://bugreports.qt.io/secure/Dashboard.jspa

We found a solution to that bug. The Cocoa window itself isn't set to non resizeable. If you do this, everything works as expected. class MainWindow : public QMainWindow { public: explicit MainWindow(QWidget *parent = nullptr) : QMainWindow(parent) { //this will get rid of the size grip widget showing setFixedSize(500, 500); } void mousePressEvent(QMouseEvent *) override { std::cout<<"mouse pressed"<<std::endl; } }; int main(int argc, char *argv[]) { QApplication a(argc, argv); MainWindow w; NSWindow* window = [(NSView*)w.window()->winId() window]; //IMTPORTANT. Otherwise the lower right mouse events will not be passed on correctly by cocoa window.styleMask &= ~NSWindowStyleMaskResizable; w.show(); return a.exec(); }

@AloyseTech IIRC hidePop() will reset the Popupwidget, so maybe hijack the add/remove process. Call hidePopup before adding are removing item and call showPopup afterwards?

Hi and welcome to devnet, What version of macOS ? Did you also check whether the latest beta of 5.12 has the same problem ?

@jsulm I got this, thanks

@raven-worx I tried the following but didn't work out.. QGraphicsPixmapItem* item = new QGraphicsPixmapItem(QPixmap::fromImage(qImage, Qt::AutoColor)); m_ViewerScene->addItem(item); QGraphicsRectItem* rect = new QGraphicsRectItem(m_BoundingBox); m_ViewerScene->addItem(rect); rect->setParentItem(item); m_ViewerScene->update(); //add the resized QGraphicsPixmapItem to the pixmap item->setPixmap( item->pixmap().scaled(QSize(128, 32),Qt::IgnoreAspectRatio, Qt::SmoothTransformation)); qInfo()<<"Rect resize props:::"<<item->childItems()[0]->boundingRect(); m_BoundingBox = item->childItems()[0]->boundingRect(); later I'm drawing box, on the image in an other viewer, with m_BoundingBox. The grey area within the blue rectangle will be resized to 128 * 32, and then the red rectangle would be added on the resized image. How to get the co-ordinates of red rect on the resized image?

@mrjj Sorry for not mentioning this before, I already tried a Gaussian Blur, it didn't help. The data is have is in the form: (xCood, yCood, zCood, value) For the first phase I am ignoring zCood. The problem comes with the sample data granuality as data is something like: (0,0), (0,100)..............(0,1500) (100, 0).(100,100)........(100,1500) ..... ..... (1500, 0).(1500,100)........(1500,1500) I have a canvas of 1500x1500 The image before gaussian (The border is part of a layer above the image, so they aren't going anywhere soon): After Gaussian Blurring (and some some interpolation on my part)(the data is a little different in both cases and I have done this in a separate application): As you can see, the output still has some boxiness to it. Also, doing it like this is just removing the sharpness of the image [it is eventually meant to be used to visualize input data not be a sunset image. Not to mention I am going too far with the blurring here making it really heavy for a repaint]. EDIT: Forgot to mention, I am using a continuous hue change here w.r.t value. But it seems that the proposal is for limited number of colors making the output even more blocky and blurring even more useless. EDIT 2: I eventually used the 2D shader for openGL. Latest output: Seems the most promising one yet

@sm4ll-3gg said in How to resize QListView row to index widget size: what I should read to better understand Model / View / Delegate programming? Basically everything I know comes from Advanced Qt Prgramming: Creating Great Software with C++ and Qt4 It is normal to set new delegate for each item if I need to show heterogeneous data in list? No. What I would do is create a QStackedWidget with the possible combinations, use that as base and display the correct page based on the data in the index

@Ocram10 said in Resize QMainWindow and QDialog: proprietà di windows "Ridimensionamento e layout" Dove trovi questa variabile?

@Fuel the exemples in pyqt-master do it automatically but i don't understsnd what event or property they use

@Ashutosh_Sachdeva You can try online installer to install Qt. My Qt setup installed using online installer has this header file. Also as stated in your other thread make sure you have QT += quickwidgets in your pro file.

@mrjj I don't want to resize it via a dialog. I need to do that with the mouse (manually)

@Gianluca86 You can make main window bigger and move the splitter. then it should be bigger.

Put the list widget in a layout. Here's more on layouts in Qt.

Hi. already fixed in https://bugreports.qt.io/browse/QTBUG-46074

@M4RZB4Ni yes, that is normal. Printer have many more pixels. so image seem smaller. Read docs. they have example of scaling stuff. This sample takes snapshot and scales it. void MainWindow::printshot() { QPixmap pix = QPixmap::grabWindow(QApplication::desktop()->winId()); QPrinter printer(QPrinter::HighResolution); printer.setOrientation(QPrinter::Landscape); QPainter painter; painter.begin(&printer); double xscale = printer.pageRect().width() / double(pix.width()); double yscale = printer.pageRect().height() / double(pix.height()); double scale = qMin(xscale, yscale); painter.translate(printer.paperRect().x() + printer.pageRect().width() / 2, printer.paperRect().y() + printer.pageRect().height() / 2); painter.scale(scale, scale); painter.translate(-width() / 2, -height() / 2); // note uses the form width/height! use pix.h/w if random image painter.drawPixmap(0, 0, pix); painter.end(); }

@the_ Yep its a nice few liners and not really dirty as sizegrip is made for such task so its not abuse or anything :) But sometimes having the grip there can be issue.

@eduardo_parra said: but the cursor detect the margins What margins? Do you mean for something inside the docks?

I found very usefull this class, I added some code to handle correctly a maximized FrameLess Widget. In void FrameLess::mouseMove(QMouseEvent *e) { if (_dragStart) { if (_parent->isMaximized()) { //this will handle correctly dragging when it is maximized maximizeWidth = _parent->width(); //maximizeWidth is an int attribute _parent->showNormal(); } if (_dragPos.x() > _parent->width()) _dragPos.setX((_parent->width()*_dragPos.x()) / maximizeWidth); _parent->move(e->globalX() - _dragPos.x(), e->globalY() - _dragPos.y()); } if (!_mousePress.testFlag(Edge::None) && !_parent->isMaximized() ) { //this prevent resizing if it is maximized [...] Now I'm wondering if there is a way to implement Windows 7/10 autosize function (the function when you drag a window on top/left/right/bottom edge of desktop and it will maximize/resize to half desktop size) on a frameless widget!

Hi, No, it's something you'll have to implement yourself. You'll probably have to create an event filter that will re-send any relevant event to your other windows.

Hi If you use layouts and put the buttons in one. Then no need for any code to do resize. So using layouts is how you do in Visual Design. Try this : Make new project open the mainwindow UI Place a button in the empty mainwindow. Right click empty spot on form Select the Layout menu (bottom) Select Layout Horizontally

BTW: If you want a fancy GUI that doesn't look / behave natively then you can use QtQuick for that. Besides layouts it has anchors, too.

It works! I'm very grateful to you.

So, I cheated. I set the max height to 180 pix and the min height to 179. The vertical resize handler is still here, but a so little resize not affect the design of my window, and I can resize horizontaly as I want.

You can put your widget and its neighbour into a QSplitter.

Thank you. It worked.

Just tried to remove that and the screen didn't look as I wanted. Maybe it's because not all my screens are scrollAreas ...

Hello @applefier , To fix the size of your layout you can use the setSizeConstraint ( SizeConstraint ) function and you have to put QLayout::SetFixedSize as arg of SizeConstraint Here is the doc explanation: sizeConstraint : SizeConstraint This property holds the resize mode of the layout. enum QLayout::SizeConstraint The possible values are: Constant Value Description QLayout::SetDefaultConstraint 0 The main widget's minimum size is set to minimumSize(), unless the widget already has a minimum size. QLayout::SetFixedSize 3 The main widget's size is set to sizeHint(); it cannot be resized at all. QLayout::SetMinimumSize 2 The main widget's minimum size is set to minimumSize(); it cannot be smaller. QLayout::SetMaximumSize 4 The main widget's maximum size is set to maximumSize(); it cannot be larger. QLayout::SetMinAndMaxSize 5 The main widget's minimum size is set to minimumSize() and its maximum size is set to maximumSize(). QLayout::SetNoConstraint 1 The widget is not constrained. Hope this will work, Regards !

@mrjj Yes. For this test case, I believe it would be setSizePolicy(QSizePolicy::MinimumExpanding, QSizePolicy::Expanding), but it does not work.

You're welcome ! By the way, you don't need to change the title of the thread anymore, just use the "Topic Tool" button to mark the thread as solved. Also, while browsing the forum, consider up-voting the answers that helped you, that will make them easier to find for other forum users :)