General and Desktop

@Taytoo https://forum.qt.io/topic/136174/printing-a-simple-pdf

Hi -- thank you for the thought, sorry about the delay. I'm honestly not sure how that relates? I've tried to use defaults to see if I can find cached versions of the Preferences, but I haven't seen anything other than the usual -- for the user of an app, their preferences for that app are stored in ~/Library/Preferences/<AppID>.plist, and there are cached "binaries" in ~/Library/Caches/<Company>/<AppName>/qmlcache (qmlc files, which according to some docs suggests its for live state?). As the preferences I'm restoring are from [Q]Settings in a QML file, do you think they could be coming from a qmlc[ache] from a previous run? Asked another way, would QML look there in the absence of an OS-supplied preferences (which would have to behave similarly in e.g. Windows/Registry editing). FWIW there are a very large number of qmlc files in ~/Library/.../qmlcache. Cheers!

Qt 5.6 is even more outdated than Qt 5.15. Please try a newer version of Qt!

@SGaist Thanks, i'll check it out!

@dabble53 Simple: Your point is in parent coordinates. And parent is the centralWidget to which your widget is located at 40,40... exactly the values to pass to it. So how do you print these numbers?

QFileSystemModel loads its content asynchronously so at some point it likely has file handles opened to do its work which could explain what you are experiencing.

Thanks. Now I think I manage to do that.

Hello All, It was my environment which is creating the miss behavior of moc. My building tools were pointing to the wrong version of VSVC (MSVC 2019). I corrected this, and all worked fine. "My Culpa" Sincerely.

My project path contains non-ASCII characters, which might cause this macro not to work.

I solved the problem for my machine. I did change 2 things at the same time: The one that I think solved it was disabling the llvm use flag for mesa. I also enabled the z3 flag (as it was also mentoined here) for llvm. Maybe if I have time I'll see which one causes the bug, but for now it works and the long queue of print jobs that need printing can finally be done! Gentoo Linux users have a solution how to tackle this and if newer versions of Ubuntu or other Linux distro's have this issue, then at least there is some information for a solution.

@osirisgothra hi, I would say that modifying ld.so.conf.d to point to a non system Qt is the wrong way to do that. Either you have your distribution provided Qt that is installed or you use a wrapper script that will modify LD_LIBRARY_PATH for your application to find the dependencies you provide along said application.

Please format your code!

yes, you are right. I am sure Rmdir operation cannot remove non-empty folder. I met the same issue

@SimonSchroeder Waw, this is realy helpfull (and not just a squeam in horror ;-), thank ypu! I will have a close look into your library and rework the whole lot in this way. Will take some time, but I'll give you feedback when it's done.

Hi @JoeCFD , our application supports Qt 5.6.3. Since we are not modifying the application layer, we are continuing to use version 5.6.3.

Refer to these classes for <QCamera>、<QCameraViewfinder>、<QCameraImageCapture>, which should solve your problem

Not sure why I am having so many problems in something which looks very straightforward. Nothing really seems to work. [image: b0f3e8c1-3c1d-40c6-9ad7-168ea335d4db.png] The only time that I have been successful in the User Interface displaying a non-default translation language was with QLocale::setDefault. I believe that I am just going to go and try with this approach. My overall language detection logic in main.cpp is going to be something like: 0. Check if user has already explicitly set an application language If that is the case, skip to step 3 This information is going to be stored in an external configuration file outside the application. 1. Detect user's default locale with QLocale::QLocale() 2. Check if user's default locale has an available translation in the application If they do not, either do nothing else, or explicitly change the current locale to match with the default translation language (for the sake of readability) I need to think exactly how I am going to match the results but QLocale has both QLocale::language() and QLocale::name() and that should be more than enough. 3. Change default locale to expected locale using QLocale::setDefault I am not planning in adding my languages to my application. So, I am not really worried about having a big switch statement.

@shreya_agrawal said in Hide Grid Widget: How can I do it? Remove gridWidget from the layout or change its size to 0