the range API directly on QRangeModel
instead? E.g:
QRangeModel model({1, 2, 3, 4, 5});
listView.setModel(&model);
model.erase(model.begin());
model[0] = x;
model.push_back(y);
-Richard
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Hi,
I would like to request for a new repository:
Name of the repository: qt-labs/figma-style-generator.git
Description: A tool for generating Quick Controls styles from Figma designs
Responsible person: Richard Moe Gustavsen
Gerrit user/email: Richard / richard.gustav...@qt.io
The UI Team has
+1
-Richard
> On 29 Nov 2024, at 22:29, Shawn Rutledge via Development
> wrote:
>
> I’m nominating Oliver Eftevaag as the maintainer of Qt Quick Dialogs. He was
> instrumental in the process of rewriting the old version to use Qt Quick
> Controls 2 and refining the API th
h the Qt source code)?
-Richard
*: This probably comes from the time when Controls was a separate repository,
and couldn’t be used by Declarative.
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
+1
-Richard
On 30 Jan 2024, at 13:11, Paul Tvete via Development
wrote:
Hi,
I would like to nominate Matthias Rauter as an approver for the Qt Project.
Matthias has been working on Qt for more than a year now. In this time, he has
done great work on Qt Location and Qt SVG, among other. I
reat addition to the public interface.
Create task for it. And then anyone that disagrees or have alternative
proposals can comment on it.
-Richard
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
that has children in the original source model (since you don’t want to include
the parent nodes, I take it).
-Richard
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
.
-Richard
> On 20 Sep 2023, at 20:31, László Papp wrote:
>
> Yes, I have tried that, thanks.
>
> bool TableProxyModel::filterAcceptsRow(int sourceRow,
>const QModelIndex &sourceParent) const
> {
> QModelIndex index = sourc
+1
Richard
20. jun. 2023 kl. 20:58 skrev Jan-Arve Sæther via Development
:
Hello all,
I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt
project.
Santhosh is a member of the UI Team, and has been working on improvement to our
styles, dark mode support, palette
put. I’m sure you’re not alone in thinking that the
order of the arguments should have been swapped from the start. Feel free to
create some JIRA tasks and assign them to me, so that we can keep track of
suggestions and other things that should ideally be changed.
-Richard
https://codereview.qt-project.org/c/qt/qtdeclarative/+/449862
-Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
e
arguments got swapped in the process, exactly to be consistent with the rest of
the TableView API (that is, the two other functions that takes a column and a
row as argument. Changing that back in Qt 6.5 wouldn’t help much, since we
would still end up with a Qt version that is different
base class (TableView),
> and the arguments swapped for it, so now it's
> TableView::modelIndex(column,row).
That is a problem, yes. Good catch. Not sure how that sneaked in, but it needs
to be fixed. But this doesn’t require an exception to the FF, we can surely fix
up th
+1
Fra: Development på vegne av Eirik
Aavitsland via Development
Sendt: mandag 5. desember 2022 11:05
Til: development@qt-project.org
Emne: Re: [Development] Nominating Axel Spoerl as approver
+1
On 12/5/22 10:57, Volker Hilsheimer via Development wrote:
> Hi,
Nice. I'm a bit surprised file_name() returns a char* rather than a
std::filesystem::path, but it'll do. It's also nice to see
source_location has a function_name() that can finally unify the
disparate ways of getting that information.
The advantages are for instance that file_name() does
> 1. Value types are passed by value
> 2. Everything is a reference
Most languages have a way to specify this in the signature. Swift has the
“inout” keyword, c# has “ref”. Have you considered this as an option as well?
BR,
Richard
___
Devel
+1
-Richard
> On Jun 13, 2022, at 9:19 AM, Frederik Gladhorn wrote:
>
> Hello :)
>
> I've lately not had time to contribute to Qt (personal life keeping me busy).
> Since Volker and others did a great job porting Qt Speech to Qt 6, they know
> the code better than
This has now taken effect, and the Wiki has been updated
(https://wiki.qt.io/Maintainers).
Congratulations Volker!
Best Regards,
Richard Moe Gustavsen
Principal Engineer
The Qt Company
Oslo, Norway
On 25 Jan 2022, at 09:38, Richard Gustavsen
mailto:richard.gustav...@qt.io>> wrote:
Hi a
+1
-Richard
> On 1 Feb 2022, at 11:08, Eirik Aavitsland wrote:
>
> +1
>
> On 2/1/22 10:50 AM, Gatis Paeglis wrote:
>> Hi all,
>> I would like to propose a change in Qt's Linux/XCB maintainership.
>> Since 2019, I have moved full time to the Qt for MCUs pr
out maintaining the
module for a long time already. So let’s make it formal as well!
[1] https://wiki.qt.io/Maintainers#Qt_Maintainers
[2]
https://codereview.qt-project.org/q/owner:volker.hilsheimer%2540qt.io+repo:qt/qtbase+status:merged
Best Regards,
Richard Moe Gustavsen
Principal Engineer
The
+1
Richard
On 20 Dec 2021, at 16:35, Tor Arne Vestbø
mailto:tor.arne.ves...@qt.io>> wrote:
Hello all,
I’d like to nominate Morten Sørvig as maintainer of high-DPI in the Qt Project
[1].
Morten has been instrumental in the development of Qt’s high-DPI support, and
has been the de-
+1
Fra: Development på vegne av Paul Wicking
Sendt: onsdag 27. oktober 2021 12:09
Til: Volker Hilsheimer
Kopi: development@qt-project.org
Emne: Re: [Development] Nominating Doris Verria as Approver
+1
> On 27 Oct 2021, at 11:56, Volker Hilsheimer wrote:
>
>
+1
Fra: Development på vegne av Shawn
Rutledge
Sendt: onsdag 27. oktober 2021 10:34
Til: development@qt-project.org
Emne: Re: [Development] Nominating Oliver Eftevaag as Approver
+1
On 2021 Oct 27, at 06:25, Paul Wicking
mailto:paul.wick...@qt.io>> wrote:
Hi
nor has the person contributed to the codebase during
the last couple of years.
The question is whether this is an abuse of approver rights.
This is a relevant question for the Qt project. Any person with approver
rights has the ability to cause a production stop. Ivan is asking for help
in t
hat would be beneficial for everyone and lower the utilization
of download.qt.io.
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> Right. That will become an issue in 4 months when GCC 11 ships with its
> internal
> header-dependency refactorings, breaking all sorts of Qt code, and
> that will then
> bubble down to various distro downstreams during this year and next. Then
> again,
> distro packagers can hopefully handle t
er with a couple of tabs open to look up
> bugs and code changes.
> Yep, same here.
Would it be better if we required all commits to have a ChangeLog entry, so
that no one
forgets? And if your commit shouldn't be in the log, you need to state that
expli
Company's position regarding conan-center?
Thanks
BR
Richard Weickelt
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> Still waiting for instructions on how to do an unattended installation of a
> binary Qt.
While you are waiting, have you seen those pages?
- https://www.qt.io/blog/qt-online-installer-4.0-pre-alpha-released
- https://wiki.qt.io/Online_Installer_4.x
Bonus:
- https://pastebin.com/jUN51zci
May
> Oddly enough, continued support for the Free Software ecosystem around
> Qt is one of the things most of us who work here care about deeply, so
I have no doubts that Qt engineers do. I can see this in in every code reciew
and I appreciate it very much!
> Our management, in any case, knows full
customized. I
have not tried it.
> That's why I asked last month (and still have no official reply) on how
> the Qt Company suggests we use Qt in public CIs, if the binary build is
> locked to Qt Accounts.
Do you seriously expect to get a reply? Are you a paying customer?
Richard
__
validation of the Code Review workflow and keep
your external contributors up-to-date on GitHub."
I haven't tried it though. Does it work? Maybe there is a project on
https://review.gerrithub.io/ where you can see github PR syncing in action.
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
elevant.
You could also contribute to https://github.com/bincrafters/conan-qt and ensure
that it is properly working and pre-built binary packages are available. It
would be in the best interest of the Qt project and thus also of the Qt company.
>> Maybe you all have great ideas that we missed though. What kind of change do
>> you think would give companies a really good reason to buy a license, without
>> at the same time hurting the community?
I wonder if selling per-developer licenses is still a sustainable business
model at all. We a
> - Product repo contains a Conan recipe. Conan takes care of
> getting/building the dependencies.
That sounds interesting. Will the QtCompany use Conan as _the_ package
manager for the market place and Qt6? Is there more information available?
Thanks
R
uge difference.
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ate. Languages like Go and Rust are are popular for a reason.
I can't blame the Qt company for not doing this, but I think that an
easy-to-use CI service for Qt applications with a Qbs-alike QML-ish DSL
could have given QML as well as Qbs much more traction. Oh well...
Richard
___
> You can download snapshot via online installer. At the moment we don't publish
> separate src packages to download.qt.io
Thanks, but I can't see any Qt snapshots in the online installer. Some of the
"preview" packages there are even outdated.
This is what I see: https://pasteboard.co/Iz16Exp.pn
> I guess that building Qbs in Coin is the only way to build against unreleased
> Qt versions.
How much effort would that be to set up and to maintain for an external
contributor? Any experiences?
___
Development mailing list
Development@qt-project.org
customers only?
Thanks
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Hello,
I've been trying to use windeployqt from a cross-compiled (mingw-w64 on
Linux) Qt. I must be the only person on the planet doing this because there
is a bug in windeployqt preventing it. The PE functionality is guarded by
Q_OS_WIN.
https://code.qt.io/cgit/qt/qttools.git/tree/src/shared/winu
Hi Volker,
A few comments - I wrote the original policy and I'm happy that you're
taking the time to evolve it:
> In addition, we have also been discussing a few aspects in The Qt Company
> where we would like to see the policy evolve, such as:
>
> * the integration of CVE handling into the pro
is so
ugly (Doxygen is even worse) that I even prefer to write API documentation
directly in rST/Sphinx.
Best regards
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Tue, 18 Jun 2019 at 17:02, Thiago Macieira
wrote:
> We have them because we made a mistake when we added SHA3 support. We've
> kept
> them for compatibility, for people who had hashes to compare to and had
> accidentally used Keccak.
>
>
Yes, we should deprecate this.
Rich
___
>> Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship
>> icu. It uses either the one provided by the system or a thin replacement
>> resulting in a reduced localization feature set according to
>> https://wiki.qt.io/Qt_5_ICU#Design_Principles
>
> Linux binaries are shipped
me library path to the Qt
libraries.
I thought that "." is always implicitly the first path where the run-time
linker looks for (other)libraries. So I don't understand why it is set
explicitly.
Richard
___
De
kaging
so I rather used the ones from the COIN logs.
Could somebody explain why the Linux release explicitly specifies "-R ." as
configure option? I have never seen that being used before.
Richard
___
Development mailing list
Development@qt-p
uot; to
bring this post up:
https://lists.qt-project.org/pipermail/interest/2019-January/032221.html but
it seems like google hasn't even indexed it.
> The answer is here:
>
> https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld
Hi,
where can I find the configure command lines that have been used for Qt
binary releases provided at https://download.qt.io/official_releases/qt/ ?
Is there also more information available about the environment they have
been built on? I am particularly interested in the Linux release.
Thanks
> - People nowadays will just use the flatpak / appimage / snap / whatever
I can see how that works for single-binary GUI applications.
Do you know any example for a complex Qt-based multi-binary (preferably
command line usage) application that does that well?
__
click
every other day. The old gerrit was certainly ugly, but it felt much more tidy.
I would be very happy if someone with UI experience could clean up the
stylesheet. :)
Thanks
Richard
___
Development mailing list
Development@qt-project.org
https:/
> This was a case where I thought it is obvious already. The definition of
> "Done" (given by Thiago earlier in this thread) has not applied for a
> long time anymore. There hasn't been maintainer for a long time. I
> understand this leave use cases in the dust but this can only by averted
> if so
On 10.04.2019 23:21, Marco Bubke wrote:
> Sounds you want flatpak. ;-)
All those run-time extracted application container formats might be nice
solutions for GUI applications which is apparently the main target of Qt.
But my observation is that they perform rather poorly when being used for
comman
> You may need to do custom steps on artifacts produced by windeployqt before
> packing them, so it's better to have separate tools for "bundling" and
> creation
> of actual packages.
Well, that's easily solved. The "tool" doesn't need to do everything on a
single invocation which leaves enough
at I could
propose for Qbs. Not using gerrit is not an option. But the Qt Company seems
to lack of an easy-to-use CI solution for this kind of project and the
current amount of contributors.
Richard
___
Development mailing list
Development@qt-projec
wer that can be cumbersome.
>> Collecting "resources that the application uses (like [...]
>> graphics, [...]" *and dependencies* would be a (important)
>> step, but not all that it takes.
>
> By this logic windeployqt should produce .msi
Hi,
I would like to know more about https://git.qt.io
- What's the purpose and the future plan?
- Is it available to registered users at qt.io ? I couldn't log in.
- Is it connected to gerrit or can it be connected?
- Does it offer gitlab CI?
Thanks
Best regar
> But do note that our parallelism isn't that bad right now. There's a long
> critical path before parallel things can currently be built, but once QtQml
> is
> built, the number of jobs that can be launched in parallel is very big. What
> doesn't need that build isn't very large.
Could you e
like Conan to provide third party
dependencies as well as Qt modules in source and prebuilt binary form? That
could solve the availability issue and would probably simplify the build flow
as well.
https://conan.io
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
s during the last years.
Future: Unclear. Jochen was so kind and made a vague declaration of intent
here https://lists.qt-project.org/pipermail/qbs/2018-October/002270.html
At least for keeping Qbs integration in QtCreator at the current level.
Richard
> On Sunday, 16 December 2018 20:12:47 PST Richard Weickelt wrote:
>> ... and if you cross-compile, you definetly don't want to your build system
>> to stick its nose into your system librararies on any platform.
>
> No, you really DO. The issue is what "system
my stuff done with low
investment, hence I often use Qbs ;-)
Richard
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
t-project.org/#/q/reviewer:%22Christian+Ehrlicher%22,n,z
Br,
Richard Moe Gustavsen
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ore inviting character. Next step could be maybe a meeting with community
members where we would clarify how the commitment of the TQtC looks like. I
am sure that there are many open questions.
Thank You
Richard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> It seems to differ quite a bit in scale. That blog post has 7 comments.
> Compare it to nearly 150 on "Deprecation of Qbs" in 3 days and countless
> emails here on the mailing list. I seem to wonder if the whole issue
> could be avoided if it was approached a bit more diplomatically from the
On 30.10.2018 18:14, NIkolai Marchenko wrote:
> For anyone interested in QBS survival, let's fill the sheet with QBS
> ecosystem.
> Maybe if we show TQtC that people are actually using it they will reconsider.
>
> Post your projects (and ones you know of) here:
>
> https://docs.google.com/sprea
> Can you name any project of moderate complexity using it?
https://github.com/bjorn/tiled
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
;t want to miss out on the productivity gains I've made with Qbs, but
on the other hand I have very little free time. However, I would voluntarily
contribute to the documentation of Qbs.
Richard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
lined version.
-Richard
Fra: Development
på vegne av Edward Welbourne
Sendt: mandag 22. oktober 2018 11.52.52
Til: Christian Ehrlicher
Kopi: development@qt-project.org; al...@qt-project.org; Thiago Macieira
Emne: Re: [Development] Un-inlining members allowed
>> How much custom c++ code does it contains for just qt?
>
> which build system which supports automatic calling of moc doesn't have
> specific code for qt ?
Qbs :-)
At least no C++ code.
___
Development mailing list
Development@qt-project.org
http://
f those modules would most likely not be Qt
- it would be possible to deduce, which features the QML
application actually uses so that unused functionality can be
dropped at build-time.
I would be interested in other opinions. Maybe I am on
//codereview.qt-project.org/#/c/228027/>-Richard
Fra: Development
på vegne av Frederik Gladhorn
Sendt: 2. mai 2018 11:09:40
Til: development@qt-project.org
Kopi: Thiago Macieira
Emne: Re: [Development] Consistently flaky test QTabWidget test
On onsdag 2. mai
I'll take a look!
-Richard
Fra: Development
på vegne av Thiago Macieira
Sendt: 2. mai 2018 09:46:40
Til: development@qt-project.org
Emne: Re: [Development] Consistently flaky test QTabWidget test
On Wednesday, 2 May 2018 00:29:18 PDT Thiago Macieira
+1
On 21 March 2018 at 12:00, Edward Welbourne wrote:
> Lars Knoll (21 March 2018 12:49)
> > He isn’t an approver yet? I agree, that we should change that :)
>
> My thought entirely !
>
> +1,
>
> Eddy.
> ___
> Development mailing list
> Develop
On 6 March 2018 at 14:06, Kevin Kofler wrote:
> Mitch Curtis wrote:
> > https://codereview.qt-project.org/#/c/221758/ makes
> > QObject::dumpObjectTree() and QObject::dumpObjectInfo() invokable so that
> > they can be used from QML.
>
> Would this have any security impact? I'm thinking of issues
On 14 February 2018 at 11:36, Konstantin Ritt wrote:
> Can we have both OpenSSL 1.0.x and 1.1.x supported when configured with
> -openssl-runtime and choose 1.0 or 1.1 with -openssl-linked? Anyhow?
>
>
No.
Rich.
___
Development mailing list
Developme
Thanks for all your hard work, and good luck for the future Jake
Rich.
On 9 February 2018 at 20:14, Jake Petroules wrote:
> Steve Jobs once said:
>
> > “I have looked in the mirror every morning and asked myself: "If today
> were the last day of my life, would I want to do what I am about to
On 8 February 2018 at 18:45, Thiago Macieira
wrote:
> As $SUBJECT says.
>
> Only for 5.11 onward, so shouldn't affect the 5.6 and 5.9 LTS (which don't
> have OpenSSL 1.1 support anyway) or any 5.10.x releases still to come.
>
> As a bonus side-effect, users who hadn't realised they have an old,
>
On 18 January 2018 at 10:07, Konstantin Tokarev wrote:
>
>
> Heap corruption can be detected with lots of existing tools, e.g. ASAN. It
> also won't be left unnoticed until it's too late, unlike memory leaks which
> may suddenly pop up when amount of data increases.
>
> Debugging out of memory co
s.
If you think that your new widget set /style cannot conform to this, then it
should probably be shipped outside Qt5.
-Richard
Fra: Development
på vegne av Konstantin Tokarev
Sendt: 30. oktober 2017 15:21:22
Til: iman ahmadvand; Qt development mailing list
Resend from the right address
On 16 October 2017 at 18:38, Richard Moore wrote:
> I need to polish up my code showing how to add in additional openssl
> features. This can be used to extend it's support without bloating
> qtnetwork or qtbase.
>
> On 13 Oct 2017 8:44 am,
There are also some http servers that I've written. I think requirements
should include:
- Extensible
- Easy to support SSL/TLS
- Support for client certs
I think we talked about some of this at least years network summit...
Cheers
Rich.
On 6 October 2017 at 17:21, Harri Porten wrote:
>
> On
Hi folks,
I try to write special 3D viewer in C++ for geomtry data. For testing
purpose, I create hundreds of simple cube entities. I wrote my own
shader and create a new shared material to all of the cube entities.
The Effect of the material contains already two general parameters that
I can
On 11 July 2017 at 22:13, Marc Mutz wrote:
> On 2017-07-08 00:39, Matteo wrote:
>
>> Hi all,
>>
>> I just finished the first preview of my QAESEncryption class and I
>> would like to have some opinions on possible improvements, issues etc.
>>
>> https://github.com/bricke/Qt-AES [1]
>>
>> This is
Thanks Frederik! A short introduction to myself: My name is Richard, I started
at Trolltech in 2006, which means that I've been working with Qt for more than
ten years. Most of that time I've been looking into issues on macOS, but after
the Nokia era, I became a part of the team im
On 8 March 2017 at 10:37, Kai Koehne wrote:
> > -Original Message-
> > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> > project.org] On Behalf Of Richard Moore
> > Sent: Tuesday, March 07, 2017 10:44 PM
> > To: Lars Knoll
> >
>
>
> You're right. My wording above was misleading, I wasn't present myself.
> This is what I remembered people telling me afterwards.
>
> Here are the session notes: https://wiki.qt.io/Qt_
> build_systems_at_QtCon_2016
>
>
Yep, there's also a video. My recollection is that there was a small voca
On 7 March 2017 at 21:21, Lars Knoll wrote:
>
> > On 7 Mar 2017, at 21:54, Thiago Macieira
> wrote:
> >
> > Em terça-feira, 7 de março de 2017, às 21:37:46 CET, Richard Moore
> escreveu:
> >>> The Qt Company has now very recently made a decision to
On 7 March 2017 at 19:12, Lars Knoll wrote:
> Hi,
>
> Thiago's right that there has not been a formal decision in the Qt project
> about the build system to use for Qt 6. So saying qbs will be the build
> system for Qt 6 is getting a bit ahead of things.
>
> But we have had many discussions in th
On 3 March 2017 at 11:33, Marc Mutz wrote:
> On Friday 03 March 2017 10:43:56 Richard Moore wrote:
> [...]
> > QSslCipher should be an integer index into a table. The
> > fact that it isn't is a poor workaround for weak API from openssl
>
> Would you mind to expa
On 3 March 2017 at 07:30, Marc Mutz wrote:
> Bad example: QSslCipher. Look at all the messy API that just deals with the
> fact it's pimpled. That class is particularly hideous because it allocates
> memory on every copy!
>
>
Please avoid using the SSL code as the example since you don't really
On 30 October 2016 at 09:03, Sean Harmer wrote:
> What can we do in terms of pre-compiled release builds of Qt? Is it
> feasible for us to distribute the runtime lib required by the plugin from
> the fbx SDK? Or do we need to find some other solution such as build the
> plugin for the release pac
On 26 September 2016 at 10:38, Giuseppe D'Angelo
wrote:
> Il 25/09/2016 05:58, Thiago Macieira ha scritto:
> anyhow). Plus, the mere existence of that page means that someone is
> relying on the binary format.
>
IIRC it was added to allow DCOP to be used in non-Qt contexts.
Rich.
Hi All,
As some of you may know, I'm planning to step down as maintainer of Qt
Network. This is because now that the Qt company has people in a position
to work on the network stack full time I think it makes much more sense for
them to be the maintainer - it doesn't mean I'll be moving away from
On 12 August 2016 at 11:40, Fredrik de Vibe wrote:
> Hi all,
>
> We have recently been working on an implementation of OAuth (1+2), and
> this is now approaching a state in which it can be distributed as a tech
> preview. For this we'll need a new public repository.
>
>
+1
> The main reason
On 26 July 2016 at 22:33, Henry Skoglund wrote:
> Hi, most likely I've had too much coffee, but has anyone checked if these
> intermittent crashes are due to outside DDOS/some trying to introduce a
> race condition and injecting new code into Qt's codebase?
>
The CI machines aren't internet acc
On 13 July 2016 at 19:10, Marc Mutz wrote:
> Renaming a public inline function of a non-exported class is BC, but SiC
> Type
> (b), so not acceptable.
>
Good analysis, however isn't the compiler allowed to not inline stuff too
which would mean this example is not b/c either.
Cheers
Rich.
On 29 April 2016 at 20:14, Allan Sandfeld Jensen wrote:
> On Friday 29 April 2016, Thiago Macieira wrote:
> > See https://lists.clearlinux.org/pipermail/dev/2016-April/000290.html
> >
> > This is yet another reason we have to stop bundling third party
> components,
> > especially the image and mo
On 18 April 2016 at 10:54, Sean Harmer wrote:
> Hi,
>
> It seems the certificate installed for the above site is incorrect. It
> reports
> itself to be for *.qtcloudapp.com.
>
Yep, the cert is not valid for this domain. Also note that it expires in
approximately 1 month, so now would be an exce
+1
On 30 March 2016 at 09:34, Sean Harmer wrote:
> Hi All,
>
> I'd like to nominate Volker Krause for approver status. Volker is one of
> the
> main authors of GammaRay, is very active in the Qt Automotive sphere where
> he
> leads up KDAB's contributions, and has touched many parts all over Qt
1 - 100 of 273 matches
Mail list logo
