It still doesn't work. Note: You should use QAction::setVisible() to change the visibility of the widget. Using QWidget::setVisible(), QWidget::show() and QWidget::hide() does not work. Source: https://doc.qt.io/qt-6/qtoolbar.html#addWidget That's why I'm currently "cloning" every QAction. The original for the menu, and the clone for the toolbar.

@Firewave here is a helpful GitHub action fork (not mine) that fixes caching: https://github.com/Kidev/install-qt-action

@jsulm yes, setting JDK 17 is required. Also, setting CMAKE manually for each Kit is also required. I successfully compiled a Mobile example using Android Qt 6.9.0 Clang arm64-v8a. However, I could not deployed to an Android 13 device. The device is detected by adb and Qt. However, I got the below error when releasing: [image: a3c9cf99-208b-45b1-9b0e-42e96e1c5144.png] Any advice on this ?

@SGaist OK, I coppied the main.qml file from the hellographs example to my project. And the GraphsView prompt was recognized. I found out, what the problem with my Main.qml was. I had to change the import commands: instead of import QtGraphs 2.12 change to import QtGraphs helped (-: Thank you very much!!! But, I have still a question: How can I use the XYModelMapper? Is there a good example? The usage differs to QtCharts, specially xSection : qsizetype ... Tobias

@SGaist said in QLineEdit - wrong placeholderText's color on Linux Mint dark theme: Hi, Which version of Qt is provided by your distribution ? Did you try to build your application with it ? Seems that installing Keepassx (I think it is the only Qt app which I installed from Mint repo, other ones are from flatpak) I got 5.15.13 as dependency packages: qmake --version QMake version 3.1 Using Qt version 5.15.13 in /usr/lib/x86_64-linux-gnu Command dpkg -l | grep qt also return similar packages: [image: e2c12747-7bc9-449b-817e-8f458455a8d3.png] I didn't try to compile on these versions yet @cristian-adam Can you provide .pro example? C++ is my secondary language and I'm polishing it on Qt where I mostly use qmake and .pro. Even if Phanton fix the problem, it is sad that so silly placeholderText has this problem in default Qt Style

I don't think I was harsh at all. The joke is old and been run through time and time and time again. It is a meme at this point that "insert operating system" sucks/hides/screwed up "insert something here". Looked at the Qt Source code and nothing helps there. That sends you to NSWorkspace::openURL function. Nothing special in the docs for that method either. Until you start getting really specific in Google which after a bit yields: https://stackoverflow.com/questions/16223026/open-an-html-page-to-an-anchor-on-mac-os-from-command-line Which then leads you to: https://apple.stackexchange.com/questions/194501/open-a-file-url-with-anchor-from-terminal/197284#197284 which basically confirms that the code path that Qt is using is broken for Anchors on MacOS. I would blame Apple for this. Not that they are going to listen. Now of course, since MacOS is just a meme at this point, doing osascript -e 'tell application "Safari" to open location "file:///Users/mjackson/Workspace1/DREAM3D-Build/NX-Commercial-Debug-Qt68-Vtk94/Bin/DREAM3DNX_d.app/Contents/Resources/Help/DREAM3DNX/html/Visualization/ApplyingRepresentations.html#outline-opacity"' does actually open the page + anchor but none of the images are rendered. Chrome, Edge and Brave all do load the images. What ever. We spent a bunch of time creating docs that could be served without the need to include QWebView or a built in web server for security purposes. Our clients did not like having those services running, even on the loop-back address and a random port. So we are stuck with local files.

Hi, In what way is it related to Qt ?

Hi and welcome to devnet, Might be a silly question but are you sure your lambda is called ? If so, is it called for all the expected stages ?

So the backend uses ffmpeg however I don't think that you currently can delegate the resizing to it. You could do it in a sink though but I am unsure about the performance of it.

Doesn't Qt ship with the Chromium rendering engine, have you considered using that for Assistant rather than using litehtml? David

Thanks, but: @Rangantha-B-V said in Custom TextField existing required property not initialized, but it is: implicitWidth exists on Item and is read-only (computed internally based on content/layout hints). I disagree. The doc does not write that the property is read-only. It says that "however some items have an inherent implicit size which cannot be overridden, for example, Image and Text", which I assume is the case of the TextInput, but is not really mentioned precisely in the doc... As a counter-example to read-only, you can set an implicitWidth with a ComboBox and with a TextField. The ComboBox can have a required on implicitWidth without any problems, which is not the case of TextField, why that ? @Rangantha-B-V said in Custom TextField existing required property not initialized, but it is: bind to width or implicitWidth internally So it's read-only from the outside but editable within the object ? In this case, why could I set it from the outside by simply removing the required line ?

@DiZhu if you read the docu, you may realize that the collides funcs of QGraphicsItem use bounding boxes of items to detect collision and this may not fit your app. If you have only triangles, it might be relatively easy for you to implement more accurate methods for collision detection. But it can be tough to handle all shapes of polygons.

@Jo-Jo I'm not sure what kind of answer you expect to get in a user forum like this? Nobody here is a lawyer.

Thank you for your help.I consider that the point is that executing .sh should be in Component when status of installer is Succcess.

@jronald Not sure why this is going wrong. Try playing with combinations of: add the series before the axes, remove series' own axes, use createDefaultAxes(). Any difference? Also FWIW whatever the cause this should not be a PySide6/Python issue, rather the underlying QtCharts code must be the problem.

@Qt-embedded-developer said in Build error on qt 6.8: what is this ? why it get shown there? It's the compile output. It gets shown here, because you have selected tab No. 4 "Compile Output". You don't have to explicitly link to stdc++. i am using fedor, so compiler is gcc. What does gcc --version say? Here is some general documentation about compiling Qt sources, which includes a section about required GCC versions. Here is a list of libraries /headers needed to compile Qt on Linux. Fedora isn't officially supported. That doesn't mean you can't build or use it, but there are no official instructions how to break down the list of required libraries / headers to Fedora packages. There is an old wiki page related to Qt5, which has some instructions for Fedora 30. You could use that as a starting point.

Thank you.

@PatG thanks, This helped me