[Interest] Questions regarding "Improper Link Resolution Before File Access in QFileSystemEngine"

2025-05-07 Thread Schimkowitsch Robert
Hi! Regarding CVE-2025-4211, “Improper Link Resolution Before File Access in QFileSystemEngine”, could someone elaborate what public APIs are affected? The mentioned QFileSystemEngine is not a public API, so which public APIs use it internally? Since the issue mentions GetTempPath, which sounds

Re: [Interest] New in Qt 6.9: Default ContextMenu in TextField and TextArea

2025-04-23 Thread Schimkowitsch Robert
The context menu does not fit the design requirements of my application. I’ll ask support to schedule the patch for a 6.9.x release. Kind regards Robert (sorry for top posting, Outlook does not allow me to write text below a quote) It’s just cut, copy, paste, delete, select all: things you can a

[Interest] New in Qt 6.9: Default ContextMenu in TextField and TextArea

2025-04-23 Thread Schimkowitsch Robert
From Qt 6.9 release notes: “ TextField and TextArea now provide a ContextMenu

Re: [Interest] How to make QMap work as input to std::ranges::views?

2025-04-15 Thread Schimkowitsch Robert
> Il 14/04/25 17:35, Volker Hilsheimer via Interest ha scritto: > > As Thiago says, you have to use std::views::transform. Sorry, that was a typo. Corrected example using asKeyValueRange: https://godbolt.org/z/fT4G9TnKW > In that case, you can put the QMap itself directly into the pipeline: > >

[Interest] How to make QMap work as input to std::ranges::views?

2025-04-14 Thread Schimkowitsch Robert
I have tried and failed, please see https://godbolt.org/z/9zTzP7sYj It looks like QMap::asKeyValueRange returns something that is not really understood as a range, or not one that views can use. How can I use a QMap as input to a std::ranges::views pipeline? Kind regards Robert

[Interest] Issues with QML registration of C++ types (only in Visual Studio Solution)

2025-04-05 Thread Schimkowitsch Robert
My project contains QML files that will refer to C++ types by name. The QML module and type are registered on startup, the QML file does the right import(s), then I can use C++ classes (QObjects with QML_ELEMENT) as typed entities in QML. Everything works as expected….when using cmake. The same

Re: [Interest] Issues with QML registration of C++ types (only in Visual Studio Solution)

2025-03-21 Thread Schimkowitsch Robert
Seems to be a bug in Qt Visual Studio Tools – works when I revert to an older version. I’ll report it. Kind regards Robert From: Interest On Behalf Of Schimkowitsch Robert Sent: Friday, 21 March 2025 13:52 To: interest@qt-project.org Subject: [Interest] Issues with QML registration of C

Re: [Interest] Extension modules: Is there some documentation?

2025-02-27 Thread Schimkowitsch Robert
Hi! It would still be nice to know what the deployment strategies are going to be. It looks like the extension modules are named by Qt version, so there are extension modules for 6.8.2 and 6.9.0. If there is a critical vulnerability, what happens? Will I get a patched extension modules for 6.8.

[Interest] Extension modules: Is there some documentation?

2025-02-26 Thread Schimkowitsch Robert
Hi! I recently switched to 6.8.2 and noticed that web engine and pdf are now so-called “extension modules”. I understand the concept in principle (I think the idea of separating deployment of web engine from Qt as a whole, so you can patch issues separately, is about a decade old). Can someone

[Interest] Using QtConcurrent on Compiler Explorer

2025-02-07 Thread Schimkowitsch Robert
Can anyone give me a hint on how to bring a Qt code example using QtConcurrent to compiler explorer? I seem to lack a way to configure which Qt modules are available. I even tried to import a little cmake project that specifies the Qt modules, but they seem to be ignored. Kind regards Robert _

Re: [Interest] QMessageBox not displayed when monitor is switched off

2024-12-10 Thread Schimkowitsch Robert
Hi, the normal way to report this would be via https://bugreports.qt.io A quick search did not reveal any existing bug report in that direction. If you write one, please share the link, you have my upvote! Kind regards Robert This message and any attachments ar

Re: [Interest] QMessageBox not displayed when monitor is switched off

2024-12-10 Thread Schimkowitsch Robert
To clarify: You mentioned you were blind. Do you use some kind of screen reader to gather the content of the message box? How does the message box not appearing affect you? I believe for seeing people, it may appear as a reasonable optimization to not show a message box when the screen is off. So

[Interest] Status of TextDocument in TextEdit (6.8)

2024-12-06 Thread Schimkowitsch Robert
Hi! When doing anything complex with the content of a (QML) TextEdit, the TextDocument is just too good to ignore, but it is marked as preliminary. Now let’s say, in Qt 6.8, I restrict myself to the following: -) Pass the TextDocument property to C++ as QQuickTextDocument -) From QQuickTextDocum

Re: [Interest] Why does QVector2d not have copy/assignment?

2024-12-04 Thread Schimkowitsch Robert
Sorry, my mistake. I notice now that only the default constructor is user-declared, which does not prevent auto-generator of copy/move. Kind regards Robert This message and any attachments are solely for the use of the intended recipients. They may contain priv

[Interest] Why does QVector2d not have copy/assignment?

2024-12-04 Thread Schimkowitsch Robert
I was investigating why one of my simple structs was not copyable. Turns out that QVector2d has no copy constructor / copy assignment operator (Qt 6.7.2). This is interesting, since it is a) possible to construct a QVector2d from a QVector3d b) possible to construct a QVector3d from a QVector2d a

Re: [Interest] Future of constexpr in Qt?

2024-11-26 Thread Schimkowitsch Robert
> > Oh, I forgot to add the part that you also need a CI that compiles and runs > with ASan and UBSan. > That's certainly a good idea. Not aware of any UBSan running on MSVC, but nothing wrong with running a parallel CI using clang and UBSan (except...work :-) Kind regards Robert _

Re: [Interest] Future of constexpr in Qt?

2024-11-26 Thread Schimkowitsch Robert
> > That should be done in unit testing, wherever possible. Some > conditions we simply can't test, such as *succeeding* in allocating a > memory block of a size comparable to PTRDIFF_MAX because such a block > is not architecturally possible (on 64-bit machines). As a rule of > thumb for test writ

Re: [Interest] Future of constexpr in Qt?

2024-11-25 Thread Schimkowitsch Robert
Hi and thanks for your replies! > You will be able to create and destroy QString and QByteArray, find out if > they > are empty or not, get the pointer to the data, but not call almost any other > methods in them. Yeah, I can see this will be of limited use in real life... > > > Herb Sutter hig

Re: [Interest] Future of constexpr in Qt?

2024-11-21 Thread Schimkowitsch Robert
al Message- From: Volker Hilsheimer Sent: Thursday, 21 November 2024 17:42 To: Schimkowitsch Robert Cc: interest@qt-project.org Subject: Re: [Interest] Future of constexpr in Qt? CAUTION: External email. Do not click on links or open attachments unless you know the sender and that the content is sa

[Interest] Future of constexpr in Qt?

2024-11-21 Thread Schimkowitsch Robert
I’d like to use constexpr more in the future in order to catch UB in compile-time tests of functions. Qt has a little constexpr sprinkled here and there, but not a lot. Does anyone know if there are plans to expand Qt in this direction? Kind regards Robert This

Re: [Interest] Is it safe to construct QBindable from QProperty* via QUntypedBindable?

2024-05-24 Thread Schimkowitsch Robert
. But you sound like you do 🙂, so IMHO there's nothing to worry about. Cheers, Axel Von: Interest mailto:interest-boun...@qt-project.org>> im Auftrag von Schimkowitsch Robert mailto:robert.schimkowit...@andritz.com>> Gesendet: Freitag, 24. Mai 202

[Interest] Is it safe to construct QBindable from QProperty* via QUntypedBindable?

2024-05-24 Thread Schimkowitsch Robert
I use QBindable a lot in C++ classes that expose properties to QML. My typical property implementation looks as follows: Q_PROPERTY(qreal x BINDABLE getBindableX READ default FINAL) //... QProperty m_X; //... CPropertyClass::getBindableX() const { return &m_X; } I got the idea to use "&m_X" t