@nsourl said in Qt D-Bus on Windows:
Do you think it's a better idea to build from sources using the official dbus repository ?
You can try to build it by yourself
Hello Daes,
I'm facing the same problem and it seems no one responded to your previous post.
Would it be possible to combine qt Remote objects and QConcurrent and Qfuture to execute the slots asynchronously?
Hi and welcome to devnet,
Did you try to use the eglfs backend ? Since the Nvdia documentation mentions egl as system to use so you do not need an X server running.
@artwaw said in Is QSettings::setValue costly:
QSettings saves all the data to registry. I'd rather avoid that, you understand.
I set it to save to .ini files, I didn't try it but registry gave me a impression that it would be messy.
Mind you, I don't say your approach will not work in the end.
I know
Thank you for your insight
Hi guys, very new into Qt, just got this workin on high sierra/PyCharm/PyQt 5.15.3. My menubar is called "menubar" => self.menubar.setNativeMenuBar(False)
...if you try to solve it from python side. Thanks a bunch!
@ivanicy You can also try to disable parts of your code until it stops crashing then you know roughly where it is. And if you use CVS like Git you can check the changes since last stable version.
@aravmadd said in progress bar not updating during iterations but updating once the process is completed?:
So I am still confused why it is happening like this
Because you modify ui stuff from another thread which is not allowed. Use signals and slots as I already wrote 3 days ago.
@suslucoder
ok im not sure what s does.
Anyway, could you try
(in on_Serial_Read)
memset(dizi, 0, 14);
memcpy(dizi, data.constData(), data.size());
in place ot the line
memcpy(dizi, data.constData(), 14);
and tell if it still stops at 15 ?
@ngochm
You do not explain what this has to do with root. You talk about "privilege". Do you actually run a some (other) process as root from your app? Do you attempt to read from/write to a file in the file system which only allows root access? Or what?
Hi, and welcome!
@thaya said in STUCK ! ERROR : No suitable kits found:
I just installed the application.
You need to install 3 things:
Qt Creator, the IDE (Integrated Development Environment)
A version of the Qt libraries
A C++ compiler that is compatible with your Qt libraries
You have definitely installed Qt Creator. However, it's not clear if you have installed Qt and a compiler. (A "Kit" = Qt + Compiler)
Which compiler do you want to use?
@Ketan__Patel__0011 You can search on Qt bugtracker (https://bugreports.qt.io/secure/Dashboard.jspa) for the error you get (FAILURE_BUCKET_ID, NULL_POINTER_READ).
@AI_Messiah After editing the ui file in designer you should rebuild your project, so the uic compiler generates ui code, then autocomplition should work.
I know this is a very old post but I am stating my solution for newcomers and people running into the same issue in hopes it will help them.
I also had this issue and my solution was to add this to my .pro file
QMAKE_LFLAGS += -no-pie
When I had this issue I tried everything suggested and this is the first one that worked. Then I went online to try to see why that worked but didn't find anything right away so I left as it was. Working.
I can't find the link to the forum where I found this now, I had many tabs open then and didn't pay attention to the website name.
Qt Webassembly cannot block the main thread, so normal Qt socket classes still do not work correctly, as is. There is some work being done to get them working better with a threaded version of Qt WebAssembly, but it is still fairly WIP and not scheduled for any Qt version yet. Even so, some things like select() and poll() will not work.
Best to use websockets, as any posix sockets get translated into websockets, unless you use a proxy server method mentioned in:
https://emscripten.org/docs/porting/networking.html
@Nubcake
It will be because some existing files are "newer" than those you now create "today". Makes, and checking debug builds against source code, are timestamp based. Not a Creator issue. Make sure you start off with all intermediate files deleted. But yes, if you keep setting the clock back you will encounter this sort of issue.
@SGaist said in I'm trying to make a GUI for ROS and I get these errros.:
"Ui::MainWindow"
He told me to delete namespace. I thought that he meant
namespace Ui {
class MainWindow;
}
and I deleted this. I wrote back again and now works. Thank you.
@JohnM64
Well this hasn't resolved the issue of getting your clang code model working in Creator, it has just switched it off! You will get a different editing aid experience. If you are happy without clang that is OK for you.
The thing is: you have guidelines you can base your GUI for the various platform Qt targets. For the rest it depends highly on the type of application you want to do.
@Infestor
Super
well i have had other cases with mysterious gaps and your "~10 pixel wide border " reminded me.
Well then you dont leak it then but you also don't need to as QPixmap is meant to be copied (and its cheap)
QPixmap p("minimap.png");
l->setPixmap(p);
is better as then we cant forget to delete the pixmap and setPixmap copies it anyway.
When ever you need to use * with Qt classes you give to other Qt class, its a sign you shouldn't need to new it.
If I get it right, you can try CSS-like states (or pseudo-classes).
For example, consider a button with the next style:
QToolButton#MyBtn {
background-color: #000;
}
QToolButton#MyBtn:hovered {
background-color: #FFF;
}
It is black by default and white when hovered.
I have found some hack to get the toolbar actions from a print preview dialog. By adding some additional logic it fixed the issue.
QList<QToolBar*> toolbarList = printPreviewDlg->findChildren<QToolBar*>();
if (!toolbarList.isEmpty()) {
if (screenSize.width() > 1920 && screenSize.height() > 1080) {
toolbarList.first()->actions().at(0)->activate(QAction::Trigger);
} else {
toolbarList.first()->actions().at(1)->activate(QAction::Trigger);
}
}
To detect the screen size I use the native Win API methods. Now, it automatically triggers the Fit to width toolbar option and sets a better preview on 4K monitor. It works depending on the screen size. The issue is resolved.
