@BwvB I don't know whether installing an eventFilter somewhere would see the mouse release. But I don't see the solutions mentioning that.

Because we had declarations of shortcuts littered all over the place we came up with the following solution to handle them in one place. We derived a class MyApplication from QApplication and overrode bool notify(QObject *receiver, QEvent *e) override. Within this function we checked e->type() == QEvent::Shortcut. Everything that couldn't be handled is then forwarded to QApplication::notify. We didn't override the Ctrl+C shortcut or anything similar. However, because this is so early in Qt's signal handling you could be lucky with this approach.

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

Hi, exec is a blocking call so basically you modify your dialog content after you dismiss it.

@learnist please don't double post.

Glad you found out and thanks for the detailed solution !

Hi Yes they say "QtitanDocking replicates Microsoft Visual Studio UI for Qt" but cant find the actual pinning either. But at €624.01, i would sure ask first :) Im have not used Qt-Advanced-Docking-System before so i have no idea if pin Docks are possible without huge rewrites.

Old lasting bug ... Funny things happen in full screen ... In this screenshots you can see an another bug : the checkmark ✓ doesn't follow the font size of the menu.

I'm sorry, my bad :- (( @mrjj said in Detect top/parent move event on child widget: @Dariusz said in Detect top/parent move event on child widget: Or the issue is that sometimes WidgetA is a window and life is good, but then same class (WidgetA ) is used in a layout and then suddenly it cant inform widgetB any more since only top parent knows it was moved ? Something like that ? Yes, since its dynamically generated UI based on a user template, the WidgetA can be inside layout of another widget, or be by itself.

@Rizwan94 May I ask what was your final implementation? I'm trying to setup a frameless window and add my title/close buttons on top of an existing QMainWindow (from .ui) Thanks in advance

Hi As far as I know, there is nothing like that in Qt. It can blur widgets but not the actual desktop.

@jsulm Hello! Sorry, but that doesn't work. I tried to insert a loop in different places, but the result remains the same. I also tried to display the main widget. @SGaist Hello. So the VideoWindow.h file (VideoWindow class) is my custom widget. This is the first piece of code that I presented.

Hi I did not find any other way to gain access to the tab bar.

got solution. before using the minimum size function set the windowstate Qt::WindowFullScreen. In my case I used line this->setWindowState(Qt::WindowFullScreen); before this->setMinimumWidth(1366); this->setMinimumHeight(768);.

Seperation of Concerns (SoC): https://en.wikipedia.org/wiki/Separation_of_concerns There are design approaches that go further, but SoC is a good place to start.

Thanks, mrjj! That's it! Merry christmas

Hi and welcome to devnet, First thing, please don't delete all that stuff in your destructors. Qt has a pattern that is based on parent widget (the parameter "this" in widget constructors) that take care of destructing all the children automatically when the parent is deleted: http://doc.qt.io/qt-5/objecttrees.html Now regarding your problem, only one widget can have focus at the same time. For the focus part, you can use setFocusPolicy on your widgets, giving an enum that tells more about the behavior you expect. For what I have experienced, playing with opacity and trying to give a modern look to a desktop software is kind of a pain. Long story short: there is no user friendly API to do so, or at least as user friendly as what QML provides. This is either because the widgets part is late compared to the QML one, or because "modern" has been associated with app, browsers, Internet, but not with desktop. Nonetheless, things might evolve in the future, since Qt developers have communicated about resuming the widgets development. This doesn't solve your problem, but could explain why you are having so much trouble trying to code an overlay that behaves with good focus policy, and using low level code such as QPalette that is always a sign you're doing something wrong, or at least not initially intended. Which could be fine, if you really know what you're doing, and you are aware that you'll have to deal with a lot of work to make your application look the same on every platform. EDIT: So I created a project with your code and here are some remarks: 1 Do not set a layout to your main window, just set the central widget with, well setCentralWidget(widget) 2 qreal is an alias for double, so instead of qreal(100)/100 just write 1.0; same for qreal(50)/100, just write 0.5 and it will be perfectly fine. 3 No need to use "this->" you are coding in C++, not JAVA ;) For your problem, I think I don't really get what you are expecting. Just an overlay when the setting widget pops? If so, maybe working with a QDialog (a modal one) would be better.

@jsulm @mrjj @ig Thanks for all the help. I was able to fix the inheritance issue by creating a new FileMenu instance in the main window.

@NIXIN You have a QMainWindow inside splitter?! I doubt that. You should have two widgets: for the left side of the splitter and for the right side of the splitter.

@Ongsk Title bar decorations are managed by your window manager. You can change them (at a user level only) by changing your theme. This applies to osx, linux, and windows. If you want to force a specific color then you could make a window with a custom title bar and draw it however you want. Things like Chrome do this. Then they have an option to "use system title bar and borders". IMO, unless you are making a fully custom window like a video game launcher, or splash screen, or something like that you should let the window manager decorate the window. People customize their WMs to look how they like and standard looks are a foundation of GUI development. Here's a post from @mrjj that shows you how to do it in windows with native calls (Qt doesn't have a call for it) in case you insist on forcing a color on your users. https://forum.qt.io/topic/85837/change-window-title-bar-color-in-windows Keep in mind that will be for windows only so if you compile for linux or osx it will not work.

@magicstar Thanks i landed up using this. Worked

@L-Koziarz Yep its sounds somewhat convoluted but never the less - exciting approach . I wish it had worked as prof of concept but it seems there are issues.

@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

@eDeviser said in Customizing QMainWindow by style sheet: Yes, this helps! I see the QMainWindow holds a QWidget which is set as cetralWidget. So It would be necessary to set the QMainWindow as centralWidget or to apply my css for the QWidget. Thank you for this hint. You have to apply your css in your qwidget ! Your css should be : centralWidget { background: yellow; width: 10px; /* when vertical / height: 10px; / when horizontal */ } centralWidget:hover { background: red; }

You should care about QSizePolicy and sizeHint of your widgets inside QDockWidget. ;)

Hi, and welcome. The image upload function on our forum is broken, the uploaded images might be visible to you, but they aren't to anyone else. See this thread for a workaround.

@mrjj Thanks for the reply! I followed your advice and tried setting the panelWindow as the parent... No change.. Any other ideas? I followed this link, http://doc.qt.io/qt-5/qmacnativewidget.html#details

Hi SGaist and thank for the help. For the code being in the constructor when it should not be, I only did it that way to have the simplest code possible to show my issue. I understand and agree with your point. I am working on an already existing application, I created this QtCreator project to isolate and replicate the issue. I do not call QWidget::show() in the constructor of my application. I have made an important discovery while working on this issue: calling blue_widget->show() at the end of my code in my QtCreator project does fixe the problem, but doing the same in my application does not fix the issue. This is the 1st time I see a different behavior, I thought I had manage to have the same 1:1 behavior between the QtCreator project and my application. Thanks for the help, I will keep looking.

@pauledd :) class MyWidget : public QWidget << yes that is subclassing :) Also, a widget can only paint on it self. its not possible to paint on other widget from inside a paintevent. Thats why the first sample didnt work. You asked painter to paint on tab from inside mainwindows paintEvent :) I guess you already found out but its just to make clear for other readers.

@SGaist I just want 1 window with the forms changing for the login and presentation windows. And then ill use dialog windows after the presentation window. Anyways thank you. Ill try QStackedWidget.

I need to be as big as the screen. Before I used this code to display it as big as the screen int Height = 0; int Width = 0; foreach (QScreen *screen, QGuiApplication::screens()) { if(QGuiApplication::primaryScreen()->name() == screen->name()) { QRect rec = screen->availableGeometry(); Height = rec.height(); Width = rec.width(); } } w.setFixedSize(Width,Height); Unfortunately, I do not know why, the height is still longer than the screen. This is why I decided to use showMaximized (), unfortunately this does not seem to go well for both systems.

Thank you all, I will try to use your advice.

@AyushExel204 It is indeed strange. I haven't worked with that library, but I see no good reason that is should work with VlcMediaPlayer but not with VlcMediaListPlayer. In this example (graciously provided by @mrjj over chat), they don't seem to use VlcMediaListPlayer and as you said that should work. Perhaps you can use it to build upon. Also you might want to search through the library's bugtracker to see if there is something known about this issue.

Hi, just to want add, while Qt Creator's capturing of your qDebug() output is usually 100%, but if you want to be sure to get everything, you could try running DebugView when your app exits.

I had to add Q_OBJECT and also delete my debug folder once, to get rid of a few link errors. Also got rid of the QThread subclassing, it is way easier to create a worker class and connect it through signals. There is really a lot of outdated example code out there. Thanks for your help!

IMO it's a code smell to rely on the OS to clean up for you. We run all of our unit tests through valgrind as part of our build process, so that a memory leak breaks the build. QT leaves a ridiculous amount of memory lying around, which of course kicks off valgrind. We've got a huge suppressions file which we have to install for every GUI related unit test, and the sheer number of suppressions makes valgrind run slower, so has resulted in longer build times. So yeah, in my opinion, it would be nice if QT didn't do that.