Re: [Qt-creator] Dev: Qt Creator 4.9 feature freeze is approaching

[Aleksey Kontsevich]

Does not work in latest master as well.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



01.02.2019, 12:45, "André Pönitz" :
> On Thu, Jan 31, 2019 at 04:10:01PM +0200, Aleksey Kontsevich wrote:
>>  Found error in 4.8: override keyword autocomplete does not work after
>>  destructor, only after other members. Will it be fixed in 4.9?
>
> What happens if you try with a current build of either 4.9 or master
> branch?
>
> Andre'
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] [Interest] Android will require 64bit soon

[Aleksey Kontsevich]

01.02.2019, 12:11, "ekke" :
> Also I think I must then also compile OpenSSL for 32 bit and 64 bit and then 
> need to know HowTo include into .pro

That could help You to do this: 
https://github.com/akontsevich/openssl-android-build

-- 
Best regards,
Aleksey


___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Dev: Qt Creator 4.9 feature freeze is approaching

[Aleksey Kontsevich]

Found error in 4.8: override keyword autocomplete does not work after 
destructor, only after other members. Will it be fixed in 4.9?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



31.01.2019, 09:53, "Eike Ziller" :
> Qt Creator 4.9 feature freeze is approaching!
>
> I have created the 4.9 branch(es). Please start targeting the 4.9 branch now. 
> The master branch will still be merged regularly into 4.9, until feature 
> freeze goes into effect next week (last merge around EOB Feb 6th 2019).
> You can even retarget existing changes on codereview (only the change owner): 
> Just add a comment "bot: move to 4.9”
>
> Br, Eike
>
> https://wiki.qt.io/Qt_Creator_Releases
>
> Qt Creator 4.9
>
> * Feature freeze wk6 (~ Feb 5 2019)
> * Beta release wk8 (~ Feb 19 2019)
> * String freeze wk10 (~ Mar 5 2019)
> * RC release wk12 (~ Mar 19 2019)
> * Final release wk14 (~ Apr 2 2019)
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Adjusting styles of QtCreator

[Aleksey Kontsevich]

Yes, good if this will be fixed. Now Scroll bars, checkboxes, other controls 
are very small, inconvenient and terrible. Distribution built QtC have much 
better look.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



23.01.2019, 00:48, "Michael Jackson" :
> Yes, that does help. It gives me some starting points to experiment.
>
> --
> Mike Jackson
>
> On 1/22/19, 11:17 AM, "Eike Ziller"  wrote:
>
> From QFusionStyle drawing of e.g. QStyle::SC_ScrollBarAddLine I’d think 
> that that uses QPalette::Button as the base color.
>
> Qt Creator’s themes (can?) set that, e.g. 
> share/qtcreator/themes/dark.creatortheme sets
>
> PaletteButton=shadowBackground
>
> (where “shadowBackground” is set to “ff232323” near the top of the file).
>
> There are also the flags DerivePaletteFromTheme and 
> ApplyThemePaletteGlobally which influence if and how the palette in the theme 
> is actually applied, not sure what does what exactly.
> The default theme, flat.creatortheme doesn’t seem to set the application 
> palette, which probably means that it uses whatever Qt sets as the palette 
> for Qt applications. (Which is why it might make a difference against which 
> Qt you compile Qt Creator in that case, I suppose).
>
> I hope that gives you some useful pointers :)
>
> Br, Eike
>
> > On Jan 22, 2019, at 16:16, Michael Jackson 
>  wrote:
> >
> > It has been a long time since I rummaged through the QtCreator code, 
> code I get an assist and point be to where the Styles/Themes are either 
> loaded or applied? Or the name of the subclass that scroll handles/widgets 
> are? I just have a hard time believing that I have to completely change linux 
> distributions or window managers just to get a different color scroll 
> handles. We change the colors on our own application and those changes are 
> reflected in the application. QtCreator does it because when you change 
> themes, you get different scroll handle colors. I just trying to track down 
> which setting in the theme file actually effects those colors. Thank you to 
> anyone that could help my old eyes out.
> >
> > --
> > Mike Jackson
> >
> > From: Cristian Adam 
> > Date: Monday, January 14, 2019 at 3:51 PM
> > To: Michael Jackson 
> > Cc: qt-creator 
> > Subject: Re: [Qt-creator] Adjusting styles of QtCreator
> >
> > On Mon, Jan 14, 2019 at 9:08 PM Michael Jackson 
>  wrote:
> >> Interesting that the only solutions that I have heard is basically to 
> “change your entire desktop”. Clearly the scroll handles are being styled 
> through the .theme file because changing themes will restyle the scroll 
> handles/background. I was hoping for an easier answer such as “.. adjust the 
> following key:value in the theme file”. I guess I have to load up an entirely 
> new desktop environment. Seems a bit over-kill but since Linux is not my full 
> time desktop I guess this is the norm?
> >>
> >
> > You will need to have a build of Qt Creator against your distribution's 
> Qt installation.
> >
> > Ubuntu 16.04 LTS comes with Qt Creator 3.5.1 though, which is a bit 
> dated. Building the latest Qt Creator on Ubuntu 16.04 doesn't help either, 
> since it comes with Qt 5.5.1, which is too old.
> >
> > If I think about it, the "easiest" way would be to compile a QStyle for 
> the same version of Qt that Qt Creator uses, then using the "-style" command 
> line parameter to enable it.
> >
> > Cheers,
> > Cristian.
> >
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > https://lists.qt-project.org/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht 
> Charlottenburg, HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Adjusting styles of QtCreator

[Aleksey Kontsevich]

Ha, yes, You are right: distribution QtC looks much much better. However text 
on left panel buttons and on progress bar still very small. Will use it. The 
only problem left: it does not autodetect Qt versions in ~/Qt/{version}/* from 
online installer - need to add them manually.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



14.01.2019, 14:49, "Cristian Adam" :
> Hi,
>
> On Linux I use the KDE Plasma desktop environment, which you might know uses 
> Qt as it's UI toolkit.
>
> If you have a build of Qt Creator for KDE Plasma, either your own or from the 
> distribution, you will have the Qt KDE theme being used to render the UI.
>
> You might find a KDE theme which might have better user experience, not to 
> mention of having consistent UI in all desktop applications.
>
> Cheers,
> Cristian.
>
> On Fri, Jan 11, 2019, 19:57 Michael Jackson  wrote:
>> I asked this a few years back but it is time to ask again. Is there a way to 
>> hack into the styles defined to change the scroll bars? I’m old and my eyes 
>> suck and having the scroll bar basically the same color as the scroll “well” 
>> or background just kind sucks.
>>
>> Thanks from the old people of the world.
>>
>> --
>>
>> Michael Jackson | Owner, President
>>
>>   BlueQuartz Software
>>
>> [e] mike.jack...@bluequartz.net
>>
>> [w] www.bluequartz.net
>> ___
>> Qt-creator mailing list
>> Qt-creator@qt-project.org
>> https://lists.qt-project.org/listinfo/qt-creator
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Adjusting styles of QtCreator

[Aleksey Kontsevich]

I tried qt5ct as well with no luck.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


11.01.2019, 22:18, "Michael Jackson" :
> Close. I am not on a HiDPI monitor but if there is anyway that I could just 
> adjust the scroll handles that would be awesome. I tried the qt5ct program 
> but that didn't seem to do anything to QtCreator itself.
>
> --
> Mike Jackson
>
> On 1/11/19, 2:41 PM, "Aleksey Kontsevich"  wrote:
>
> Same question and corresponding bug report: 
> https://bugreports.qt.io/browse/QTCREATORBUG-18631
> :-)
>
> --
> Best regards,
> Aleksey
> Linked in https://www.linkedin.com/in/alekseykontsevich
>
> 11.01.2019, 20:59, "Michael Jackson" :
> > I asked this a few years back but it is time to ask again. Is there a 
> way to hack into the styles defined to change the scroll bars? I’m old and my 
> eyes suck and having the scroll bar basically the same color as the scroll 
> “well” or background just kind sucks.
> >
> > Thanks from the old people of the world.
> >
> > --
> >
> > Michael Jackson | Owner, President
> >
> > BlueQuartz Software
> >
> > [e] mike.jack...@bluequartz.net
> >
> > [w] www.bluequartz.net
> > ,
> >
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Adjusting styles of QtCreator

[Aleksey Kontsevich]

Same question and corresponding bug report: 
https://bugreports.qt.io/browse/QTCREATORBUG-18631
:-)

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



11.01.2019, 20:59, "Michael Jackson" :
> I asked this a few years back but it is time to ask again. Is there a way to 
> hack into the styles defined to change the scroll bars? I’m old and my eyes 
> suck and having the scroll bar basically the same color as the scroll “well” 
> or background just kind sucks.
>
> Thanks from the old people of the world.
>
> --
>
> Michael Jackson | Owner, President
>
>   BlueQuartz Software
>
> [e] mike.jack...@bluequartz.net
>
> [w] www.bluequartz.net
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Storing plugin data

[Aleksey Kontsevich]

SettingsDatabase Class: 
https://doc-snapshots.qt.io/qtcreator-extending/core-settingsdatabase.html ? 
Use Core::ICore::settingsDatabase() instance then. If not - create your own 
SQLite DB and store in 
QStandardPaths::writableLocation(QStandardPaths::DataLocation) + 
QStringLiteral("/your_path")

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



22.11.2018, 19:13, "Davide Coppola" :
> Hi,
>
> I need to store some data for a Qt Creator plugin I am working on.
> Keep in mind that I am not talking about settings, but actual data generated 
> by the plugin.
>
> I am planning to use SQLite to handle the data, but I am not sure where I 
> should keep the file used to save the database.
>
> Am I supposed to use some data path returned by 
> QStandardPaths::standardLocations or is there a better/different way for 
> plugins?
>
> Thanks
>
> --
> Davide Coppola
>
> website: http://www.davidecoppola.com
> blog: http://blog.davidecoppola.com
>
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@lists.qt-project.org
> https://lists.qt-project.org/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@lists.qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

I see. However it is not clear to me: whether I can monitor now which help URL 
was opened, keywords searched, etc in QtC or can not?

In src/plugins/coreplugin/helpmanager.h file you've removed

void helpRequested(const QUrl , Core::HelpManager::HelpViewerLocation 
location);

signal which allowed at least to track URLs of opened help documents.

In Qt Help classes http://doc.qt.io/qt-5/qthelp-module.html I see the 
possibility and signals to track opened help documents or search keywords. Not 
sure how to get document titles from URLs, seems Qt Help does not provide this 
as well?

So the only question: is it possible somehow to get  QHelpEngine instance for 
Qt Creator to connect to above signals? I do not see QtC help plugin provides 
such interface to public. Use QObject::findChild()? Thanks!

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


10.10.2018, 11:00, "Eike Ziller" :
>>  On 10. Oct 2018, at 00:57, Aleksey Kontsevich  wrote:
>>
>>  Hi again,
>>
>>  Have question about QtC help system as well. I saw there was some class 
>> which emits signal when some document openned in help system with help page 
>> URI as argument: (Core::HelpManager) or something. Now can't find it. 
>> Whether it was removed or such functionality does not exist?
>
> That signal only existed to get the information from Core plugin to Help 
> plugin. This has been changed to a direct call in 
> https://codereview.qt-project.org/238543 when making Core plugin independent 
> from QtHelp.
>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>
>>  08.10.2018, 00:53, "Aleksey Kontsevich" :
>>>  Hi Eike,
>>>
>>>  I see there is no documentation about QtSupport namesapce or 
>>> QtKitInformation?
>>>
>>>  Also it is not clear how to get other information like:
>>>  - compiler
>>>  - debugger
>>>  - target platform
>>>  - make system (qmake, qbs, cmake, etc)
>>>
>>>  Could You provide more info please? Thanks!
>>>
>>>  --
>>>  Best regards,
>>>  Aleksey
>>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>>
>>>  12.09.2018, 14:20, "Eike Ziller" :
>>>>   If your question is about kits, generally the KitManager provides the 
>>>> list of defined Kits.
>>>>   Kits are composed of data generated by KitInformation classes.
>>>>   A specific KitInformation class can be used to provide specific info 
>>>> about a kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version 
>>>> specified in the kit.
>>>>
>>>>   Br, Eike
>>>>
>>>>>    On 11. Sep 2018, at 14:29, Aleksey Kontsevich  wrote:
>>>>>
>>>>>    Hi all,
>>>>>
>>>>>    I need to implement KitDataSource for new ConnectedCreatorPlugin which 
>>>>> will be officially shipped with QtC distribution. This data source gather 
>>>>> information about compilers, platforms, target platforms, debuggers, etc 
>>>>> used by a QtC user. I've found ProjectExplorer Namespace documentation 
>>>>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
>>>>>  with classes which contains this information however documentation is 
>>>>> still very poor and there are very many classes so it is not quite clear 
>>>>> which one to use, how to use and how they are connected to each other. So 
>>>>> question is:
>>>>>    - how better organize these information gathering
>>>>>    - which classes to use
>>>>>    - which signals, methods
>>>>>    - when to gather the information: on a project open, kit setup, etc?
>>>>>
>>>>>    Gould you guide me a little on this please? Thanks!
>>>>>
>>>>>    --
>>>>>    Best regards,
>>>>>    Aleksey
>>>>>    Linked in https://www.linkedin.com/in/alekseykontsevich
>>>>>    ___
>>>>>    Qt-creator mailing list
>>>>>    Qt-creator@qt-project.org
>>>>>    http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>
>>>>   --
>>>>   Eike Ziller
>>>>   Principal Software Engineer
>>>>
>>>>   The Qt Company GmbH
>>>>   Rudower Chaussee 13
>>>>   D-12489 Berlin
>>>>   eike.zil...@qt.io
>>>>   http://qt.io
>>>>   Geschäftsführer: Mika Pälsi,
>>>>   Juha Varelius, Mika Harjuaho
>>>>   Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht 
>>>> Charlottenburg, HRB 144331 B
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

Thanks, Eike, for the comprehensive explanation: added much more info and in 
more correct way than before to KitDataSource. Only 2 questions:

-  I see DebuggerItem allows to get debugger version via QString version() 
const method, is there something similar for compiler? I see such information 
is absent in ToolChain class.

- ToolChain class allows to get cxxLanguageVersion() or languageVersion(), 
however not sure what arguments are for these methods? Also they are return 
enums, good to have QString() analogues - are there something available?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


10.10.2018, 10:53, "Eike Ziller" :
>>  On 7. Oct 2018, at 23:53, Aleksey Kontsevich  wrote:
>>
>>  Hi Eike,
>>
>>  I see there is no documentation about QtSupport namesapce or 
>> QtKitInformation?
>>
>>  Also it is not clear how to get other information like:
>>  - compiler
>
> e.g.
> ToolChainKitInformation::toolChain(kit, 
> ProjectExplorer::Constants::CXX_LANGUAGE_ID)
>
>>  - debugger
>
> DebuggerKitInformation::debugger(kit)
>
>>  - target platform
>
> Possibly DeviceTypeKitInformation::deviceTypeId(kit)
>
>>  - make system (qmake, qbs, cmake, etc)
>
> Possibly something like SessionManager::projects() + project->id() (which is 
> more a type ID)
>
>>  Could You provide more info please? Thanks!
>>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>
>>  12.09.2018, 14:20, "Eike Ziller" :
>>>  If your question is about kits, generally the KitManager provides the list 
>>> of defined Kits.
>>>  Kits are composed of data generated by KitInformation classes.
>>>  A specific KitInformation class can be used to provide specific info about 
>>> a kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version 
>>> specified in the kit.
>>>
>>>  Br, Eike
>>>
>>>>   On 11. Sep 2018, at 14:29, Aleksey Kontsevich  wrote:
>>>>
>>>>   Hi all,
>>>>
>>>>   I need to implement KitDataSource for new ConnectedCreatorPlugin which 
>>>> will be officially shipped with QtC distribution. This data source gather 
>>>> information about compilers, platforms, target platforms, debuggers, etc 
>>>> used by a QtC user. I've found ProjectExplorer Namespace documentation 
>>>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
>>>>  with classes which contains this information however documentation is 
>>>> still very poor and there are very many classes so it is not quite clear 
>>>> which one to use, how to use and how they are connected to each other. So 
>>>> question is:
>>>>   - how better organize these information gathering
>>>>   - which classes to use
>>>>   - which signals, methods
>>>>   - when to gather the information: on a project open, kit setup, etc?
>>>>
>>>>   Gould you guide me a little on this please? Thanks!
>>>>
>>>>   --
>>>>   Best regards,
>>>>   Aleksey
>>>>   Linked in https://www.linkedin.com/in/alekseykontsevich
>>>>   ___
>>>>   Qt-creator mailing list
>>>>   Qt-creator@qt-project.org
>>>>   http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>
>>>  --
>>>  Eike Ziller
>>>  Principal Software Engineer
>>>
>>>  The Qt Company GmbH
>>>  Rudower Chaussee 13
>>>  D-12489 Berlin
>>>  eike.zil...@qt.io
>>>  http://qt.io
>>>  Geschäftsführer: Mika Pälsi,
>>>  Juha Varelius, Mika Harjuaho
>>>  Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht 
>>> Charlottenburg, HRB 144331 B
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

Hi again,

Have question about QtC help system as well. I saw there was some class which 
emits signal when some document openned in help system with help page URI as 
argument: (Core::HelpManager) or something. Now can't find it. Whether it was 
removed or such functionality does not exist?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


08.10.2018, 00:53, "Aleksey Kontsevich" :
> Hi Eike,
>
> I see there is no documentation about QtSupport namesapce or QtKitInformation?
>
> Also it is not clear how to get other information like:
> - compiler
> - debugger
> - target platform
> - make system (qmake, qbs, cmake, etc)
>
> Could You provide more info please? Thanks!
>
> --
> Best regards,
> Aleksey
> Linked in https://www.linkedin.com/in/alekseykontsevich
>
> 12.09.2018, 14:20, "Eike Ziller" :
>>  If your question is about kits, generally the KitManager provides the list 
>> of defined Kits.
>>  Kits are composed of data generated by KitInformation classes.
>>  A specific KitInformation class can be used to provide specific info about 
>> a kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version 
>> specified in the kit.
>>
>>  Br, Eike
>>
>>>   On 11. Sep 2018, at 14:29, Aleksey Kontsevich  wrote:
>>>
>>>   Hi all,
>>>
>>>   I need to implement KitDataSource for new ConnectedCreatorPlugin which 
>>> will be officially shipped with QtC distribution. This data source gather 
>>> information about compilers, platforms, target platforms, debuggers, etc 
>>> used by a QtC user. I've found ProjectExplorer Namespace documentation 
>>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
>>>  with classes which contains this information however documentation is 
>>> still very poor and there are very many classes so it is not quite clear 
>>> which one to use, how to use and how they are connected to each other. So 
>>> question is:
>>>   - how better organize these information gathering
>>>   - which classes to use
>>>   - which signals, methods
>>>   - when to gather the information: on a project open, kit setup, etc?
>>>
>>>   Gould you guide me a little on this please? Thanks!
>>>
>>>   --
>>>   Best regards,
>>>   Aleksey
>>>   Linked in https://www.linkedin.com/in/alekseykontsevich
>>>   ___
>>>   Qt-creator mailing list
>>>   Qt-creator@qt-project.org
>>>   http://lists.qt-project.org/mailman/listinfo/qt-creator
>>
>>  --
>>  Eike Ziller
>>  Principal Software Engineer
>>
>>  The Qt Company GmbH
>>  Rudower Chaussee 13
>>  D-12489 Berlin
>>  eike.zil...@qt.io
>>  http://qt.io
>>  Geschäftsführer: Mika Pälsi,
>>  Juha Varelius, Mika Harjuaho
>>  Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
>> HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

Hi Eike,

I see there is no documentation about QtSupport namesapce or QtKitInformation?

Also it is not clear how to get other information like:
- compiler
- debugger
- target platform
- make system (qmake, qbs, cmake, etc)

Could You provide more info please? Thanks!

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


12.09.2018, 14:20, "Eike Ziller" :
> If your question is about kits, generally the KitManager provides the list of 
> defined Kits.
> Kits are composed of data generated by KitInformation classes.
> A specific KitInformation class can be used to provide specific info about a 
> kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version specified 
> in the kit.
>
> Br, Eike
>
>>  On 11. Sep 2018, at 14:29, Aleksey Kontsevich  wrote:
>>
>>  Hi all,
>>
>>  I need to implement KitDataSource for new ConnectedCreatorPlugin which will 
>> be officially shipped with QtC distribution. This data source gather 
>> information about compilers, platforms, target platforms, debuggers, etc 
>> used by a QtC user. I've found ProjectExplorer Namespace documentation 
>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
>>  with classes which contains this information however documentation is still 
>> very poor and there are very many classes so it is not quite clear which one 
>> to use, how to use and how they are connected to each other. So question is:
>>  - how better organize these information gathering
>>  - which classes to use
>>  - which signals, methods
>>  - when to gather the information: on a project open, kit setup, etc?
>>
>>  Gould you guide me a little on this please? Thanks!
>>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

[Aleksey Kontsevich]

Thanks all for the repos. Now initial library and plugin commits are on review 
for both projects:
- https://codereview.qt-project.org/#/c/240347/
- https://codereview.qt-project.org/#/c/240361/

It is good if someone wants to review and approve those cause we need to move 
things forward and try to include our project into coming QtC 4.8 release.

Thanks all again for participation!

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



04.09.2018, 12:24, "Frederik Gladhorn" :
> With much joy I created two repositories.
>
> qt-creator/plugin-telemetry
> playground/telemetry
>
> They still need concise descriptions as the other repos have, please send them
> to me.
>
> Cheers,
> Frederik
>
> On fredag 31. august 2018 13.02.46 CEST Frederik Gladhorn wrote:
>>  On torsdag 30. august 2018 17.40.14 CEST Aleksey Kontsevich wrote:
>>  > You need 2 repos - clones of following:
>>  > https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
>>  > https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
>>
>>  I'm not sure I want to clone the repos directly, how will reviews happen?
>>  Should there be a merge request? Is anyone interested in reviewing the whole
>>  stuff and how?
>>
>>  Then most files I peaked into were lacking the license header and in the
>>  root directory I only found a LGPL license (I may be wrong, I didn't spend
>>  very long looking), so that's also not compatible with Qt license policy.
>>
>>  So the question stands, how should the import/review happen?
>>
>>  Cheers,
>>  Frederik
>>
>>  > > On torsdag 30. august 2018 12.55.17 CEST Lars Knoll wrote:
>>  > >> Agreed. Frederik, could you help with creating the required repos?
>>  > >
>>  > > I can create the repos. How do you imagine importing the existing code,
>>  > > assuming that's the idea?
>>  > > Should this be a clone of the existing stuff or fresh repos where we
>>  > > start
>>  > > with a review of the existing code bases?
>>  > >
>>  > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
>>  > >
>>  > > I'd suggest: qt-creator/plugin-telemetry
>>  > >
>>  > >> Telemetry library: playground/telemetry
>>  > >
>>  > > If this is supposed to become an official Qt library at some point, it
>>  > > should probably be something like qttelemetry, but starting in
>>  > > playground
>>  > > would means it needs moving and renaming eventually in any case. The
>>  > > closer we can get to the final location, the better.
>>  > >
>>  > > Cheers,
>>  > > Frederik
>>  > >
>>  > >> Thanks,
>>  > >> Lars
>>  > >>
>>  > >> On 30 Aug 2018, at 12:50, Tuukka Turunen  wrote:
>>  > >>
>>  > >> Hi,
>>  > >>
>>  > >> There were no objection to this, request. However, perhaps due to the
>>  > >> summertime the repos were not created.
>>  > >> Let’s make those now and move this code under the Qt project.
>>  > >>
>>  > >> Yours,
>>  > >>
>>  > >> Tuukka
>>  > >>
>>  > >> From: Qt-creator
>>  > >>
>>  > >>  on behalf of
>>  > >> Tino Pyssysalo  Date: Monday, 16 July 2018 at
>>  > >> 10.17
>>  > >>
>>  > >> To: "qt-creator@qt-project.org" 
>>  > >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin
>>  > >> and
>>  > >> telemetry library
>>  > >> Hi all,
>>  > >>
>>  > >> In March this year, I requested a repo for an open source telemetry
>>  > >>
>>  > >> plugin
>>  > >>
>>  > >> for Qt Creator. Now, the plugin has been implemented and I’d like to
>>  > >> request two repos: · A repo for a Connected Creator plugin
>>  > >> · A playground repo for a telemetry library
>>  > >>
>>  > >> Description: The Qt Company wants to collect usage data from Qt
>>  > >>
>>  > >> development tools. For that purpose, we have developed a
>>  > >> general-purpose
>>  > >> telemetry library and a Qt Creator -specific plugin, using the
>>  > >> telemetry
>>  > >> library. The reason to collect the data from o

Re: [Qt-creator] Downloading Kate Highlighter Definitions

[Aleksey Kontsevich]

There are few bug reports opened explaining this matter:https://bugreports.qt.io/browse/QTCREATORBUG-20607https://bugreports.qt.io/browse/QTBUG-68971 Not sure about current status of the above. Think Eike may tell more :) -- Best regards,AlekseyLinked in  https://www.linkedin.com/in/alekseykontsevich   24.09.2018, 21:12, "Jochen Becher" :Hi,QtCreator says "SSL is not supported". But I have packages libssl1.0.0,libssl1.1 and openssl installed on Ubuntu 18.04. Anything I miss?Why doesn't Qt or QtCreator deliver their own packages if finding asystem install is difficult?System Information:qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locksqt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callbackqt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callbackqt.network.ssl: QSslSocket: cannot resolve ERR_free_stringsqt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanupqt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_initqt.network.ssl: QSslSocket: cannot resolve sk_new_nullqt.network.ssl: QSslSocket: cannot resolve sk_pushqt.network.ssl: QSslSocket: cannot resolve sk_freeqt.network.ssl: QSslSocket: cannot resolve sk_numqt.network.ssl: QSslSocket: cannot resolve sk_pop_freeqt.network.ssl: QSslSocket: cannot resolve sk_valueqt.network.ssl: QSslSocket: cannot resolve SSL_library_initqt.network.ssl: QSslSocket: cannot resolve SSL_load_error_stringsqt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_indexqt.network.ssl: QSslSocket: cannot resolve SSLv3_client_methodqt.network.ssl: QSslSocket: cannot resolve SSLv23_client_methodqt.network.ssl: QSslSocket: cannot resolve SSLv3_server_methodqt.network.ssl: QSslSocket: cannot resolve SSLv23_server_methodqt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chainqt.network.ssl: QSslSocket: cannot resolveOPENSSL_add_all_algorithms_noconfqt.network.ssl: QSslSocket: cannot resolveOPENSSL_add_all_algorithms_confqt.network.ssl: QSslSocket: cannot resolve SSLeayqt.network.ssl: Incompatible version of OpenSSLRegards, JochenAm Montag, den 24.09.2018, 06:52 + schrieb Eike Ziller: > On 21. Sep 2018, at 20:19, Jochen Becher  > wrote: > > Hi, > > Downloading Kate Highlighter definitions fails for me in Qt Creator > 4.7.0. I get an error dialog: "Error connection to server" / "Not > possible to retrieve data.". > > I checked the URL that is used (at least what my source code from > git/master says: "https://www.kate-editor.org/syntax/update-5.60.xm > l") > and it seems to be fine. > > Known Issue? My guess: Since it’s trying to use https, Qt needs to find OpenSSL (on Lin/Win). Qt’s method for finding that is not failsafe (to say the least), and it also isn’t made easy with the various incompatible versions of it. I think Help > System Information from Qt Creator’s menu should show you some information about if and what SSL library is found. -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___Qt-creator mailing listQt-creator@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/qt-creator___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

I see. What about Kits really used by user?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


12.09.2018, 14:20, "Eike Ziller" :
> If your question is about kits, generally the KitManager provides the list of 
> defined Kits.
> Kits are composed of data generated by KitInformation classes.
> A specific KitInformation class can be used to provide specific info about a 
> kit, e.g. QtKitInformation::qtVersion(kit) returns the Qt version specified 
> in the kit.
>
> Br, Eike
>
>>  On 11. Sep 2018, at 14:29, Aleksey Kontsevich  wrote:
>>
>>  Hi all,
>>
>>  I need to implement KitDataSource for new ConnectedCreatorPlugin which will 
>> be officially shipped with QtC distribution. This data source gather 
>> information about compilers, platforms, target platforms, debuggers, etc 
>> used by a QtC user. I've found ProjectExplorer Namespace documentation 
>> (https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
>>  with classes which contains this information however documentation is still 
>> very poor and there are very many classes so it is not quite clear which one 
>> to use, how to use and how they are connected to each other. So question is:
>>  - how better organize these information gathering
>>  - which classes to use
>>  - which signals, methods
>>  - when to gather the information: on a project open, kit setup, etc?
>>
>>  Gould you guide me a little on this please? Thanks!
>>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] Qt Creator plugin API question

[Aleksey Kontsevich]

Hi all,

I need to implement KitDataSource for new ConnectedCreatorPlugin which will be 
officially shipped with QtC distribution. This data source gather information 
about   compilers, platforms, target platforms, debuggers, etc used by a QtC 
user. I've found  ProjectExplorer Namespace documentation 
(https://doc-snapshots.qt.io/qtcreator-extending/projectexplorer.html#namespaces)
 with classes which contains this information however documentation is still 
very poor and there are very many classes so it is not quite clear which one to 
use, how to use and how they are connected to each other. So question is:
 - how better organize these information gathering
 - which classes to use
 - which signals, methods
 - when to gather the information: on a project open, kit setup, etc?

Gould you guide me a little on this please? Thanks!

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] The great idea for Qt Creator

[Aleksey Kontsevich]

> I think this is a very good idea. One thing about Qt Creator is it is
> a bit frustrating to work with the Project file tree, and combining
> the ones with the same name could be a good improvement.

Visual Studio uses similar approach for UI and its sources - combining them 
under same expandable name. Not sure how to organize this in QtC but sounds 
interesting.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


05.09.2018, 08:26, "Carel Combrink" :
> On Wed, Sep 5, 2018 at 7:16 AM Tomasz Siekierda  wrote:
>>  On Tue, 4 Sep 2018 at 20:52, Szyk Cech  wrote:
>>  >
>>  > Hi
>>  >
>>  > I want introduce big improvement (at least in my humble opinion) to Qt
>>  > Creator.
>>  >
>>  > My idea is very simple and very strong logical/rational/sensible and Qt
>>  > projects oriented (but not limited to Qt projects).
>>  >
>>  > I don't pretend to be renter of this idea, but if you use/follow this
>>  > idea, then I suppose you mention this concept as "Szyk Cech's project
>>  > menu style".
>>  >
>>  > So lets sum up typical Qt project:
>>  >
>>  > * plenty cpp, h, ui and qml files - typically related to each others and
>>  > names only differ with extensions (eg. MainWindow.h, MainWindow.cpp,
>>  > MainWindow.ui)
>>  >
>>  > * few cpp and h files typically differs only with extensions (Factory.h,
>>  > Factory.cpp)
>>  >
>>  > * main.cpp
>>  >
>>  > Now we have big Qt project tree which is pretty unusable for bigger
>>  > projects (like Qt Creator). But we can improve this greatly!
>>  >
>>  > We can use full advantage of QTreeView widget and display all 3 (or 4)
>>  > Qt files in 1 row!!!
>>  >
>>  > I recognize following use cases:
>>  >
>>  > 1. We have Qt widget file (eg. MainWindow.h, MainWindow.cpp,
>>  > MainWindow.ui), so we display in first column only file name without
>>  > extension, and in next 3 columns h, cpp, ui . Then when we have direct
>>  > access for every files related to our ui file (h and cpp) - without
>>  > stupid clicking headers or sources (in order to unroll them) and without
>>  > annoying scrolling!!!
>>
>>  I'd rather keep the project tree as thin as possible and leave more
>>  space for code editor views. So I'd rather suggest making base file
>>  name an expandable item with 3-4 children (concrete files .cpp, h.
>>  etc.).
>>
>>  Also, there is a big problem here: Qt Creator would have to assume
>>  (or, even worse for performance - check) that someString.h and
>>  someString.cpp are related. What if they are not?
>>
>>  And what if there are multiple files with the same name?
>>
>>  And lastly, what if there are multiple implementations for a single
>>  header? (class.h, classWin.cpp, classMac.cpp etc.)
>>
>>  By the way, in most cases scrolling is not necessary - just hit F4 to
>>  switch between header and source files. And if that fails, there is
>>  also the Locator which allows you to open relevant files quickly.
>>
>>  > 2. if additionally to 1. we have qml file with the same name as h, cpp,
>>  > ui - display it in 4. column
>>  >
>>  > 3. If we have only h and cpp (or c) file: display name in first column
>>  > and h and cpp in next 2.
>>  >
>>  > 4. If project does not contain Qml files or not contain Ui files, then
>>  > QTreeView should not display Qml or Ui columns accordingly (only h and 
>> cpp).
>>  >
>>  > 5. If project is pure c project then c extension should display in Cpp
>>  > column.
>>  >
>>  > 6. Any other files names are displayed traditionally in first column.
>>  >
>>  > You can see my mock interface in attached png file.
>>  >
>>  > I can't implement this great feature for many reasons:
>>  >
>>  > 1. I work and have limited free time, and:
>>  >
>>  > 2. I have other great ideas for my projects (which I consider more
>>  > important).
>>  >
>>  > 3. I have experience in writing mods for Qt Creator, but: Most important
>>  > problem is that I can't be sure my mod will be accepted by developers.
>>  > So I can spend few weeks writing this mod and polish this idea, and end
>>  > up with rejected opinions. I do not believe using this idea only for my
>>  > self, because I can't adjust my patches for every new Qt Creator
>>  > releases (it is very tedious and frustrating work to me - so I give up
>>  > with my Qt Creator mod and use official version only).
>>  >
>>  > best wishes
>>  >
>>  > Szyk Cech
>>  >
>>  >
>>  > ___
>>  > Qt-creator mailing list
>>  > Qt-creator@qt-project.org
>>  > http://lists.qt-project.org/mailman/listinfo/qt-creator
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> I think this is a very good idea. One thing about Qt Creator is it is
> a bit frustrating to work with the Project file tree, and combining
> the ones with the same name could be a good improvement.
>
> That said, I am not sure about the proposed 

Re: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

[Aleksey Kontsevich]

Description for the plugin:
Connected creator plugin collects usage data from Qt Creator users. This data 
is used to improve Qt user experience and as one information source to make 
product decisions. 

For the library:
Qt library for collecting usage statistics from users for Qt applications via 
telemetry and submitting the data to REST API server backend 

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


04.09.2018, 12:24, "Frederik Gladhorn" :
> With much joy I created two repositories.
>
> qt-creator/plugin-telemetry
> playground/telemetry
>
> They still need concise descriptions as the other repos have, please send them
> to me.
>
> Cheers,
> Frederik
>
> On fredag 31. august 2018 13.02.46 CEST Frederik Gladhorn wrote:
>>  On torsdag 30. august 2018 17.40.14 CEST Aleksey Kontsevich wrote:
>>  > You need 2 repos - clones of following:
>>  > https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
>>  > https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
>>
>>  I'm not sure I want to clone the repos directly, how will reviews happen?
>>  Should there be a merge request? Is anyone interested in reviewing the whole
>>  stuff and how?
>>
>>  Then most files I peaked into were lacking the license header and in the
>>  root directory I only found a LGPL license (I may be wrong, I didn't spend
>>  very long looking), so that's also not compatible with Qt license policy.
>>
>>  So the question stands, how should the import/review happen?
>>
>>  Cheers,
>>  Frederik
>>
>>  > > On torsdag 30. august 2018 12.55.17 CEST Lars Knoll wrote:
>>  > >> Agreed. Frederik, could you help with creating the required repos?
>>  > >
>>  > > I can create the repos. How do you imagine importing the existing code,
>>  > > assuming that's the idea?
>>  > > Should this be a clone of the existing stuff or fresh repos where we
>>  > > start
>>  > > with a review of the existing code bases?
>>  > >
>>  > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
>>  > >
>>  > > I'd suggest: qt-creator/plugin-telemetry
>>  > >
>>  > >> Telemetry library: playground/telemetry
>>  > >
>>  > > If this is supposed to become an official Qt library at some point, it
>>  > > should probably be something like qttelemetry, but starting in
>>  > > playground
>>  > > would means it needs moving and renaming eventually in any case. The
>>  > > closer we can get to the final location, the better.
>>  > >
>>  > > Cheers,
>>  > > Frederik
>>  > >
>>  > >> Thanks,
>>  > >> Lars
>>  > >>
>>  > >> On 30 Aug 2018, at 12:50, Tuukka Turunen  wrote:
>>  > >>
>>  > >> Hi,
>>  > >>
>>  > >> There were no objection to this, request. However, perhaps due to the
>>  > >> summertime the repos were not created.
>>  > >> Let’s make those now and move this code under the Qt project.
>>  > >>
>>  > >> Yours,
>>  > >>
>>  > >> Tuukka
>>  > >>
>>  > >> From: Qt-creator
>>  > >>
>>  > >>  on behalf of
>>  > >> Tino Pyssysalo  Date: Monday, 16 July 2018 at
>>  > >> 10.17
>>  > >>
>>  > >> To: "qt-creator@qt-project.org" 
>>  > >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin
>>  > >> and
>>  > >> telemetry library
>>  > >> Hi all,
>>  > >>
>>  > >> In March this year, I requested a repo for an open source telemetry
>>  > >>
>>  > >> plugin
>>  > >>
>>  > >> for Qt Creator. Now, the plugin has been implemented and I’d like to
>>  > >> request two repos: · A repo for a Connected Creator plugin
>>  > >> · A playground repo for a telemetry library
>>  > >>
>>  > >> Description: The Qt Company wants to collect usage data from Qt
>>  > >>
>>  > >> development tools. For that purpose, we have developed a
>>  > >> general-purpose
>>  > >> telemetry library and a Qt Creator -specific plugin, using the
>>  > >> telemetry
>>  > >> library. The reason to collect the data from our users is to learn

Re: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

[Aleksey Kontsevich]

License header could be easily added and license is LGPL-3.0 which should not 
be a problem.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


31.08.2018, 14:14, "Frederik Gladhorn" :
> On torsdag 30. august 2018 17.40.14 CEST Aleksey Kontsevich wrote:
>>  You need 2 repos - clones of following:
>>  https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
>>  https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
>
> I'm not sure I want to clone the repos directly, how will reviews happen?
> Should there be a merge request? Is anyone interested in reviewing the whole
> stuff and how?
>
> Then most files I peaked into were lacking the license header and in the root
> directory I only found a LGPL license (I may be wrong, I didn't spend very
> long looking), so that's also not compatible with Qt license policy.
>
> So the question stands, how should the import/review happen?
>
> Cheers,
> Frederik
>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>
>>  30.08.2018, 18:20, "Frederik Gladhorn" :
>>  > On torsdag 30. august 2018 12.55.17 CEST Lars Knoll wrote:
>>  >> Agreed. Frederik, could you help with creating the required repos?
>>  >
>>  > I can create the repos. How do you imagine importing the existing code,
>>  > assuming that's the idea?
>>  > Should this be a clone of the existing stuff or fresh repos where we start
>>  > with a review of the existing code bases?
>>  >
>>  >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
>>  >
>>  > I'd suggest: qt-creator/plugin-telemetry
>>  >
>>  >> Telemetry library: playground/telemetry
>>  >
>>  > If this is supposed to become an official Qt library at some point, it
>>  > should probably be something like qttelemetry, but starting in playground
>>  > would means it needs moving and renaming eventually in any case. The
>>  > closer we can get to the final location, the better.
>>  >
>>  > Cheers,
>>  > Frederik
>>  >
>>  >> Thanks,
>>  >> Lars
>>  >>
>>  >> On 30 Aug 2018, at 12:50, Tuukka Turunen  wrote:
>>  >>
>>  >> Hi,
>>  >>
>>  >> There were no objection to this, request. However, perhaps due to the
>>  >> summertime the repos were not created.
>>  >> Let’s make those now and move this code under the Qt project.
>>  >>
>>  >> Yours,
>>  >>
>>  >> Tuukka
>>  >>
>>  >> From: Qt-creator
>>  >>  on behalf of
>>  >> Tino Pyssysalo  Date: Monday, 16 July 2018 at
>>  >> 10.17
>>  >> To: "qt-creator@qt-project.org" 
>>  >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
>>  >> telemetry library
>>  >> Hi all,
>>  >>
>>  >> In March this year, I requested a repo for an open source telemetry
>>  >> plugin
>>  >> for Qt Creator. Now, the plugin has been implemented and I’d like to
>>  >> request two repos: · A repo for a Connected Creator plugin
>>  >> · A playground repo for a telemetry library
>>  >>
>>  >> Description: The Qt Company wants to collect usage data from Qt
>>  >> development tools. For that purpose, we have developed a general-purpose
>>  >> telemetry library and a Qt Creator -specific plugin, using the telemetry
>>  >> library. The reason to collect the data from our users is to learn, how
>>  >> developers use Qt Creator and other tools, how usage patterns change,
>>  >> how quickly new features and versions are started to be used, which
>>  >> tools are mostly used? This information is one data source, helping us
>>  >> to make decisions, how to further develop our products. In the short
>>  >> run, we believe we will get valuable information, how to improve the
>>  >> user experience of our products. The connected creator plugin implements
>>  >> the frontend for tracking the data from different data sources in Qt
>>  >> Creator. The frontend consists of a simple UI to enable/disable the
>>  >> plugin, to set logs expiration period, and to view the data to be
>>  >> transmitted or previously transmitted data (logs). Currently, the plugin
>>  >> tracks Qt Quick Designer usage only: launch count and usage time.
>>  >&

Re: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

[Aleksey Kontsevich]

You need 2 repos - clones of following:
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



30.08.2018, 18:20, "Frederik Gladhorn" :
> On torsdag 30. august 2018 12.55.17 CEST Lars Knoll wrote:
>>  Agreed. Frederik, could you help with creating the required repos?
>
> I can create the repos. How do you imagine importing the existing code,
> assuming that's the idea?
> Should this be a clone of the existing stuff or fresh repos where we start
> with a review of the existing code bases?
>
>>  Connected Creator plugin: qt-cresator/plugin-connectedcreator
>
> I'd suggest: qt-creator/plugin-telemetry
>
>>  Telemetry library: playground/telemetry
>
> If this is supposed to become an official Qt library at some point, it should
> probably be something like qttelemetry, but starting in playground would means
> it needs moving and renaming eventually in any case. The closer we can get to
> the final location, the better.
>
> Cheers,
> Frederik
>
>>  Thanks,
>>  Lars
>>
>>  On 30 Aug 2018, at 12:50, Tuukka Turunen  wrote:
>>
>>  Hi,
>>
>>  There were no objection to this, request. However, perhaps due to the
>>  summertime the repos were not created.
>>  Let’s make those now and move this code under the Qt project.
>>
>>  Yours,
>>
>>  Tuukka
>>
>>  From: Qt-creator  on
>>  behalf of Tino Pyssysalo  Date: Monday, 16 July 2018
>>  at 10.17
>>  To: "qt-creator@qt-project.org" 
>>  Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
>>  telemetry library
>>  Hi all,
>>
>>  In March this year, I requested a repo for an open source telemetry plugin
>>  for Qt Creator. Now, the plugin has been implemented and I’d like to
>>  request two repos: · A repo for a Connected Creator plugin
>>  · A playground repo for a telemetry library
>>
>>  Description: The Qt Company wants to collect usage data from Qt development
>>  tools. For that purpose, we have developed a general-purpose telemetry
>>  library and a Qt Creator -specific plugin, using the telemetry library. The
>>  reason to collect the data from our users is to learn, how developers use
>>  Qt Creator and other tools, how usage patterns change, how quickly new
>>  features and versions are started to be used, which tools are mostly used?
>>  This information is one data source, helping us to make decisions, how to
>>  further develop our products. In the short run, we believe we will get
>>  valuable information, how to improve the user experience of our products.
>>  The connected creator plugin implements the frontend for tracking the data
>>  from different data sources in Qt Creator. The frontend consists of a
>>  simple UI to enable/disable the plugin, to set logs expiration period, and
>>  to view the data to be transmitted or previously transmitted data (logs).
>>  Currently, the plugin tracks Qt Quick Designer usage only: launch count and
>>  usage time. General platform data is collected by the telemetry library.
>>  This data currently includes compiler details, locale, OpenGL type and
>>  version, Qt version, screen details, Qt Creator version, license type
>>  (evaluation, commercial, no license), and unique id (generated with QUuid).
>>
>>  All collected data is anonymous. No personal data such as project names,
>>  project locations and paths, IP or MAC addresses, email addresses or Qt
>>  Account details are collected.
>>  The data is stored in the backend server, owned by The Qt Company. The
>>  backend is complexly separated from the telemetry frontend and the code
>>  will be provided in The Qt Company
>>  private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
>>  The collected data is cached into a settings file before the transmission.
>>  This allows the user to check, what data is going to be transmitted and
>>  even disable the plugin before any data is actually transmitted. In
>>  addition, data caching allows calculating key values in the frontend
>>  instead of sending each user event to the server separately. This reduces
>>  the network traffic significantly. By default, the cached data is
>>  transmitted to the server once per week. It is possible to log the
>>  transmitted data into the files to verify all the data transmitted to the
>>  server.
>>  The plugin is planned to be completely opt-in. The online installer will ask
>>  the user, if he/she wants to install the plugin. There is no default
>>  selection for the installation, but user must explicitly choose either to
>>  install or not install the plugin. If the user decides to install the
>>  plugin, it can be disabled in Qt Creator settings. The user is able to see
>>  the cached data and before the first transmission, the user can disable the
>>  plugin, even though it has been installed.
>>  More implementation details can be found in Jira
>>  ticket: 

Re: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library

[Aleksey Kontsevich]

You need 2 repos - clones of following:https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC pluginhttps://github.com/akontsevich/QTelemetry - the library - QTelemetry name -- Best regards,AlekseyLinked in  https://www.linkedin.com/in/alekseykontsevich   30.08.2018, 18:20, "Frederik Gladhorn" :On torsdag 30. august 2018 12.55.17 CEST Lars Knoll wrote: Agreed. Frederik, could you help with creating the required repos?I can create the repos. How do you imagine importing the existing code,assuming that's the idea?Should this be a clone of the existing stuff or fresh repos where we startwith a review of the existing code bases?  Connected Creator plugin: qt-cresator/plugin-connectedcreatorI'd suggest: qt-creator/plugin-telemetry  Telemetry library: playground/telemetryIf this is supposed to become an official Qt library at some point, it shouldprobably be something like qttelemetry, but starting in playground would meansit needs moving and renaming eventually in any case. The closer we can get tothe final location, the better.Cheers,Frederik   Thanks, Lars On 30 Aug 2018, at 12:50, Tuukka Turunen  wrote: Hi, There were no objection to this, request. However, perhaps due to the summertime the repos were not created. Let’s make those now and move this code under the Qt project. Yours, Tuukka From: Qt-creator  on behalf of Tino Pyssysalo  Date: Monday, 16 July 2018 at 10.17 To: "qt-creator@qt-project.org"  Subject: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library Hi all, In March this year, I requested a repo for an open source telemetry plugin for Qt Creator. Now, the plugin has been implemented and I’d like to request two repos: · A repo for a Connected Creator plugin · A playground repo for a telemetry library Description: The Qt Company wants to collect usage data from Qt development tools. For that purpose, we have developed a general-purpose telemetry library and a Qt Creator -specific plugin, using the telemetry library. The reason to collect the data from our users is to learn, how developers use Qt Creator and other tools, how usage patterns change, how quickly new features and versions are started to be used, which tools are mostly used? This information is one data source, helping us to make decisions, how to further develop our products. In the short run, we believe we will get valuable information, how to improve the user experience of our products. The connected creator plugin implements the frontend for tracking the data from different data sources in Qt Creator. The frontend consists of a simple UI to enable/disable the plugin, to set logs expiration period, and to view the data to be transmitted or previously transmitted data (logs). Currently, the plugin tracks Qt Quick Designer usage only: launch count and usage time. General platform data is collected by the telemetry library. This data currently includes compiler details, locale, OpenGL type and version, Qt version, screen details, Qt Creator version, license type (evaluation, commercial, no license), and unique id (generated with QUuid). All collected data is anonymous. No personal data such as project names, project locations and paths, IP or MAC addresses, email addresses or Qt Account details are collected. The data is stored in the backend server, owned by The Qt Company. The backend is complexly separated from the telemetry frontend and the code will be provided in The Qt Company private repo: https://github.com/TheQtCompany/qt-telemetry-backend. The collected data is cached into a settings file before the transmission. This allows the user to check, what data is going to be transmitted and even disable the plugin before any data is actually transmitted. In addition, data caching allows calculating key values in the frontend instead of sending each user event to the server separately. This reduces the network traffic significantly. By default, the cached data is transmitted to the server once per week. It is possible to log the transmitted data into the files to verify all the data transmitted to the server. The plugin is planned to be completely opt-in. The online installer will ask the user, if he/she wants to install the plugin. There is no default selection for the installation, but user must explicitly choose either to install or not install the plugin. If the user decides to install the plugin, it can be disabled in Qt Creator settings. The user is able to see the cached data and before the first transmission, the user can disable the plugin, even though it has been installed. More implementation details can be found in Jira ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250 Existing repos: Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry library: https://github.com/akontsevich/QTelemetry 

Re: [Qt-creator] Questions about CMake INTERFACE project

[Aleksey Kontsevich]

Observed this situation many times as well - good to know the answer: is there 
a way to handle, bug or missed feature?

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



27.08.2018, 08:23, "Abir Basak" :
> Hi,
>   When I open a CMake INTERFACE project, do not see the header files in the 
> QtC Projects pane. This is not problem with executable or library project.
>   Presently as a workaround I made a custom target adding the header files, 
> e.g.
>  add_custom_target(dummy SOURCES ${HEADERS})
> This solves the problem partially listing the header files under a separate 
> target node 'dummy' , but misses language features.
>  So it shows all sorts of wrong analysis like include file not found, or 
> requires c++17 extension etc. Those settings are all present for the actual 
> target like target_compile_features, target_Include_directories , but can't 
> be placed on custom target which is not a compilable target.
>
>  Is there a proper way to handle INTERFACE projects so that QtC understands 
> it and doesn't show wrong analysis (btw, the project itself is fine, runs all 
> tests & examples correctly, only the analysis in QtC is misleading & doesn't 
> show the headers without custom target, even with target_sources)
>
> Thanks
> ,
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Memory usage of Qt Creator

[Aleksey Kontsevich]

Clean QtC 4.5.2 takes 60 MB for me. -- Best regards,AlekseyLinked in  https://www.linkedin.com/in/alekseykontsevich   13.04.2018, 13:32, "timur.kris...@gmail.com" :Hi,Just noticed that with the latest version of Qt Creator the memoryusage numbers went up.Currently I get ~400MiB for qtcreator and ~450MiB for clangbackend.This seems to slowly go down after I close some source files, though ittakes time (guess it keeps them in cache for a while).Are these figures normal / expected?Best regards,Timur___Qt-creator mailing listQt-creator@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/qt-creator___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Migration from QtCreator 4.5 to 4.6

[Aleksey Kontsevich]

Use this one: http://code.qt.io/cgit/qt-creator/qt-creator.git 

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


11.04.2018, 17:00, "Карелин Павел" <hka...@yandex.ru>:
> Now I have paid attention to the date of the commit (dc358dc841b8ca),
> that was builded my QtC - it's 22.02.18. A really very old commit.
> But this is the last commit in my origin/4.6 branch.
> It's possible that something is wrong with my git repository.
> I use git-repo:  https://github.com/qtproject/qt-creator.git
>
> 11.04.2018 16:46, Aleksey Kontsevich пишет:
>>  Also think Qt version does matter and issues are related:
>>
>>  
>> https://bugreports.qt.io/browse/QTCREATORBUG-20178?focusedCommentId=397533=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-397533
>>
>>  Have successfully built v.4.5.2 branch with 5.10.0 on Linux (openSUSE). 
>> 4.5, 4.6, Qt5.10.1 - fail for some reason.
>>
>>  On Mac all builds fine.
>>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>
>>  11.04.2018, 16:20, "Eike Ziller" <eike.zil...@qt.io>:
>>>>    On 11. Apr 2018, at 15:05, Jason H <jh...@gmx.com> wrote:
>>>>
>>>>    It probably won't matter. The qml parser of qtc 4.6 is out of date as 
>>>> of 5.10. The patch landed the same day as the 4.6 branch. It's a pretty 
>>>> big oversight.
>>>  It most probably does matter.
>>>
>>>  There was https://bugreports.qt.io/browse/QTCREATORBUG-19757 with Qbs 
>>> files which was resolved for Qt Creator 4.6.0, so yes, please use something 
>>> like the v4.6.0 tag, or head of 4.6 branch.
>>>
>>>>>    Sent: Wednesday, April 11, 2018 at 1:52 PM
>>>>>    From: "Christian Kandeler" <christian.kande...@qt.io>
>>>>>    To: qt-creator@qt-project.org
>>>>>    Subject: Re: [Qt-creator] Migration from QtCreator 4.5 to 4.6
>>>>>
>>>>>    On Wed, 11 Apr 2018 12:15:40 +0300
>>>>>    Карелин Павел <hka...@yandex.ru> wrote:
>>>>>
>>>>>>    I decided to go over from QtC 4.5 to 4.6. I myself build QtC 4.6 of
>>>>>>    gitrev: dc358dc841b8ca84237de3fbadb1939801981d1a
>>>>>    Why are you using some random pre-release state? That makes little 
>>>>> sense. If you build yourself, you should use the current state of the 4.6 
>>>>> branch.
>>>>>
>>>>>    Christian
>>>>>    ___
>>>>>    Qt-creator mailing list
>>>>>    Qt-creator@qt-project.org
>>>>>    http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>>    ___
>>>>    Qt-creator mailing list
>>>>    Qt-creator@qt-project.org
>>>>    http://lists.qt-project.org/mailman/listinfo/qt-creator
>>>  --
>>>  Eike Ziller
>>>  Principal Software Engineer
>>>
>>>  The Qt Company GmbH
>>>  Rudower Chaussee 13
>>>  D-12489 Berlin
>>>  eike.zil...@qt.io
>>>  http://qt.io
>>>  Geschäftsführer: Mika Pälsi,
>>>  Juha Varelius, Mika Harjuaho
>>>  Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht 
>>> Charlottenburg, HRB 144331 B
>>>
>>>  ___
>>>  Qt-creator mailing list
>>>  Qt-creator@qt-project.org
>>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Migration from QtCreator 4.5 to 4.6

[Aleksey Kontsevich]

Also think Qt version does matter and issues are related:

https://bugreports.qt.io/browse/QTCREATORBUG-20178?focusedCommentId=397533=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-397533

Have successfully built v.4.5.2 branch with 5.10.0 on Linux (openSUSE). 4.5, 
4.6, Qt5.10.1 - fail for some reason.

On Mac all builds fine.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


11.04.2018, 16:20, "Eike Ziller" :
>>  On 11. Apr 2018, at 15:05, Jason H  wrote:
>>
>>  It probably won't matter. The qml parser of qtc 4.6 is out of date as of 
>> 5.10. The patch landed the same day as the 4.6 branch. It's a pretty big 
>> oversight.
>
> It most probably does matter.
>
> There was https://bugreports.qt.io/browse/QTCREATORBUG-19757 with Qbs files 
> which was resolved for Qt Creator 4.6.0, so yes, please use something like 
> the v4.6.0 tag, or head of 4.6 branch.
>
>>>  Sent: Wednesday, April 11, 2018 at 1:52 PM
>>>  From: "Christian Kandeler" 
>>>  To: qt-creator@qt-project.org
>>>  Subject: Re: [Qt-creator] Migration from QtCreator 4.5 to 4.6
>>>
>>>  On Wed, 11 Apr 2018 12:15:40 +0300
>>>  Карелин Павел  wrote:
>>>
  I decided to go over from QtC 4.5 to 4.6. I myself build QtC 4.6 of
  gitrev: dc358dc841b8ca84237de3fbadb1939801981d1a
>>>
>>>  Why are you using some random pre-release state? That makes little sense. 
>>> If you build yourself, you should use the current state of the 4.6 branch.
>>>
>>>  Christian
>>>  ___
>>>  Qt-creator mailing list
>>>  Qt-creator@qt-project.org
>>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] clang-tidy complains about Q_OBJECT macro

[Aleksey Kontsevich]

Yes, not exactly the same but similar:

Warning. The code model could not parse an included file, which might lead to 
slow or incorrect code completion and highlighting, for example.

type_traits:3070:7: error: expected ‘(‘ for function-style cast or type 
construction
QLoggingCategory:1:10: note: in file included from 
Qt/5.10.1/gcc_64/include/QtCore/QLoggingCategory:1:
qloggingcategory.h:43:10: note: in file included from 
Qt/5.10.1/gcc_64/include/QtCore/qloggingcategory.h:43:
qglobal.h:45:12: note: in file included from 
Qt/5.10.1/gcc_64/include/QtCore/qglobal.h:45:

Also it puts warning in lines with Q_OBJECT macro, and suggests to add override 
to objects' destructors, etc.

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


29.03.2018, 13:51, "Eike Ziller" :
> Looks like https://bugreports.qt.io/browse/QTCREATORBUG-17460
>
> Not sure why that reappeared for you.
>
> Br, Eike
>
>>  On Mar 29, 2018, at 11:51, timur.kris...@gmail.com wrote:
>>
>>  Hi!
>>
>>  I upgraded to Qt Creator 4.6.0 and was happy to see all the stuff that
>>  went in. However, it now dislikes the Q_OBJECT macro:
>>
>>  warning: unknown warning group '-Wsuggest-override', ignored
>>
>>  Looks like another disparity between gcc and clang warning options.
>>  I guess it somehow picks up this:
>>
>>  QT_WARNING_DISABLE_GCC("-Wsuggest-override")
>>
>>  instead of the correct clang-specific warning option.
>>
>>  Best regards,
>>  Timur
>>  ___
>>  Qt-creator mailing list
>>  Qt-creator@qt-project.org
>>  http://lists.qt-project.org/mailman/listinfo/qt-creator
>
> --
> Eike Ziller
> Principal Software Engineer
>
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> eike.zil...@qt.io
> http://qt.io
> Geschäftsführer: Mika Pälsi,
> Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
> HRB 144331 B
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] clang-tidy complains about Q_OBJECT macro

[Aleksey Kontsevich]

People in blog said it is: 
http://blog.qt.io/blog/2018/03/28/qt-creator-4-6-0-released/#comment-1202733

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


29.03.2018, 13:35, "timur.kris...@gmail.com" <timur.kris...@gmail.com>:
> Hello Aleksey,
>
> I think the bug report is about something else entirely.
>
> Regards,
> Timur
>
> On Thu, 2018-03-29 at 13:14 +0300, Aleksey Kontsevich wrote:
>>  https://bugreports.qt.io/browse/QTCREATORBUG-18757
>>  I have gcc 7.3.1 on my machine however still have this. Probably
>>  depends on gcc Qt Creator was built with - which is 5.3.1
>>
>>  --
>>  Best regards,
>>  Aleksey
>>  Linked in https://www.linkedin.com/in/alekseykontsevich
>>
>>  29.03.2018, 12:52, "timur.kris...@gmail.com" <timur.kris...@gmail.com
>>  >:
>>  > Hi!
>>  >
>>  > I upgraded to Qt Creator 4.6.0 and was happy to see all the stuff
>>  > that
>>  > went in. However, it now dislikes the Q_OBJECT macro:
>>  >
>>  > warning: unknown warning group '-Wsuggest-override', ignored
>>  >
>>  > Looks like another disparity between gcc and clang warning options.
>>  > I guess it somehow picks up this:
>>  >
>>  > QT_WARNING_DISABLE_GCC("-Wsuggest-override")
>>  >
>>  > instead of the correct clang-specific warning option.
>>  >
>>  > Best regards,
>>  > Timur
>>  > ___
>>  > Qt-creator mailing list
>>  > Qt-creator@qt-project.org
>>  > http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] clang-tidy complains about Q_OBJECT macro

[Aleksey Kontsevich]

https://bugreports.qt.io/browse/QTCREATORBUG-18757
I have gcc 7.3.1 on my machine however still have this. Probably depends on gcc 
Qt Creator was built with - which is 5.3.1

-- 
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich



29.03.2018, 12:52, "timur.kris...@gmail.com" :
> Hi!
>
> I upgraded to Qt Creator 4.6.0 and was happy to see all the stuff that
> went in. However, it now dislikes the Q_OBJECT macro:
>
> warning: unknown warning group '-Wsuggest-override', ignored
>
> Looks like another disparity between gcc and clang warning options.
> I guess it somehow picks up this:
>
> QT_WARNING_DISABLE_GCC("-Wsuggest-override")
>
> instead of the correct clang-specific warning option.
>
> Best regards,
> Timur
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Font size in Qt Creator 4.5.1 in Wayland

[Aleksey Kontsevich]

Letter was missed for some reason, sending again:
---
For me in Xorg on big monitor I have very small fonts and GUI elements. Known 
issue and it is not clear to me why Hi/LowDPI Qt improvements work fine in all 
Qt/KDE applications but not in Qt Creator and Qt Maintenance Tool? Think this 
issue could be fixed by applying modern UI style like Qt Curve or Breeze, but 
Qt Creator does not allow this for now: 
https://bugreports.qt.io/browse/QTCREATORBUG-18631?focusedCommentId=390416=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-390416

Reported issue: https://bugreports.qt.io/browse/QTCREATORBUG-18631
Hope this will be fixed. Not comfortable to work with such very small elements.

--
Best regards,
Aleksey
Linked in  https://www.linkedin.com/in/alekseykontsevich


24.02.2018, 18:06, "timur.kris...@gmail.com" :
> Hi,
>
> When I launch Qt Creator 4.5.1 in a Wayland session, it has a
> disturbingly enormous font size on its menus and GUI elements. This
> doesn't happen on Xorg, though.
>
> Is this a known issue or should I report a bug?
> Is there a workaround?
>
> Thanks & best regards,
> Timur
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Font size in Qt Creator 4.5.1 in Wayland

[Aleksey Kontsevich]

Letter was missed for some reason, sending again:---For me in Xorg on big monitor I have very small fonts and GUI elements. Known issue and it is not clear to me why Hi/LowDPI Qt improvements work fine in all Qt/KDE applications but not in Qt Creator and Qt Maintenance Tool? Think this issue could be fixed by applying modern UI style like Qt Curve or Breeze, but Qt Creator does not allow this for now: https://bugreports.qt.io/browse/QTCREATORBUG-18631?focusedCommentId=390416=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-390416 Reported issue: https://bugreports.qt.io/browse/QTCREATORBUG-18631Hope this will be fixed. Not comfortable to work with such very small elements. --Best regards,AlekseyLinked in  https://www.linkedin.com/in/alekseykontsevich  24.02.2018, 18:06, "timur.kris...@gmail.com" :Hi,When I launch Qt Creator 4.5.1 in a Wayland session, it has adisturbingly enormous font size on its menus and GUI elements. Thisdoesn't happen on Xorg, though.Is this a known issue or should I report a bug?Is there a workaround?Thanks & best regards,Timur___Qt-creator mailing listQt-creator@qt-project.orghttp://lists.qt-project.org/mailman/listinfo/qt-creator  Конец пересылаемого сообщения   -- Best regards,AlekseyLinked in  https://www.linkedin.com/in/alekseykontsevich ___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator