General and Desktop

Also, for different file path of .ui file, both change CMakeLists.txt: set(PROJECT_SOURCES main.cpp mainwindow.cpp mainwindow.h Form/mainwindow.ui ) and the mainwindow.cpp's include path: #include "./Form/ui_mainwindow.h"

@Axel-Spoerl said in QWidget Drag And Drop inside Layout. Is this a good way?: I have troubles to imagine what you mean by that. Colors aside, a widget is typically a rectangle. If I want to indicate a potential landing spot, I'd rather use a rectangle, than a line. I think @StudentScripter means the same behavior you see when adding widgets to a layout in QtDesigner. A "line" can be a thin rectangle :) You also see a rectangle when dragging QDockWidgets around showing the valid DockAreas. Maybe check the source code of QtCreator's Designer or QMainWindows dockarea.

@Zbigniew-Sch said in Program does not work properly using QFileSystemModel and QTreeView (Qt 6.7.2) under Windows 11: Are you from the Qt development team? This is a user forum... most people here are users like you with more or less experience. Debug your app to see why and where it crashes. If you think it's a bug related to QFileSystemModel and Win11, create a bugreport here

@SiGa As @SimonSchroeder said above, if you were using layouts properly, there's almost no way that things overlap, when resizing the main widget. Only free floating widgets, which are not part of any layout might do.

up .

@symHeisenberg You could show a widget when https://doc.qt.io/qt-6/qcalendarwidget.html#clicked is emitted where you show the notes for the date which was clicked.

@Joe-von-Habsburg https://stackoverflow.com/questions/10810279/finding-libraries-using-pkg-config-in-windows open one of the pc files and check if the prefix is correct. The installed pkg config path is basically fixed under lib. Do not try to change it.

I use the bin folder as an argument for the windeployqt command, and it doesnt work if i do it in another folder. However, running the windeployqt in the build folder worked just fine. Thanks for your help with that, i really appreciate it. Now i know which issue i am having with the form that doesnt open. For some reason, it says that the QtQuick.Effects module is not installed, even though i just checked to see if i have the additional libraries downloaded, and i have those. I dont know if i have to add something to my .PRO or something like that but it just says its not downloaded anymore

@apfal Happy you got it working. Good luck!

@CJha Look here. :)

@sayan275 It's also always better to post the relevant code as text and not as image, so others can reproduce it easier.

@Axel-Spoerl Thanks, finally my code is working

At https://learn.microsoft.com/en-us/cpp/windows/deployment-in-visual-cpp?view=msvc-170 we can see that there are 3 ways of having the Visual C++ Runtime available: Central deployment Local deployment Static linking The easiest way it's the local deployment, which means that you only have to have the above mentioned dlls next to your executable. If you are using CMake, then you just have to add one line to your CMakeLists.txt file: include(InstallRequiredSystemLibraries)

Thank you @SGaist for your advice and encouragement. I'm going to work on the subject

@MadisonTrash It works thanks!!

Hi and welcome to devnet, Are you thinking about something like QRubberBand ?

@JUDE34823 said in Scaling problems with the apps and preview Windows 11: My laptop defaults to (Recommended) 150% scaling at 2560x1600 150% is the issue here. QT_SCALE_FACTOR_ROUNDING_POLICY is an environment variable that controls how the 1.5 gets rounded. You might want to flor the value. Qt6 has a different default value than Qt5. Qt Creator has a combobox which allows the user to select the rounding policy. See https://bugreports.qt.io/browse/QTCREATORBUG-29501

@SGaist done

@lfmissonb Indeed, because that specifies its own font (and so color) for the fragment you are adding.

@Crag_Hack Yes, as I wrote earlier ISTM you do understand lambdas and captures! :) Lambdas do their capture work where they are in the code, e.g. as a connect() statement is met to set up a signal/slot. The lambda-slot then uses those variables in its code when the slot is executed at a future time. With an = the variable's value is copied at connect()-time, so the slot will always its value as it was at that instant, while with an & only a reference to the variable, not its current value, is copied, so when accessed in the slot it will have its value as it is at that time. An &-captured variable must therefore still be in scope/alive when the lambda body executes, which is not required/not relevant for an =-captured one.