Thank you for the report. I have banned the user, which got rid of the spam posting. Not a loss, as this user did not post any other content on the site. Just deleting this one posting was not possible.
@mpergand I just tried it with another machine where "Noto Sans" was selected from the beginning. Same issue, from a certain size on, the bold text was displayed non-bold. But after having changed the font to something else and back to "Noto Sans", the issue was gone.
Maybe some strange configuration problem caused by an years old KDE profile and some updates?!
Strange, but could be fixed by simply playing around with the font settings.
@Axel-Spoerl my /opt/foo/qt_build/qttools/src/assistant/qlitehtml/src/qlitehtml_autogen/include directory is empty. Should it include the litehtml.h file? Is it expected to be populated after running the configure script, or is it not copied there until the actual build process?
Sorry, but that doesn't make it the "right" way to do this. You want to export every widget from a UI class so that the outside world can access it directly, reading and writing. Yes, Designer makes sure the ui class is private precisely so you don't try to do this.
Now if I move page1 into a QDialog which is a member of my MainWindow see myself forced to write getters and setters or signals and slots every time i need to read/write from one to another. That is what i wanted to avoid. So the question is if there is a way to write the QDialog instance so that i have access to its members anytime (even if its closed), and access from the dialog to the MainWindow's members without signals and slots.
You are not supposed to do this, even though you consider it advantageous. Yes, you should write getters/setters on the containing widget and you should use signals/slots if appropriate. Yes you may have to move code around if you happen to change what page widgets are on. Equally your way code would have a hard dependency on a particular widget and its variable name in another UI class.
Up to you whether you take this design advice or pursue the way you want to do it.
Hello, I am making an application that has the function of a text editor and when I generate the android version of the application, the menu does not come out as I would like I do not know if you can help me with it
How have you implemented the menu in your text editor application? (e.g., using the Options Menu, Context Menu, Toolbar)
Are you using any third-party libraries or custom views for the menu?
Could you share relevant code snippets related to the menu implementation in your application?
Are there specific sections of your code where you believe the issue might be occurring?
Are you using XML layouts for your menu items, and have you verified that the layout files are correctly defined?
Have you set appropriate icons, titles, and actions for each menu item?
Are there any conditions or logic in your code that might affect the visibility or behavior of the menu items?
Have you checked whether the menu items are correctly associated with the corresponding activities or fragments?
Testing on Emulator/Devices:
Have you tested the application on different Android devices or emulators to see if the issue is device-specific?
Are there any particular Android versions where the menu behaves differently?
Theme and Styles:
Have you customized the theme or styles for your application, and could this be affecting the appearance of the menu?
Are there any conflicts between your custom styles and the default Android styles for menus?
Are the menu items responding to user interactions, such as clicks or long presses?
Have you implemented the necessary event handlers for the menu items?
Android Version Compatibility:
Is your application designed to be compatible with a specific minimum Android version, and have you tested it on devices running that version or newer?
If you're using a Toolbar for your menu, have you configured it correctly in your layout and activity or fragment?
Have you set the Toolbar as the ActionBar for the activity?
Screenshots or Descriptions:
Can you provide a visual representation of how the menu appears and describe how you would like it to look?
Are there any specific design requirements or guidelines you are trying to follow?
I need to customize the QPrintDialog in the Qt framework. The default view has controls that give access to local storage on the device. All access to local disks must be disabled on the dialog.
Is this in reference to the print to file option? That can be turned off with the QAbstractPrintDialog::PrintToFile option. On my X11 test system with no other printer available, the dialog still shows the location as "local file", but the input to select a file is gone.
if there is a trigger causing issues it seems to only trip up 6.6.0.
When I'm correct it will also not work with the latest Qt5.15 (lts) and Qt6.5/6.2. If so then you have to blame the odbc driver since it does not return the correct string lengths. There was a fix for it to follow the odbc standard (and avoid wrong usage) but some ancient odbc drivers are not following the standard. So - please provide a fully working example.
Well, you could read the file node-at-a-time using QXmlStreamReader if the input is supposed to be a known, reasonably straightforward format. Then you will know the first time it does something unexpected.
However, the example you gave cannot be corrected automatically without knowing precisely what rules it should have followed. Given this input, <tag2> attrib="ABC" </tag1> is the "correct" input supposed to be:
<tag2> attrib="ABC" </tag2>, the close tag was supposed to match the open tag. The text is perfectly acceptable.
<tag1> attrib="ABC" </tag1>, the open tag was supposed to match the close tag.
<tag2 attrib="ABC"> </tag2>, the text that looks like an attribute actually should be an attribute, with or without with the space in the text, and with either tag1 or tag2. Does either element, tag1 or tag2, allow an attribute called "attrib"?
Other options I haven't guessed at.
If you have a schema , use a validating parser to determine all the ways your input is broken. Even without a schema, a well-formed XML check will pick up some obvious errors. Better still, tell the source of the XML to fix their own output.