wAsPair = map | std::views::transform(fTransform);
But you cannot use an rvalue as the input range (see e.g.
https://en.cppreference.com/w/cpp/ranges/dangling). Make a copy first:
auto keyValueRange = map.asKeyValueRange();
auto viewAsPair = keyValueRange | std::views::transform(fTransfor
t::ShortcutOverride event (which is a QKeyEvent) for Ctrl+X.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
s, or writing a pure QML test, is probably the
way to go.
Fee free to share a link to your attempt on gerrit.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
default delegate
doesn’t assume that it has to care about the item’s BackgroundRole value if the
item is selected (so setting e.g. a semi-transparent brush for the Highlight
role won’t work).
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Thanks a lot Andy, I'll have a closer look onto these.
Right now we are using a Qt3D based solution for displaying physics
simulations and motion capturing results.
Cheers, Volker
Am 15.02.2025 um 17:00 schrieb Andy:
Volker:
I investigated a bunch of options: OpenSceneGrap
Hi Andy,
Out of curiosity, what new or boring technology are you migrating your
Qt3D to?
Cheers, Volker
Am 14.02.2025 um 16:00 schrieb Andy:
Thanks Mike.
I was actually doing something similar and moved away from it in
favour of (more) self-containment! :-)
I did have some success at
lang trunk, and
-std=c++26, another character breaks the build - not because of the
static_assert, but because the “data” variable is no longer initialized by a
constant expression.
Volker
PS: which is why for the JNI improvements in the recent Qt releases we cooked
up a true, but
rwise benefit from
it.
If there’s any part of Qt where you’d see significant value from making things
constexpr, then you’re welcome to push things for review.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Ah, interesting. Didn’t know that page exists :) Will ask someone to catch up.
Cheers,
Volker
> On 3 Oct 2024, at 16:33, Pierre-Yves Siret wrote:
>
> I forgot to link the qt.io page, this is the one :
> https://www.qt.io/product/features
> This doesn't mention the market
ntrols). I don’t know which
exact qt.io <http://qt.io/> page you are looking at, but I suspect that what
you found as not licensed under the LGPL is the former, while the code in
qtdeclarative is of course the latter.
https://bugreports.qt.io/browse/QTBUG-96585 is about integrating
: QTBUG-26369”),
and then push your local commit to gerrit via
% git push gerrit HEAD:refs/for/dev
(the gerrit remote will also have been set up via init-repository).
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
e.g.
% ninja tst_qstring_check
To build and run a whole set of tests you’d probably have to write a script
that processes the output from `ninja -t targets`. Re-configuring with
QT_BUILD_TESTS_BY_DEFAULT=ON is probably a better choice.
Volker
__
’
(the || true is needed because some helper-repos don’t have a ‘dev’ branch).
before configuring.
The process is documented at https://wiki.qt.io/Building_Qt_6_from_Git; if you
spot anything on that page that could be improved, feel free to make changes.
Cheers,
Volker
Qt has never linked to MFC.
Perhaps with VS2022, the path to relevant headers and libraries is no longer
implicitly added to the INCLUDE and LIB environment variables.
Volker
> On 2 Jul 2024, at 07:56, Axel Spoerl via Interest
> wrote:
>
> Good morning David,
>
> t
on Android
through the emulator, and only release smoke-testing on device; so
theoretically, the plumbing in the Qt build system should just work if your
emulator has a ChromeOS image.
And you can of course file bug reports, but they might only get attention if
the issue is reproducible on
> On 19 Jun 2024, at 20:14, David M. Cotter wrote:
>
> If i have a QGraphicsScene (not necessarily connected to a view, or if
> required, an OFFSCREEN view), can i set its output as the input to a
> QMediaCaptureSession?
> I see i can connect a QWindowCapture, but must that window be showing? c
king the QAccessibleAnnouncementEvent object accessible
for other code to modify it before you send it with updateAccessibility() would
be an improvement.
Volker
> On 13 Jun 2024, at 13:32, Corentin Bacqué-cazenave
> wrote:
>
> My idea is to instantiate QAccessibleAnnouncementEvent in the main window
have only one level of children and already have the
QObject that they belong to, then you can create the event with the QObject,
and the child index by calling QAccessibleEvent::setChild.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
instance to call that method on?
FWIW, QAccessibleAnnouncementEvent, is a new type in Qt 6.8, and we are still
in beta, so if there’s anything missing from that class to make it usable, then
there’s still time to add it.
Volker
> On 13 Jun 2024, at 12:28, Corentin Bacqué-cazenave
>
/qheaderview.html#sectionSizeHint into account.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
changes should be ignored.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
atch this
next time.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
ntDatabase::addApplicationFont, with a font file you ship
separately or as a resource.
There's no API in Qt to install a font file with the system. Your application
might not have the privileges to do so, so if you need that, then you’d
probably best do that as part of your installation ro
ther. You can
keep your widget code and add Qt Quick via QQuickWidget to it already today.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
_doc.setTextWidth(-1);
_doc.setHtml("This is a test message");
return QSize(_doc.idealWidth(), _doc.size().height());
}
Sorry I can't release the full code as it does lots of other things like icon
decoration role, clicking on links in the HTML, etc.
Hope that helps,
Tony
Best regards
be which platform you see this on, and whether
you are running your UI on a display with a fractional scale level, as that
might result in rounding errors in the integer-based painting architecture of
Qt Widgets and QGraphicsView.
Volker
On 23 Nov 2023, at 16:28, Calogero Mauceri wrote:
Hi
when you call QApplication::quit()
yourself, I suppose.
Volker
> On 24 Oct 2023, at 20:30, Alexander Dyagilev wrote:
>
> Hello,
>
> No, it returns true always.
>
> On 10/23/2023 11:30 PM, Hamish Moffatt via Interest wrote:
>> On 24/10/23 06:10, Alexander Dyagile
ents?
>
> Hamish
They should; the window system event is handled as a spontaneous event and
should reach Q(Gui)Application::event with the spontaneous flag set; a call to
Q(Core)Application::quit sends (or posts, depending on the thread) the event as
a synthetic event to t
details
would be good.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
ast to and from void *, this should
be reproducible with small bit of code. And if you have that, then comparing
the assembly you get out of your compiler when targeting Intel vs ARM might
give some hints.
Volker
___
Interest mailing list
Interest@
le the ApplicationPaletteChange event in your
UI. You can then evaluate the value of QStyleHints::colorScheme API to decide
how you want to modify your style sheet.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/li
Cross-posting from the development list: anyone with an interest in Qt
TextToSpeech is welcome to the API review session on Monday 22nd afternoon,
16:00 Oslo time (CEST). Link to the MS Teams meeting, and to the new APIs we
plan to have in Qt 6.6, below.
Volker
> On 13 May 2023, at 14
can’t get it out as a QVariantMap anymore, and the code above will
print “QMultMap”, like it should.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Hi,
I hope some of you might be interested in joining this and, well, ask anything:
https://www.meetup.com/meeting-cpp-online/events/291796153/
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo
e the lineEdit is also after the tab widget).
And we need to allow that as a temporary state.
So as a stop-gap, don’t set the tab order to move from line edit to tab widget.
Volker
On 3 Mar 2023, at 19:42, Scott Bloom wrote:
Qt Creator? Never heard of it 😊 I use Visual Studio, but
tion to add such a
property to an object (and an item in a tree is generally not represented by an
object, it’s just data provided by the model).
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
solve that kind of problem. What that could look like
continues to be a subject of research. Ville has commented on that in the past
[1] and has recently played with Qt and sender/receiver (i.e. P2300), which got
even Eric Niebler excited [2].
Volker
[1] https://lists.qt-project.org/piperm
.
Volker
> On 23 Oct 2022, at 21:29, Volker Hilsheimer via Interest
> wrote:
>
> Thanks for pointing those out Bill, I did not have those helpers from the Qt
> 5 Extras on my radar. Will check where we are with those.
>
>
> Volker
>
>
>> On 21 Oct 2022, at
Legacy products will continue to be maintained with Qt 4.8 custom spins as
> well as Qt 5.x custom spins but no new development will occur using Qt. That
> has been the feedback from one and all.
Indeed, what your clients do or don’t do would be a lot more interesting if we
could assume that they get their information from someone who’s at least trying
to keep up ;)
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Thanks for pointing those out Bill, I did not have those helpers from the Qt 5
Extras on my radar. Will check where we are with those.
Volker
> On 21 Oct 2022, at 23:18, Bill Jones wrote:
>
> Hi Volker,
>
> Another missing module in Qt 6.x that is very important to desktop
s, but if you were
happy with things in Qt 5, then the types in Qt5Compat as they are are
perfectly fine to use.
[2] https://www.qt.io/blog/introducing-qt-quick-effect-maker
So, unless you depend on Qt Location, there’s no point in waiting. And if you
do - we’ll soon share mor
oes that. It relies on private
Qt APIs though.
There might be C++17-ways to simplify some of that using `if constexpr`, but
the basics will probably be the same.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
ull source for the widget can be found here
> https://github.com/towel42-com/SABUtils/blob/trunk/HyperLinkLineEdit.cpp
> https://github.com/towel42-com/SABUtils/blob/trunk/HyperLinkLineEdit.h
>
> Thanks.
>
> Scott
Hey Scott,
This should be a job for a QWidget::leaveEvent override:
https://doc.
can do is to get the visualRect of the last index, and
then calculate the view’s sizeHint based on that. That means that the tree has
to be fully expanded.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
> On 20 May 2022, at 21:05, Thorsten Glaser wrote:
>
> On Fri, 20 May 2022, Volker Hilsheimer wrote:
>
>> sending a synthesized wheel event with the Alt modifier set to the
>> QWidget will not trigger this behavior, as that never exercises that
>
> Hmm. I’m on
ctScrollArea.
Lastly, you probably don’t want to do any of this when the original wheel event
comes from a kinetic scrolling device (like a track pad), so check
QWheelEvent::phase and only do this when it’s Qt::NoScrollPhase.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
censes have expired,
are a huge step into the right direction.
[1] https://www.qt.io/faq/tag/qt-commercial-licensing
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Of course; I think there are a number of developers here that use Qt under an
Open Source license though, and perhaps even a few that, while having various
reasons not to use Qt under an Open Source license, still wouldn't mind
contributing with patches.
Volker
> On 24 Feb 2022,
ne answer to this was to move Qt under Open
Governance so that anyone could contribute to Qt and make sure that it stays
awesome also for domains that Nokia won’t care much about.
Evidently, the people commenting in this thread care deeply enough about Qt on
the desk
ong as the QtShaderTools is only used as a build
tool (as done with qtmultimedia), the fact that it’s not LGPL’ed doesn’t matter.
That we have LGPL’ed the module now with Qt 6.3 opens up possibilities to use
some of that code at runtime. But note that as of now, there are no public APIs
in the Qt
to do anything with it to configure and build Qt from source.
Volker
> On 6 Feb 2022, at 16:22, BeneschTech LLC wrote:
>
> So you guys put in a work around cmake as well...
>
> Ill be happy to compile the changes needed once I get linguist building. Just
> curious why th
ten software and ive only ever encountered
> issues with third party code. Indulge us old guys though. We have reasons we
> like traditional make and autotools.
Cheers,
Volker
> On Sun, Feb 6, 2022, 7:22 AM Bob Hood wrote:
> On 2/5/2022 4:15 PM, BeneschTech LLC wrote:
> > I h
s a preedit text in
the preedit area (underlined perhaps, or with a different background color),
and the compositor window will open to allow you to pick one of the several
glyphs that can be used (for instance, either 长 or 鬯).
So, this is important for complex input methods; but the preedit area i
as Thiago suggested, how do you then generate your make files?
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
QMenuBar is not a Win32 native menu bar, and neither is QMenu backed by a
native win32 menu. Windows knows nothing about their role in the UI (unless it
asks for it via accessibility infrastructure, but that’s unrelated to those
messages).
Volker
From
done to trigger those
permission dialogs).
Filed a JIRA ticket at
https://bugreports.qt.io/browse/QTBUG-97408
Thanks,
Volker
> On 9 Oct 2021, at 22:08, Alexander Carôt wrote:
>
> P.S.: see below – in that regard I compiled the camera example (Qt6.2) and
> ran it via clickin
$$$ to The Qt Company, then I’m sure we can discuss a
special Qt 6 version for you that runs on Windows 7. It’s not going to be
cheap, but that’s also a choice a customer has to make.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
d matches the original font in certain attributes (for
instance, proportional font, or serifed font). The quality of the glyphs in the
font Qt choses for you might then not be what you expect.
It’s best to explicitly select the fonts you want for the
eems like there’ll be an entry in the registry for your application, such as
HKLM\Software\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers\your_application.exe
or
HKCU\Software\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers\your_application.exe
that you can query.
Cheer
o something about it… that’s a bit much.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Appreciated.
For commercial license holders, contacting our support team is the right
approach to get issues impacting your product flagged.
Cheers,
Volker
> On 3 Sep 2021, at 16:54, Crocker, William wrote:
>
> I gave you money.
> That is my contribution.
>
>>
>
odeURIComponent in proper
> places...
>
> I think this is a must to fix bug for upcoming Qt 6.2 :)
We’re all looking forward to your contribution!
https://wiki.qt.io/Qt_Contribution_Guidelines
Cheers,
Volker
___
Interest mailing list
Interest
Hi Alexander,
I recommend the following blog post from Lars about some of the significant
changes we made to Qt Multimedia for Qt 6:
https://www.qt.io/blog/qt-multimedia-in-qt-6
Cheers,
Volker
> On 25 Aug 2021, at 15:02, Alexander Carôt wrote:
>
> Hi Juha and Jérome and all,
&g
decent amount of traffic on the IRC/Matrix channels.
These emails, and the “QThreadPool” discussion over the last days, indicate at
any rate that no traffic is disappearing due to system failures.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
the Qt
Company.
If that’s functionality you care about, then perhaps it’s an opportunity to
pick it up and see what it takes to port it over.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
>
>>> On Fri, Jun 11, 2021 at 10:05 AM Volker Hilsheimer
>>> wrote:
>>> > On 11 Jun 2021, at 13:52, Turtle Creek Software
>>> > wrote:
>>> >
>>> > Here's more info on the weird QTableWidget problem we're se
the Alpha is around the corner as well. Early feedback to
those (and several other changes and fixes to Qt Widgets from the last couple
of weeks [1]) would be most welcome.
Cheers,
Volker
[1]
https://codereview.qt-project.org/q/is:merged+branch:dev+path:%255Esrc/widgets/.*+after:2021-05-31
c, char **argv)
{
QApplication app(argc, argv);
QTableWidget table(10, 10);
table.setCellWidget(5, 5, new CellWidget);
table.show();
return app.exec();
}
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
ignores them to let them propagate through
the hierarchy).
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
away with a minimal change for ExtendedSelection.
There’s no intention to bring those changes to Qt 5.
Volker
> On 28 May 2021, at 19:01, Elvis Stansvik wrote:
>
> Yea man, just change it. No one remembers a coward! :)
>
> Den fre 28 maj 2021 kl 17:07 skrev David M. Cotter :
,
Volker
> On 28 May 2021, at 16:00, Volker Hilsheimer wrote:
>
> This seems unrelated, since the JIRA ticket predates both 5.11 and 5.15, so
> while it does sound like a regression that you’re welcome to report, it won’t
> help me with deciding about this particular issue.
>
>
This seems unrelated, since the JIRA ticket predates both 5.11 and 5.15, so
while it does sound like a regression that you’re welcome to report, it won’t
help me with deciding about this particular issue.
Cheers,
Volker
> On 28 May 2021, at 15:30, Olivier B.
> wrote:
>
> Here,
Cross-posting from the development mailing list in case any of you have a
strong opinion about this.
Volker
> On 28 May 2021, at 13:10, Volker Hilsheimer wrote:
>
> Hey Widget fans,
>
> I need your opinions on https://bugreports.qt.io/browse/QTBUG-59888
>
> The
(w);
> #endif
> }
> ```
>
> Cheers
> --
> Nicholas Yue
As the name suggests, QOpenGLWindow is a QWindow, and QWindow’s are designed to
be top level windows.
To embed an OpenGL rendering surface into a widget-based UI, you should be
looking at QOpenGLWidget instead:
https://doc.qt.io/qt-6/qopenglwidget.html
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
.
Cheers,
Volker
> On 30 Apr 2021, at 17:20, Jason H wrote:
>
> Not to Jeffery specifically,
>
> I have mixed feelings about the whole situation. I think Roland is right, or
> at least has a valid point most of the time, even if it is technical or
> limited to a specific
We currently have no specific plans to make QWidget render through RHI, and
neither the video nor my earlier emails suggest that this is on the roadmap. It
generally makes very little sense to draw with a pen into a freshly wiped out
Vulkan surface 60 times per second.
Cheers,
Volker
>
or breaking a lot of code out there, and still not given us the UI
components we would have needed.
I’m sure there are opportunities to share more code between widgets and quick
world esp on the UI framework classes, and with Qt 6 we have taken some steps
into that direction. But whether
g *with* Qt.
The development *of* Qt, which patching of QJSEngine would qualify as, is best
discussed at
https://lists.qt-project.org/listinfo/development
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
> Em 15/04/2021 11:57, Volker Hilsheimer escreveu:
>>> On 15 Apr 2021, at 12:25, Rui Oliveira wrote:
>>>
>>> Hey,
>>> As per the title implies, I would like some comments on the GUI offerings
>>> Qt currently has.
>>>
>>> I
ontinue to work and look great on future
versions of the various operating systems as well. There’ll probably always be
applications for which the widget concepts are a perfect fit.
For an increasing amount of applications and environments however, Qt Quick
provides the better architecture,
e existing paint engines, and not use QRhi.
So the best option for you is to not use the QOpenGLWidget viewport on iOS,
based on your experience that it’s slower than the default software rasteriser.
Regards,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
rs ago to support Windows XP menu animations
in Qt is probably not a shiny example of robustness.
But most of it is pretty good, even some of mine, and it makes me proud to have
been able to contribute to Qt and to work with the incredibly talented people
in the Qt community for most of my prof
check what The Qt Company can
provide as a commercial service that fits their needs.
Perhaps that happens frequently already. That would explain the recent
development of the Qt Company stock price...
Volker
PS: Roland, I was looking at your
https://www.theminimumyouneedtoknow.com/agile_book.ht
> On 24 Mar 2021, at 15:06, eric.fedosej...@gmail.com wrote:
>
> From: Interest On Behalf Of Volker
> Hilsheimer
> Sent: Wednesday, March 24, 2021 4:06 AM
>
>> For feedback regarding the licensing changes made that context (including
>> 5.15), I’d suggest you g
ing useless
> QML needing to be ripped out.
Don’t use it.
I don’t consider this substance. Go back to the original thread if you want to
spread FUD, Roland.
I started a new one were we can focus on substantial and constructive
conversation about what needs to be brought back to make Qt 6 better and
porting easier.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
> On 24 Mar 2021, at 08:43, Max Paperno wrote:
> On 3/23/2021 11:44 AM, Volker Hilsheimer wrote:
> ...
>> I personally wonder why people that never want to change what they built
>> last year want to develop software development. Isn’t that what makes
>> building stu
why people that never want to change what they built last
year want to develop software development. Isn’t that what makes building stuff
out of bits and ideas so much more interesting than building stuff out of
sticks and stones?
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
ulted in more churn - but also in good feedback. Either
way, it is perhaps not the most representative porting experience.
Roland, if you have specific 1st hand porting experience to share and
constructive contributions to make about which APIs we should bring back
because, then please do so.
Cheers,
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
> On 20 Mar 2021, at 01:14, Thorsten Glaser wrote:
>
> On Fri, 19 Mar 2021, Volker Hilsheimer wrote:
>
>> Do you have any particular classes in mind?
>
> There’s the deprecation of QApplication::desktop()->screen()->winId()
> which is necessary for comman
> On 19 Mar 2021, at 14:34, Roland Hughes wrote:
>
>
> On 3/19/21 7:51 AM, Volker Hilsheimer wrote:
>>> On 19 Mar 2021, at 12:12, Roland Hughes wrote:
>>>
>>>
>>>
>>> On 3/19/21 6:00 AM, Giuseppe D'Angelo wrote:
>>>&
cases, but the porting experiences I’ve
read so far suggest that by and large it has been a rather decent experience.
Do you have any particular classes in mind?
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Drag events are related to Drag’n’Drop, and you rarely drag from or drop onto a
scroll bar.
The Qt documentation is quite clear about the role of those event types, I
think:
https://doc.qt.io/qt-5/qevent.html#Type-enum
https://doc.qt.io/qt-5/qdropevent.html
Volker
> On 24 Nov 2020, at
data structures
(which the code does anyway, in verifying that there is a DISPLAY environment
variable), or pass a pointer to (or index of) a QScreen if you want to place a
UI on a specific display.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
the event loop implementation on Windows in Qt 5.15,
such as
* 81408c0e76616b127c46779dc14bbcf084a3d87b
* e0d80167c18b5a71acf4dac59f3e6f37292fa397
to better the integration with foreign event loops, but you should updating to
5.15.1 which has e.g
fb6f62354ff8d29152db7cfa479b2689a25ae7a9 which fixe
r to #include the inl file in the hpp file? That way you
still have separation of declaration and definition on a file-level, but don’t
expose users of your C++ headers (including moc) to your way of organizing
things.
Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
You have to show widgets that you add to parents that are already visible.
Cheers,
Volker
From: Interest on behalf of Carlos Agon
Sent: Saturday, June 20, 2020 10:28:46 AM
To: interest@qt-project.org
Subject: [Interest] adding widget into a mousePressEvent
very much appreciated.
Cheers, Volker
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
pcre -plugin-sql-sqlite -plugin-sql-odbc -make-tool
jom > ConfigureOutput_msvc2019.txt 2>&1
jom > BuildOutput_msvc2019.txt 2>&1
Python, Perl, and Ruby are installed and in the PATH.
Is this a valid method to build Qt or should I try a different recipe?
As I always stru
seem somewhat related although they should have been resolved in my
Qt 13.0 beta version or do not apply anymore.
Are those bugs still present? And if they are, is there a workaround?
Cheers, Volker
--
___
Interest mailing list
Interest@qt-project.org
Thanks Allan and Alexandru!
The build is running ...
Cheers, Volker
Am 25.04.2019 um 10:59 schrieb Allan Sandfeld Jensen:
On Donnerstag, 25. April 2019 10:28:42 CEST Volker Enderlein wrote:
Hi,
when building Qt and WebEngine separately (i.e. not doing an embeddd
build), do I need to
1 - 100 of 141 matches
Mail list logo
