Re: [Development] Add QTBUG title to new release changelog

[Julius Bullinger]

On 05-Mar-21 10:46 AM, Roland Winklmeier wrote:

Good morning,

I was curious to see what changed in Qt 6.0.2 release and found a list 
of fixed QTBUGS:


[qtbase]
443ce5d073 Fixes: QTBUG-89578
b61275ee72 Fixes: QTBUG-90042 
e255716291 Fixes: QTBUG-74088


The QTBUG number itself does not tell me much, hence it is very hard to 
predict if anything relevant is in that release affecting my projects.

How hard would it be to change it to

[qtbase]
443ce5d073 Fixes: QTBUG-89578 QLineEdit Cursor show white line when use 
property of setInputMask
b61275ee72 Fixes: QTBUG-90042 QIcon not using Hi DPI pixmap version
e255716291 Fixes: QTBUG-74088 Menu Bar Items Disabled When QMainWindow Has 
Window Modal Child and Another Window Made Active

That would be much easier to read.


I very much second this request. Also, most of the bugs mentioned as 
fixed in the 5.15.3 release notes don't have the respective Fix Version 
set in Jira (or any Fix Version, for that matter).


That means commercial customers must now cross-reference each and every 
issue ID in the release note with the ones they reported/that affect 
them to see if they have been fixed.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Proposal: Deprecate QVector in Qt 6

[Julius Bullinger]

On 23.04.2020 16:45, Giuseppe D'Angelo via Development wrote:

== Naming of functions and types if QList = QVector ==

We have QStringList, QVariantList and friends, which are aliases / 
subclasses of QList and so on.


Should they become QStringVector, QVariantVector; and the *List names 
stay, aliases for the *Vector names, mirroring QList and QVector 
themselves?


Another suggestion: Get rid if the aliases; use the fully-qualified 
types instead.


I'm always irritated if I open the documentation of QVariantList from 
within Qt Creator, and land on the QVariant docu instead. I'm interested 
in the features of the container, not the contained type.


And I have to remember if QStringList is the same as as QList, 
or if it's actually a different container with a different API.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] CMake branch

[Julius Bullinger]

On 22.03.2019 09:58, Simon Hausmann wrote:


I think earlier last year we never considered this even, but today
the quality of the .pro file converter has made this a possibility
worth trying.


Is this converter available somewhere? We're currently planning to 
migrate a project from qmake to CMake, and evaluating the switch with 
such a converter would be a tremendous help!

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Qt Quick Templates 2 from C++

[Julius Bullinger]

On Feb 14, 2019, at 1:03 PM, Joe via Development
 wrote:


please unsubscribe me from your f.  g list


On 14.02.2019 22:20, Joe via Development wrote:

please fuc. g unsubscribeme from your fuk  g list i don’t have a
password as i didn’t join but a jerk asshole e put me here


No need to swear. You can unsubscribe without a password. Just go to 
https://lists.qt-project.org/listinfo/development, enter your mail 
address at the bottom, press 'Unsubscribe or edit options', and then 
'Unsubscribe' again.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Archiving is working

[Julius Bullinger]

On 15.01.2019 15:10, Sampo Heikkinen via Development wrote:

Quicker look to development archives shows that it should be
working now. At least my recent email can be found from archives.
It’s most likely that every email sent during these two weeks are gone
forever because file permissions. I will investigate this still though.


It's also mails that have been in the archive already that are now 
missing. For example, search for "site:lists.qt-project.org creator" on 
Google. Most of the links there that have been archived do not work 
anymore. This affects all lists, development, interest, qt-creator, qbs, 
and so on.

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Preventing link rot in Qt docs

[Julius Bullinger]

Il 07/12/18 13:46, Sze Howe Koh ha scritto:

This is a problem because the Qt docs are heavily cited in the forums,
the wiki, and external sites like StackOverflow.


On 08.12.2018 02:34, Topi Reiniö wrote:
> Redirects are now in place. We have also plans to implement better
> versioning for the online docs.
>
>
> \topi

Piggybacking on this: There's also many existing links pointing to the 
several qt-project.org servers. 
{bugreports,doc,downloads,wiki}.qt-project.org and qt-project.org/forums 
are the ones I encounter most, and only the non-encrypted HTTP URLs 
redirect to the new qt.io pages.


It would be really nice having redirects for https://*.qt-project.org 
URLs as well.


Regards,
Julius
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Who is in charge of qt-project.org?

[Julius Bullinger]

Hi Tuukka,

On 02.11.2018 13:44, Tuukka Turunen wrote:

Exactly. We are very pleased if there are people who start to
contribute to Qbs. So far it has been very little by others than
employees of The Qt Company.

We will continue maintaining Qbs so that it stays supported until end
of 2019 and also release a new version in April 2019 as promised.
Most likely Qbs remains usable a long time after support ends - even
without anyone from the community working on it.

This is a good opportunity for those interested in further developing
Qbs to step up and start taking it forward. We can help with the
reviews and provide the infrastructure. We can help even with new
releases, if there is enough interest to develop it further.


To be honest, that's not at all what the blog post at 
http://blog.qt.io/blog/2018/10/29/deprecation-of-qbs/ suggests:


> We have decided to deprecate Qbs and redirect our resources to
> increase support for CMake.
The keyword here being "deprecate". You're not saying "The Qt Company is 
pulling resources", you're saying "Qbs will go away, don't use it 
anymore" ("you" being TQtC). The first one would be fine, the latter one 
is a clear signal to stay away from it.


If Qbs is independent from TQtC (what the discussion here suggests), 
than TQtC is in no position to _deprecate_ it.



We probably should have opened the dialogue about the future of Qbs
during the process of thinking about the options. This would have
been good and fair towards the community.


I think TQtC has every right to say "we won't be 
supporting/funding/developing Qbs anymore" (as it seems to have happened 
with Qt Widgets IIRC), but announcing its deprecation is a completely 
different beast IMO.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Policy for examples with large resources?

[Julius Bullinger]

Hi Konstantin

On Friday, 27 January, 2017 at 17:48, Konstantin Tokarev wrote:
> 27.01.2017, 19:41, "Oswald Buddenhagen" :
>> On Fri, Jan 27, 2017 at 03:48:54PM +, Sean Harmer wrote:
>>>  Is there a way we can get a git-lfs repo set up as a submodule to be
>>>  referenced by the qt3d repo?
>>
>> sure. you just need to prototype a solution which i can deploy to our
>> server. as of now, you have gerrit 2.7 and apache at your disposal.
>>
>>>  Or is there some other solution that would be preferred?
>>
>> one quite ugly variant is doing poor man's "lfs" by putting a script in
>> the repo which uses wget and such to fetch data from some well-known
>> location. the file names on the server should be versioned, of course.
>> the problem is of course reviewing and uploading the files ...
> 
> Another variant which is similar but (arguably) somewhat less ugly is to put
> assets into Conan[1] package. We already have necessary qt5.git infrastructure
> in place.
> 
>  [1] https://www.conan.io/

What do you mean by "We already have necessary qt5.git infrastructure in place"?

As a Conan user myself, I'd like to learn more about these packages. Are there 
official Qt packages for Conan available? I've found a few unofficial ones, but 
didn’t know anything about official support. Could you provide a link or some 
documentation?

Thanks,

Julius
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.9

[Julius Bullinger]

-Ursprüngliche Nachricht-
Von: Development 
[mailto:development-bounces+julius.bullinger=asctec...@qt-project.org] Im 
Auftrag von Jani Heikkinen
Gesendet: Tuesday, 29 November, 2016 12:08
An: Thiago Macieira ; development@qt-project.org
Betreff: Re: [Development] Qt 5.9

> And how to encourage users to use online installers instead of offline ones? 
> One solution could be that we start using online ones at
> first & bring offline ones later. Earlier we have released beta with offline 
> only so should we do this differently with Qt 5.9: 
> 
> Qt 5.9 alpha: src only
> Qt 5.9 beta: online only
> Qt 5.9 rc & final: online + offline

I hope it's okay to chime in here as a non-developer, but I would actually 
really be happy about that!

I really like to test beta-versions on Windows, but can't justify installing a 
completely new Qt environment (including another Creator instance with its own 
kits and settings).

If the beta was available in the online installer, I would happily start 
testing today!
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Building Qt with dynamic OpenGL on MinGW broken

[Julius Bullinger]

Hello,

because of QTBUG-52487, there's currently no straight-forward way to build an 
OpenGL-dynamic QT 5.7 with MinGW on Windows. There's a patch attached to the 
bug report, but it's not on Gerrit (and the author hasn't responded to the 
request to push it to Gerrit).

May I propose that somebody else takes the patch and pushes it to Gerrit for a 
proper review? 

Thanks and best regards,
Julius
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.6 StyleSheet

[Julius Bullinger]

Von: Development 
[mailto:development-bounces+julius.bullinger=asctec...@qt-project.org] Im 
Auftrag von Berkay Elbir
Gesendet: Dienstag, 31. Mai 2016 12:23 Uhr
An: development@qt-project.org
Betreff: [Development] Qt 5.6 StyleSheet
> It affects whole project. I mean that affecting other widgets. All the expand 
> symbols change to plus sign. This QLabel is unrelated to this widget(below).
> Did anyone face with this problem?

I faced the same problem, reported it as QTBUG-51799, and it is fixed in 5.6.1 
(to be released in a few days).

Best regards,
Julius
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New Qt5.6 Beta snapshot available

[Julius Bullinger]

Von: Development [mailto:development-boun...@qt-project.org] Im Auftrag von 
Heikkinen Jani
Gesendet: Freitag, 4. Dezember 2015 11:43 Uhr
An: development@qt-project.org
Betreff: [Development] New Qt5.6 Beta snapshot available


> Please test the packages & report all findings in Jira. We are trying to get 
> beta out as soon as possible so please inform all new beta blockers to me 
> immediately.

With this snapshot, wheel scrolling in Creator is borked on my Win 8.1 64-bit 
machine. It used to respect system settings (scroll 3 lines), but now it only 
scrolls a single line.

It's fixed in the lastest Qt Creator 3.6 snapshot, I just wanted to give you a 
heads up.

Best regards,
Julius
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development