1

Topic: Qt VS Tools does not plow project discovery

Minimum a problem example: the Last version Qt the Last version Qt VS Tools Last  MSVS 1) I create in Qt Creator the project on Qt Widgets and I close the project 2) I open studio and through menu Qt VS Tool-> Open Qt Project file I open the file of the project created above 3) the studio reflects and produces an error "parsing *projectPath/ProjectName* - Nested quantifier +." And everything, the project does not open. Generally any Qt projects through this add-in do not open. Who in course - it is possible to make something that this add-in worked?

2

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS>... AS> Generally any Qt projects through this add-in do not open. AS> who in course - it is possible to make something that this add-in worked? Well it is possible  a plug-in, there it is a little code. And generally - what for to you such perversion? At me any more or less serious project did not manage to be translated in an automatic mode under . Where it is better to create new  from zero and to throw there the necessary files. And it is even better - to use something of type CMake if you need to support a little IDE.

3

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> Generally any Qt projects through this add-in do not open. AS> who in course - it is possible to make something that this add-in worked? Write in  or look same as at you, repair very operatively.

4

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> Minimum a problem example: AS> the Last version Qt AS> the Last version Qt VS Tools AS> Last  MSVS Yes, respected AeroSun, at me all the same is installed: Qt v 5.11.0 (Qt Creator v 4.6.1); Qt-VsAddin-msvc2017-2.2.0.vsix; MSVS-2017 CE; OS: Windows 7/64 SP1. On steps I fulfill everything on what you informed. The project we create for compilation under MSVC2017 (x64). AS> 1) I create in Qt Creator the project on Qt Widgets and I close project AS> 2) I open studio and through menu Qt VS Tool-> Open Qt Project file I open the file of project AS created above> 3) the studio reflects and produces an error "parsing *projectPath/ProjectName* - Nested quantifier +." AS> And everything, the project does not open. At me - the project opens successfully and compiled. Thus, I use adjustments: MSVC2017 (x64) AS> Generally any Qt projects through this add-in do not open. AS> who in course - it is possible to make something that this add-in worked? P.S. Adjustments Qt VS Addin: Name: msvc2017_64 Path: C:\Qt\Qt5.11.0\5.11.0\msvc2017_64 In System Variables - in ways of search Path = it is added: C:\Qt\Qt5.11.0\5.11.0\msvc2017_64\bin Variable QTDIR: C:\Qt\Qt5.11.0\5.11.0\msvc2017_64

5

Re: Qt VS Tools does not plow project discovery

Hello, SaZ, you wrote:... SaZ> And generally - what for to you such perversion? At me any more or less serious project did not manage to be translated in an automatic mode under . It NOT a perversion, and one of variants of quite regular usage of system of development. About "to translate in an automatic mode under " -  in a type to translate what has been made NOT UNDER Windows? SaZ> Where it is better to create new  from zero and to throw there the necessary files. And it is even better - to use something of type CMake if you need to support a little IDE. CMake - the good utility for  development. If at me the project for Linux, I quite probably prefer CMake (we had also such projects). Application CMake in  for Linux is especially actual, if the project does not use library Qt (but applies QtCreator as IDE). If all we do for Windows on Qt than the same is bad qmake... P.S. About development for Windows: For us volume enough projects (to tell - solutions with a considerable quantity of projects more precisely) and it is quite successfully worked with qmake. At least - while it is compiled for Windows - it is quite applicable qmake.

6

Re: Qt VS Tools does not plow project discovery

Hello, AlexGin, you wrote: AG> It NOT a perversion, and one of variants of quite regular usage of system of development. It not regular means, and a crutch to give though something to users who want with QtCreator to pass on MSVS. AG> About "to translate in an automatic mode under " -  in a type to translate what has been made NOT UNDER Windows? Means.pro->.sln AG> CMake - the good utility for  development.  here at anything. First of all it is a cross connect-IDE. AG> if at me the project for Linux, I will quite probably prefer CMake (we had also such projects). AG> Application CMake in  for Linux is especially actual, if the project does not use library Qt (but applies QtCreator as IDE). Under  with the same success it is possible and.pro files. You to yourselves complicate life. AG> if all we do for Windows on Qt than the same is bad qmake. . Only that it is supported only QtCreator th. AG> P.S. About development for Windows: for us volume enough projects (to tell - solutions with a considerable quantity of projects more precisely) and it is quite successfully worked with qmake. AG> At least - while it is compiled for Windows - it is quite applicable qmake. Speech not about the compiler, and about convenient IDE for development.

7

Re: Qt VS Tools does not plow project discovery

Hello, SaZ, you wrote: SaZ> And it is even better - to use something of type CMake if you need to support a little IDE. +1 If there is initial requirement MSVC and QtCreator CMake unambiguously it is better qmake (and generally cmake it is better). If courageous can look aside qbs: the correct system of the assembly with declarative JS-like language which supports generation of solutions for studio and has  support in QtCreator.

8

Re: Qt VS Tools does not plow project discovery

Hello, SaZ, you wrote: SaZ> Hello, AlexGin, you wrote: AG>> It NOT a perversion, and one of variants of quite regular usage of system of development. SaZ> it not regular means, and a crutch to give though something to users who want with QtCreator to pass on MSVS.... Which want to combine studio positive sides, with positive sides QtCreator AG>> CMake - the good utility for  development. SaZ> Krossplatforma here at anything. First of all it is a cross connect-IDE. CMake -  assembly system: https://habr.com/post/155467 Kross-IDE is the same QtCreator. AG>> If at me the project for Linux, I will quite probably prefer CMake (we had also such projects). AG>> Application CMake in  for Linux is especially actual, if the project does not use library Qt (but applies QtCreator as IDE). SaZ> Under  with the same success it is possible and.pro files. You to yourselves complicate life. As practice showed - is not complicated. As such development does not use itself Qt, and (as I already specified), apply QtCteator as IDE. Thus, we do not remain rigidly "fastened" on the same QtCteator - we use postulates Open Source of the community, allowing to have freedom of an independent choice of means of development AG>> If all we do for Windows on Qt than the same is bad qmake... SaZ> Only that it is supported only QtCreator th. +100500 Quite right, but in a context of projects under Windows on Qt it is comprehensible.

9

Re: Qt VS Tools does not plow project discovery

Hello, AlexGin, you wrote: AG>... Which want to combine studio positive sides, with positive sides QtCreator Aha, to cross  to a hedgehog. As here already many times wrote - MSVS better in all aspects, except for debugging QML. AG> CMake -  assembly system: https://habr.com/post/155467 On  to the link, the second sentence: "Thus itself CMake immediately Kross-IDE is not engaged in the assembly" AG> it is the same QtCreator. -IDE is means that cmake supports various IDE. And here generally QtCreator? We about different things speak to a campaign.

10

Re: Qt VS Tools does not plow project discovery

Hello, Skorodum, you wrote: S> If courageous can look aside qbs: the correct system of the assembly with declarative JS-like language which supports generation of solutions for studio and has  support in QtCreator. About generation of solutions did not know. Thanks, now I are mandatory  QBS, and that earlier hands all in any way did not reach. For a long time searched for analogs CMake.

11

Re: Qt VS Tools does not plow project discovery

Hello, SaZ, you wrote: SaZ> About generation of solutions did not know. Thanks, now I are mandatory  QBS, and that earlier hands all in any way did not reach. For a long time searched for analogs CMake. I just for fun tried recently on the simple project (some applications and libraries), worked without problems.

12

Re: Qt VS Tools does not plow project discovery

Hello, Skorodum, you wrote: S> If courageous can look aside qbs: the correct system of the assembly with declarative JS-like language which supports generation of solutions for studio and has  support in QtCreator. Twisted qbs - but it was not got to unwinding, a pair of clocks with  too did not help to get generation of solutions for studio, as a result I do an output - this thing still crude.

13

Re: Qt VS Tools does not plow project discovery

About, exposed System Variables and it was got - an error still shows, but the correct solution generates. Thanks)

14

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> Twisted qbs - but it was not got to unwinding, a pair of clocks with  too did not help to get generation of solutions for studio, as a result I do an output - this thing still crude. At me other experience the Author: Skorodum Date: 08.06 12:20 In what at you a problem "Hello World" from command line  can?

15

Re: Qt VS Tools does not plow project discovery

Hello, Skorodum, you wrote: S> At me other experience the Author: Skorodum Date: 08.06 12:20 S> In what at you a problem "Hello World" from command line  can? Yes. And Qt it is delivered through them  on  to ways. That  cannot find,  to launch etc. Through a pair of clocks of fuss I understood that it is all not seriously.

16

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> Yes. And Qt it is delivered through them  on  to ways. That  cannot find,  to launch etc. Through a pair of clocks of fuss I understood that it is all not seriously. While it is more similar to curve hands or not ability to read steam of pages of the documentation

17

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> About, exposed System Variables and it was got - an error still shows, but the correct solution generates. Thanks) Nazdorove!!! And what for an error?

18

Re: Qt VS Tools does not plow project discovery

Hello, AlexGin, you wrote: AG>>> It NOT a perversion, and one of variants of quite regular usage of system of development. SaZ>> it not regular means, and a crutch to give though something to users who want with QtCreator to pass on MSVS. AG>... Which want to combine studio positive sides, with positive sides QtCreator Here it is possible more in detail about positive sides? Impart experience. When and what for two systems of development use?

19

Re: Qt VS Tools does not plow project discovery

Hello, Iso12, you wrote: I> Here it is possible more in detail about positive sides? Impart experience. I> when and what for two systems of development use? Such pretty often. Whatever one may do the main commercial development goes only under Windows. Under it unique convenient IDE for With ++ (studio + VAX). Some parts of projects it is necessary to do a cross connect platform most, or a part of such projects from the third commands. And under other OS it is necessary to use for pluses only Qt Creator (opensource the community and could not give birth to convenient tools for With ++). Here also quits that you want you do not want, and it is necessary to use and the second IDE. Well and the second: QML it is better to write in QtCreator - as only there there is its support.

20

Re: Qt VS Tools does not plow project discovery

Hello, AlexGin, you wrote: AG> And what for an error? That that in the initial message - "parsing *projectPath/ProjectName* - Nested quantifier +.". Time a solution forms now the worker, it seems that it  something another. Strange.

21

Re: Qt VS Tools does not plow project discovery

Hello, Iso12, you wrote:... AG>>... To combine studio positive sides, with positive sides QtCreator... I> Here it is possible more in detail about positive sides? Impart experience. I> when and what for two systems of development use? These are the general reasons on the given subject: https://stackoverflow.com/questions/288 … studio-ide https://www.slant.co/versus/2474/4792/~ … qt-creator Now personally my reasons FOR QtCreator: 1) Creation of the new project on Qt; 2) Creation, development, editing dialogue and other GUI forms (QML and classical ); 3) Specific cases. An example: support.rep files (and options REPC_REPLICA, REPC_SOURCE) for development Qt Remote Object of projects; 4) It is convenient in a case when are not anchored to Windows (and in particular if in the project it is not applied at all Qt). FOR MSVS: 1) convenience of editing of the codes of the project (support dockable editors of files of the project); 2) it is immediate GUI development systems - where more conveniently and more floppy for the user; 3) rather convenient and thought over navigation under the project; 4) very convenient debugger and process of debugging; 5) Good IntelliSense, especially it is actual in MSVC-2017; 6) thought More over system of parsing of a C ++ syntax (at code writing - selection of incorrect expressions); 7) Intergatsija with monitoring systems of versions (as an example - with  GIT th) here is more convenient. In general - time lion's share by development - it is led in studio (MSVC-2017 CE) and some, rather small time, - in QtCreator P.S. My own reasons enumerated more low, quite probably, seem to someone not justified. It is not necessary to perceive all it in the form of the ultimate truth Here - more likely a matter of taste and personal preferences, instead of . P.P.S. From the list of advantages MSVS I removed operation with two monitors - as QtCreator v4.6.1 also allows to carry out a window on the dop/monitor.

22

Re: Qt VS Tools does not plow project discovery

Hello, AlexGin, you wrote: AG> FOR QtCreator: 80 % of actions: editing, navigation, integration with , the assembly. AG> FOR MSVS: the Debugger. All remaining in Kreatore is much better.

23

Re: Qt VS Tools does not plow project discovery

Hello, Skorodum, you wrote: S> Hello, AlexGin, you wrote: AG>> FOR QtCreator: S> 80 % of actions: editing, navigation, integration with , the assembly. AG>> FOR MSVS: S> the Debugger. All remaining in Kreatore is much better. What there can be better? - "Integration with "? - In  it is better only if studio never used. - "assembly"? - Studio solutions from them.props is actually the standard of the assembly, competitors are not present. - "navigation"? - Here even to argue there is nothing. At first  it is much more convenient than open files in . In the second - besides  which it is possible to add a side-about-side to hang out on remaining monitors + considering them with integration in Win a desktop - similar convenience is not given  by the environment. In  one pain to edit if the code is arranged in many places. And "Peek definition"? Yes well, after that it does not turn out to consider seriously  (I am not assured even not that there generally ever there will be a similar functionality). - etc. But! We not consider bare studio, and a standard development environment under with ++? In this case without VAX at all has no sense to compare. And with VAX: - VA View - with absence of this piece at once it is possible to give-90 efficiency % on the big or unfamiliar projects. Actually it is the killer-feature - any another IDE cannot make alternative of studio if it has given piece. - VA Outline - with absence of this piece it is necessary to add still-90 efficiency % on unfamiliar projects and absence of convenience at the big refactoring - VA Hashtags - in heavy and big projects the invaluable help, especially rescues in  - additional helps - additional navigation, + list methods, open correcponding file, find references (!!! Who it  - is already difficult when there is no), illumination of places where the variable (the same for reading) - additional means of refactoring -  changes (yes, they around are, but here it is the most convenient) - code inspection Therefore  against studio looks as a notepad against Word. The majority of a functional simply misses, or in embryo, or is made inconveniently. But yes, Qt Creator is the best that there is for not-Windows OS.

24

Re: Qt VS Tools does not plow project discovery

Hello, AeroSun, you wrote: AS> - "integration with "? - In  it is better only if studio never used." git blame "," git rebase - interactive "," git stash "in studio already is? With normal ? AS> -"assembly"? - Studio solutions from them.props is actually the standard of the assembly, competitors are not present. Ridiculously. All topic about inability of studio to work with different systems of the assembly. AS> -"navigation"? - Here even to argue there is nothing. At first  it is much more convenient than open files in . Nonsense.  is a self-deception. If at you the big project at you ten open files, visual navigation on  - the anti-pattern which reduces productivity. AS> in the second - besides  which it is possible to add a side-about-side to hang out on remaining monitors + considering them with integration in Win a desktop - similar convenience is not given  by the environment. In  it is possible to open some editors and to dissolve them on different monitors, only at normal navigation it rarely is necessary AS> In  one pain to edit if the code is arranged in many places. Well if to try to pass by means of a mouse - can be yes. But all power in F2 ("Follow symbol under cursor") and a locator (passage to classes, methods, files etc. including fuzzy logic) and passage forward-back as in the browser. AS> and "Peek definition"? Horror. In : F2, looked and "alt+left" to return reversely. AS> yes well after that it does not turn out to consider seriously  (I it is not assured even not that there generally ever there will be a similar functionality). The studio is a deadlock way of evolution in respect of editing, nobody repeats their approach, and MSEC saw Visual Studio Code. AS> But! We not consider bare studio, and a standard development environment under with ++? In this case without VAX at all has no sense to compare. In-in, without a paid plug-in the studio is not made absolutely not (except for a debugger). AS> And with VAX: AS> - VA View - with absence of this piece at once it is possible to give-90 efficiency % on the big or unfamiliar projects. Actually it is the killer-feature - any another IDE cannot make alternative of studio if it has given piece. AS> - VA Outline - with absence of this piece it is necessary to add still-90 efficiency % on unfamiliar projects and absence of convenience at the big refactoring AS> - VA Hashtags - in heavy and big projects the invaluable help, especially rescues in  AS> - additional helps AS> - additional navigation, + list methods, open correcponding file, find references (!!! Who it  - is already difficult when there is no), illumination of places where the variable (the same for reading) AS> - additional means of refactoring AS> -  changes (yes, they around are, but here it is the most convenient) AS> - code inspection If to translate with bird's on normal it appears that considerable part of it is in Kreatore from a box. Free of charge. . AS> Therefore  against studio looks as a notepad against Word. The majority of a functional simply misses, or in embryo, or is made inconveniently. Well it is clear, as well as in a case with qbs to be beyond the learned template - in any way.

25

Re: Qt VS Tools does not plow project discovery

Hello, Skorodum, you wrote:... AG> FOR QtCreator: S> 80 % of actions: editing, navigation, integration with , the assembly.... AG> FOR MSVS: S> the Debugger. All remaining in Kreatore is much better. Respected Skorodum! I expressed my point of view. It at all does not mean that at you it should coincide with mine P.S. Under integration with the code monitoring system, I imply that fact that GitExtensions at me are integrated in MSVC. In MSVC I see a toolbar and the menu - allowing me directly to work with my favourite monitoring system of versions (Git) and its graphic jacket (GitExtensions). Thus, I do not have necessity somewhere to quit studio, to fulfill "commit" and other commands Git. Unfortunately, the given behavior is not watched in QtCreator (though and in  support for Git is made ).