Re: [Qt-creator] Refactor > generate missing property members Crunchiness

[Jason H]

So My 4.15, when adding the memer implementations now puts them in the .cpp (yay)

But very minor feedback - it drops you into the .cpp (yay) where you last were, but the implementation is added at the bottom.

 

From a wrkflow perspective, it would make sense to scroll to the bottom where the code is adde (for immediate editing), or stay in (or pop back to) the header for more Generate Missing... goodness, so that you can get up the Q_PROPERTY lines then right click and generate a bunch at once. (Either by selecting several or repeatedly right-clicking)

 

Regardless, I'm really enjoying the 4.14->4.15 improvement!
 

 

 
 

Sent: Wednesday, May 12, 2021 at 10:30 AM
From: "Leander Schulten" 
To: "Jason H" 
Cc: "qt-creator" 
Subject: Re: [Qt-creator] Refactor > generate missing property members Crunchiness


1. You mean the function body? There is a setting for that in the QtC 4.15. See the Quickfixes section at https://www.qt.io/blog/qt-creator-4.15-whats-new-in-c-support-0

 

 




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

Re: [Qt-creator] [Interest] WASM build Error: Bad relocation type

[Jason H]

> However I blew away the build dir and did a full rebuild now and got:
> wasm-ld: error: initial memory too small, 21088512 bytes needed
>
> Command line contains: "--initial-memory=16777216 --no-entry 
> --global-base=1024"
>
> Progress! :-) How do I change the memory setting [in QtCreator]? According to 
> something I read on the internet,
> wasm {
>   QMAKE_TOTAL_MEMORY=21233664
> }
>
> Should fix it. But the commandline --inital-memory didn't change. Help?



Ok Success, kinda. It crashes.

Firat: Fixing the inital memory error:

wasm {
QMAKE_TOTAL_MEMORY=21495808 # ignored for some reason
QMAKE_LFLAGS += -s TOTAL_MEMORY=21495808
}

Then, when QtCreator attempts to start the page:
 /bin/sh /Users/jason/Projects/emsdk/upstream/emscripten/emrun --browser chrome 
--port 3 --no_emrun_detect --serve_after_close 
/Users/jason/Projects/poc-ui-Qt_5_15_1_WebAssembly-Debug/poc-ui.html
from: can't read /var/mail/tools
/Users/jason/Projects/emsdk/upstream/emscripten/emrun: line 9: syntax error 
near unexpected token `__file__'
/Users/jason/Projects/emsdk/upstream/emscripten/emrun: line 9: `  
python_selector.run(__file__)'

However, this confuses python (and me). Removing the /bin/sh from the QtCreator 
command line (at a console)gets it to start and load the page.
Leaving the /bin/sh in, gets you that `from: can't read /var/mail/tools`, 
because it is interpreting the python code as a shell script.

Being on Mac, I wondered if it was a zsh issue, but running a bash shell then 
the QtCreator command line, I get the same result.

Changing the "effective run call" in QtC did not help





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

Re: [Qt-creator] Debugging app using Camera on MacOS?

[Jason H]

True there is some risk of an infinite loop if the make `touch`es the Makefile, 
to maybe there is a way to compare hashes?
> 
> Make supposedly supports re-creating the Makefile in a rule:
> 
> https://www.gnu.org/software/make/manual/html_node/Remaking-Makefiles.html
> 
> "If a makefile has a rule which says how to update it (found either in that 
> very makefile or in another one) or if an implicit rule applies to it (see 
> Using Implicit Rules), it will be updated if necessary. After all makefiles 
> have been checked, if any have actually been changed, make starts with a 
> clean slate and reads all the makefiles over again.”
> 
> So it sees the rule for “Makefile: ….”, executes it if required, checks if 
> the Makefile changed, and restarts itself if so.


Thank you for that tidbit. I wonder what explains my behavior then?
I really do know how to use a computer, I promise! :-)

Anyway, it's working now (the Info.plist)




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

Re: [Qt-creator] Debugging app using Camera on MacOS?

[Jason H]

Just realized, after the make inception, you'll have bail out of the first 
make. I'm not a Makefile guru, such things are beyond me at this point. 

> Sent: Wednesday, May 19, 2021 at 9:36 AM
> From: "Jason H" 
> To: "Eike Ziller" 
> Cc: "qt-creator" 
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>
> Ok, I have that rule too, but does it re-invoke make after updating? It seems 
> to continue to process the old, out of date Makefile?
> After 
>$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
> It either needs to say something like:
>Makefile updated; run make again
> or:
>make
> So:
> $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
> make
> 
> True there is some risk of an infinite loop if the make `touch`es the 
> Makefile, to maybe there is a way to compare hashes?
> 
> 
> 
> > Sent: Wednesday, May 19, 2021 at 3:34 AM
> > From: "Eike Ziller" 
> > To: "Jason H" 
> > Cc: "qt-creator" 
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> >
> > 
> > 
> > > On May 18, 2021, at 18:58, Jason H  wrote:
> > > 
> > >  
> > > So I am dumb. I forgot that among all those popups QtCreator gives you 
> > > when you save the .pro, running qmake is not one of them
> > > I *thought* running  qmake would have been automatic when the .pro 
> > > changes. (Or that the Makefile would pick up the .pro was modified and 
> > > run qmake automatically) but that doesn't seem to be the case?
> > > 
> > 
> > The Makefile _should_ have a rule for re-running qmake when the .pro file 
> > is changed. My dummy project has
> > 
> > Makefile: ../qmake_widgets/qmake_widgets.pro ……
> > ...
> > $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
> > 
> > Which is tricky because while running “make”, the Makefile is changed…. but 
> > it is supposed to work.
> > 
> > Br, Eike
> > 
> > > 
> > > Sent: Tuesday, May 18, 2021 at 11:53 AM
> > > From: "Jason H" 
> > > To: "Jason H" 
> > > Cc: "qt-creator" 
> > > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > > Accidentally only replied to Lars before, but for the list, for 
> > > throughness:
> > > Thanks Lars.
> > >  
> > > I have added in the .pro
> > > mac {
> > > QMAKE_INFO_PLIST = macos/Info.plist
> > > }
> > > 
> > >  
> > > And the plist was copied from the build directory, added the key/string 
> > > pair:
> > > NSCameraUsageDescription
> > > Reads Barcodes
> > > 
> > > And still no joy. The Info.plist in the package contents is not the one 
> > > with the added key.
> > > I tried mac, macx, and macos for the platform in .pro. QtCreator shows 
> > > int he Project pane:
> > > Other Files /
> > > .. v macos
> > >  Info.plist 
> > >  
> > > So the file is there. It's just not being used. I have NOT set CONFIG -= 
> > > app_bundle. Looking at the compile output, Info.plist does not appear in 
> > > the compile output pane.
> > >  
> > > It seems that something else is needed than QMAKE_INFO_PLIST? 
> > >  
> > > ...
> > > ANSWER: Yes it needs a manual copy (currently). Then I filed  
> > > https://bugreports.qt.io/browse/QTBUG-93832
> > >  
> > >  
> > > Sent: Tuesday, May 18, 2021 at 11:25 AM
> > > From: "Jason H" 
> > > To: "Lars Knoll" 
> > > Cc: "qt-creator" 
> > > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > > I got it working with a manual copy, but also filed:
> > > https://bugreports.qt.io/browse/QTBUG-93832
> > >  
> > >  
> > >  
> > > Sent: Tuesday, May 18, 2021 at 4:40 AM
> > > From: "Lars Knoll" 
> > > To: "Eike Ziller" 
> > > Cc: "Jason H" , "qt-creator" 
> > > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > > On 17 May 2021, at 18:50, Eike Ziller  wrote:
> > > On May 17, 2021, at 16:27, Jason H  wrote:
> > > 
> > > Here is the question (asked by someone else) (Note this is specific to 
> > > *debugging* the app.)
> > > https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
> > > with no good resolution.
&

Re: [Qt-creator] Debugging app using Camera on MacOS?

[Jason H]

Ok, I have that rule too, but does it re-invoke make after updating? It seems 
to continue to process the old, out of date Makefile?
After 
   $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
It either needs to say something like:
   Makefile updated; run make again
or:
   make
So:
$(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
make

True there is some risk of an infinite loop if the make `touch`es the Makefile, 
to maybe there is a way to compare hashes?



> Sent: Wednesday, May 19, 2021 at 3:34 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: "qt-creator" 
> Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
>
> 
> 
> > On May 18, 2021, at 18:58, Jason H  wrote:
> > 
> >  
> > So I am dumb. I forgot that among all those popups QtCreator gives you when 
> > you save the .pro, running qmake is not one of them
> > I *thought* running  qmake would have been automatic when the .pro changes. 
> > (Or that the Makefile would pick up the .pro was modified and run qmake 
> > automatically) but that doesn't seem to be the case?
> > 
> 
> The Makefile _should_ have a rule for re-running qmake when the .pro file is 
> changed. My dummy project has
> 
> Makefile: ../qmake_widgets/qmake_widgets.pro ……
> ...
> $(QMAKE) -o Makefile ../qmake_widgets/qmake_widgets.pro ….
> 
> Which is tricky because while running “make”, the Makefile is changed…. but 
> it is supposed to work.
> 
> Br, Eike
> 
> > 
> > Sent: Tuesday, May 18, 2021 at 11:53 AM
> > From: "Jason H" 
> > To: "Jason H" 
> > Cc: "qt-creator" 
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > Accidentally only replied to Lars before, but for the list, for throughness:
> > Thanks Lars.
> >  
> > I have added in the .pro
> > mac {
> > QMAKE_INFO_PLIST = macos/Info.plist
> > }
> > 
> >  
> > And the plist was copied from the build directory, added the key/string 
> > pair:
> > NSCameraUsageDescription
> > Reads Barcodes
> > 
> > And still no joy. The Info.plist in the package contents is not the one 
> > with the added key.
> > I tried mac, macx, and macos for the platform in .pro. QtCreator shows int 
> > he Project pane:
> > Other Files /
> > .. v macos
> >  Info.plist 
> >  
> > So the file is there. It's just not being used. I have NOT set CONFIG -= 
> > app_bundle. Looking at the compile output, Info.plist does not appear in 
> > the compile output pane.
> >  
> > It seems that something else is needed than QMAKE_INFO_PLIST? 
> >  
> > ...
> > ANSWER: Yes it needs a manual copy (currently). Then I filed  
> > https://bugreports.qt.io/browse/QTBUG-93832
> >  
> >  
> > Sent: Tuesday, May 18, 2021 at 11:25 AM
> > From: "Jason H" 
> > To: "Lars Knoll" 
> > Cc: "qt-creator" 
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > I got it working with a manual copy, but also filed:
> > https://bugreports.qt.io/browse/QTBUG-93832
> >  
> >  
> >  
> > Sent: Tuesday, May 18, 2021 at 4:40 AM
> > From: "Lars Knoll" 
> > To: "Eike Ziller" 
> > Cc: "Jason H" , "qt-creator" 
> > Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?
> > On 17 May 2021, at 18:50, Eike Ziller  wrote:
> > On May 17, 2021, at 16:27, Jason H  wrote:
> > 
> > Here is the question (asked by someone else) (Note this is specific to 
> > *debugging* the app.)
> > https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
> > with no good resolution.
> > 
> > It seems the way QtC is launching the debugger is running afoul of the 
> > NSCameraUsageDescription. Has anyone else figured out a way around this?
> > I'm wondering if the Info.plist needs to be applied to LLDB somehow?
> > 
> > I don’t quite understand if this is a Qt Creator specific issue or not.
> > 
> > If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe 
> > running the app without debugging and then Debug > Start debugging > Attach 
> > to running application helps.
> >  
> > I’ve been doing some debugging of the camera on macOS lately. You do need 
> > to add the Info.plist with 
> > NSCameraUsageDescription/NSMicrophoneUsageDescription to your app to allow 
> > camera/microphone access. 
> >  
> > After that, you might get a confirmation dialog to allow access on

Re: [Qt-creator] Debugging app using Camera on MacOS?

[Jason H]

 


So I am dumb. I forgot that among all those popups QtCreator gives you when you save the .pro, running qmake is not one of them

I *thought* running  qmake would have been automatic when the .pro changes. (Or that the Makefile would pick up the .pro was modified and run qmake automatically) but that doesn't seem to be the case?

 

 

 

Sent: Tuesday, May 18, 2021 at 11:53 AM
From: "Jason H" 
To: "Jason H" 
Cc: "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?



Accidentally only replied to Lars before, but for the list, for throughness:


Thanks Lars.

 

I have added in the .pro


mac {
QMAKE_INFO_PLIST = macos/Info.plist
}

 

And the plist was copied from the build directory, added the key/string pair:


NSCameraUsageDescription
Reads Barcodes


And still no joy. The Info.plist in the package contents is not the one with the added key.

I tried mac, macx, and macos for the platform in .pro. QtCreator shows int he Project pane:

Other Files /

.. v macos

 Info.plist 

 

So the file is there. It's just not being used. I have NOT set CONFIG -= app_bundle. Looking at the compile output, Info.plist does not appear in the compile output pane.

 

It seems that something else is needed than QMAKE_INFO_PLIST? 

 

...

ANSWER: Yes it needs a manual copy (currently). Then I filed  https://bugreports.qt.io/browse/QTBUG-93832



 
 

Sent: Tuesday, May 18, 2021 at 11:25 AM
From: "Jason H" 
To: "Lars Knoll" 
Cc: "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?



I got it working with a manual copy, but also filed:

https://bugreports.qt.io/browse/QTBUG-93832

 

 
 

Sent: Tuesday, May 18, 2021 at 4:40 AM
From: "Lars Knoll" 
To: "Eike Ziller" 
Cc: "Jason H" , "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?





On 17 May 2021, at 18:50, Eike Ziller <eike.zil...@qt.io> wrote:


On May 17, 2021, at 16:27, Jason H <jh...@gmx.com> wrote:

Here is the question (asked by someone else) (Note this is specific to *debugging* the app.)
https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
with no good resolution.

It seems the way QtC is launching the debugger is running afoul of the NSCameraUsageDescription. Has anyone else figured out a way around this?
I'm wondering if the Info.plist needs to be applied to LLDB somehow?

I don’t quite understand if this is a Qt Creator specific issue or not.

If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe running the app without debugging and then Debug > Start debugging > Attach to running application helps.


 

I’ve been doing some debugging of the camera on macOS lately. You do need to add the Info.plist with NSCameraUsageDescription/NSMicrophoneUsageDescription to your app to allow camera/microphone access. 

 

After that, you might get a confirmation dialog to allow access on first launch. Once that’s confirmed, you should be able to debug the app just fine. At least it does work for me using Qt Creator.

 

Cheers,

Lars

 






___ 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] Debugging app using Camera on MacOS?

[Jason H]

Accidentally only replied to Lars before, but for the list, for throughness:


Thanks Lars.

 

I have added in the .pro


mac {
QMAKE_INFO_PLIST = macos/Info.plist
}

 

And the plist was copied from the build directory, added the key/string pair:


NSCameraUsageDescription
Reads Barcodes


And still no joy. The Info.plist in the package contents is not the one with the added key.

I tried mac, macx, and macos for the platform in .pro. QtCreator shows int he Project pane:

Other Files /

.. v macos

 Info.plist 

 

So the file is there. It's just not being used. I have NOT set CONFIG -= app_bundle. Looking at the compile output, Info.plist does not appear in the compile output pane.

 

It seems that something else is needed than QMAKE_INFO_PLIST? 

 

...

ANSWER: Yes it needs a manual copy (currently). Then I filed  https://bugreports.qt.io/browse/QTBUG-93832



 
 

Sent: Tuesday, May 18, 2021 at 11:25 AM
From: "Jason H" 
To: "Lars Knoll" 
Cc: "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?



I got it working with a manual copy, but also filed:

https://bugreports.qt.io/browse/QTBUG-93832

 

 
 

Sent: Tuesday, May 18, 2021 at 4:40 AM
From: "Lars Knoll" 
To: "Eike Ziller" 
Cc: "Jason H" , "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?





On 17 May 2021, at 18:50, Eike Ziller <eike.zil...@qt.io> wrote:


On May 17, 2021, at 16:27, Jason H <jh...@gmx.com> wrote:

Here is the question (asked by someone else) (Note this is specific to *debugging* the app.)
https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
with no good resolution.

It seems the way QtC is launching the debugger is running afoul of the NSCameraUsageDescription. Has anyone else figured out a way around this?
I'm wondering if the Info.plist needs to be applied to LLDB somehow?

I don’t quite understand if this is a Qt Creator specific issue or not.

If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe running the app without debugging and then Debug > Start debugging > Attach to running application helps.


 

I’ve been doing some debugging of the camera on macOS lately. You do need to add the Info.plist with NSCameraUsageDescription/NSMicrophoneUsageDescription to your app to allow camera/microphone access. 

 

After that, you might get a confirmation dialog to allow access on first launch. Once that’s confirmed, you should be able to debug the app just fine. At least it does work for me using Qt Creator.

 

Cheers,

Lars

 






___ 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] Debugging app using Camera on MacOS?

[Jason H]

I got it working with a manual copy, but also filed:

https://bugreports.qt.io/browse/QTBUG-93832

 

 
 

Sent: Tuesday, May 18, 2021 at 4:40 AM
From: "Lars Knoll" 
To: "Eike Ziller" 
Cc: "Jason H" , "qt-creator" 
Subject: Re: [Qt-creator] Debugging app using Camera on MacOS?





On 17 May 2021, at 18:50, Eike Ziller <eike.zil...@qt.io> wrote:


On May 17, 2021, at 16:27, Jason H <jh...@gmx.com> wrote:

Here is the question (asked by someone else) (Note this is specific to *debugging* the app.)
https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
with no good resolution.

It seems the way QtC is launching the debugger is running afoul of the NSCameraUsageDescription. Has anyone else figured out a way around this?
I'm wondering if the Info.plist needs to be applied to LLDB somehow?

I don’t quite understand if this is a Qt Creator specific issue or not.

If the issue is that Qt Creator starts lldb, and lldb starts the app, maybe running the app without debugging and then Debug > Start debugging > Attach to running application helps.


 

I’ve been doing some debugging of the camera on macOS lately. You do need to add the Info.plist with NSCameraUsageDescription/NSMicrophoneUsageDescription to your app to allow camera/microphone access. 

 

After that, you might get a confirmation dialog to allow access on first launch. Once that’s confirmed, you should be able to debug the app just fine. At least it does work for me using Qt Creator.

 

Cheers,

Lars

 





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

[Qt-creator] Debugging app using Camera on MacOS?

[Jason H]

Here is the question (asked by someone else) (Note this is specific to 
*debugging* the app.)
https://stackoverflow.com/questions/60459036/how-do-i-debug-an-app-on-the-mac-that-accesses-the-camera
with no good resolution.

It seems the way QtC is launching the debugger is running afoul of the 
NSCameraUsageDescription. Has anyone else figured out a way around this?
I'm wondering if the Info.plist needs to be applied to LLDB somehow?


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

[Qt-creator] Refactor > generate missing property members Crunchiness

[Jason H]

1. I love that QtC can "Generate missing property members"
But I don't love that it generates the function definition in the .h file

2. I love that QtC can "Move the definition to the .cpp file"
But I don't love that it drops you into the .cpp file. Then I have to go back 
to the file and repeat. Given that a property typically has a getter and a 
setter, I am doing this twice for each proeprty.


1&2 could be fixed by a variety of resolutions:
a. "Generate missing property members" automatically generating them in the 
.cpp file
b. add "Generate missing property members in .cpp" option
c. minimally, just leaving me in the .h file

I seem to have discovered a bug in the auto-completion of the Q_PROPERTY(type 
name ...) generation. If you tab though and loop back around, when I "generated 
missing property members", it generated them with "x" as the type - an actual 
x, and not the type in the Q_PROPERTY statement
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Class wizard minor feedback

[Jason H]

When choosing a base class in the class wizard, combo box entries are 
duplicated.
(Attached)

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

[Qt-creator] Plugin Idea: Record application?

[Jason H]

Is there already a plug in, or how cool would it be, that you can record an 
application window (having been run in QtC) with a button in the QtC UI?
Maybe even capture the application output pane in SRT format?), so you can see 
in near-real-time the application debug output?


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

[Qt-creator] QML_ELEMENT crunchiness

[Jason H]

I have the QML_ELEMENT a shot today on a class.

+++ pro.pro
CONFIG += qmltypes
QML_IMPORT_NAME = com.company
QML_IMPORT_MAJOR_VERSION = 1

+++ class.cpp
#include 

class JsonSerialPort : public QObject
{
Q_OBJECT
QML_ELEMENT
...
}

However this method is interior to my experience using the old qmlRegister() 
integration.
1. In QML file, the import statement gives: "QML Module not found" in the 
linter.
2. No contezt sensitive autocompletion is offered.

I expected these to be resolved on compile of the project, but they were not.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Fonts duplicated in translation list?

[Jason H]

When in the project wizard, and you say yes to translations, and it asks you to 
pick them, some are (seemingly) duplicated.
I'm not sure if there is some language variant that makes these not duplicates?

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

[Qt-creator] QTimer::timeout is not a signal?

[Jason H]

I'm getting this message rom clazy in QtCreator, but I'm pretty sure 
::timeout /is/ a signal?
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Switching to more "semantic" versioning scheme

[Jason H]

> Sent: Wednesday, March 24, 2021 at 5:05 AM
> From: "Eike Ziller" 
> To: "qt-creator" 
> Subject: [Qt-creator] Switching to more "semantic" versioning scheme
>
> We want to switch Qt Creator to semantic versioning, which means bumping the 
> major version for each feature release, since we don’t keep binary 
> compatibility between these.
> 
> - Next release after 4.15 is Qt Creator 5.
> - Followed by Qt Creator 6 in December 2021.
> - Qt Creator 7 in spring 2022
> - and so on.

Though I understand the reasoning, I think this would be confusing. 
Qt Creator has definite impact on Qt code, w.r.t. parsing. I'm thinking of how 
many
releases it took QtC to support QML Enums. I think a more meaningful system 
would
be to version it with the Qt build version, with the Z (x.y.z) being the 
Qt Creator release with Qt version x.y. 

Examples: 
Qt Creator 5.15.4 (5th release based on Qt 5.15.2)
Qt Creator 6.0.1. (2nd release based on 6.0)

Compared to:
Qt Creator 7 in 2022,
Qt Creator 9 in 2023,
Qt Creator 13 in 2025,
Qt Creator 23 in 2030.
Qt Creator 33 in 2040.


Or maybe no one cares about the QtCreator Qt built-with version? And maybe I 
shouldn't care either? 
I just always wonder "What is an appropriate version of QtC to be using with Qt 
x.y?"

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

Re: [Qt-creator] Java support?

[Jason H]

> Sent: Friday, September 11, 2020 at 3:41 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: "qt-creator" 
> Subject: Re: [Qt-creator] Java support?
>
> 
> 
> > On Sep 10, 2020, at 20:21, Jason H  wrote:
> > 
> > I'm working in an Android/iOS app and while creator is just fine for 
> > iOS/Objective-C, QtCreator is not fine at all for Android/Java.
> > 
> > I'm wondering how close QtCreator is to being able to:
> > * present the java files and classes in the Project explorer (gradle 
> > integration?)
> 
> I don’t see gradle integration coming. When we’d finished it, Google would 
> probably switch to something else :P

I guess they already have in the sense that Kotlin is now an Android language. 
:-( But it seems that Gradle is here to stay.

> But you should be able to use a Generic Project for that: File > New > Import 
> Project > Import Existing Project. (For the language server you should 
> probably import the module base directory?)
> That could probably be made more obvious… like not putting it at the end of a 
> category with lots of version control related items, and calling it something 
> like Import Directory or such (there doesn’t need to be a “project” of any 
> kind).
> 
> > * parse and edit Java code
> > 
> > I'm thinking the language server would do a lot of the heavy lifting?
> 
> The java-language-server would/should solve the “parse and edit” part.
> I have not tried it, but probably setting it up as “Start Server per Project” 
> is required, and probably having the module path as the base of the Qt 
> Creator project.
> Also, Qt Creator still has a specialized Java editor from the pre-LSP times, 
> which might interfere with the language client, so switching the handler for 
> text/x-java to “Plain Text Editor” in Preferences > Environment > MIME Types 
> might be needed to.
> 
> I agree that someone should check this, potentially throwing the old Java 
> editor away, and maybe Qt Creator can help a bit with setting up the Java 
> language server too, similar to what we do for Python.

+1 

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

[Qt-creator] Java support?

[Jason H]

I'm working in an Android/iOS app and while creator is just fine for 
iOS/Objective-C, QtCreator is not fine at all for Android/Java.

I'm wondering how close QtCreator is to being able to:
* present the java files and classes in the Project explorer (gradle 
integration?)
* parse and edit Java code

I'm thinking the language server would do a lot of the heavy lifting?

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

[Qt-creator] Just noticed minor ui consistency thing: text highlight

[Jason H]

The default matched text color is yellow highlight. But the find occurrences 
are green in the scroll bar.
Shouldn't the default highlight be green to match? Yellow is taken by warnings, 
red by errors, and are highlighted as such.

Also, shouldn't breakpoints also appear in the scroll bar (the decorator is 
also red... but maybe we can make them blue?)


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

Re: [Qt-creator] Adding kits to Qt Creator in a more noob-friendly way

[Jason H]

> Sent: Monday, May 18, 2020 at 9:07 AM
> From: "Robert Löhning" 
> To: qt-creator@qt-project.org
> Subject: Re: [Qt-creator] Adding kits to Qt Creator in a more noob-friendly 
> way
>
> Am 11.05.20 um 01:52 schrieb Henry Skoglund:
> > Hi, finally took the plunge this weekend and started building Qt myself
> > (MinGW static builds for Windows).
> > Using configure.bat worked fine, it even suggested I should add "-opengl
> > desktop" otherwise "... the build might fail." Helpful stuff.
> > 
> > So I ended up with a fresh new directory "static", next to the
> > C:\Qt\5.14.2\mingw73_32 directory. Question was, how to add the static
> > build as a kit to my Qt Creator? Googling helped, and it was smooth
> > sailing once I realized you go into Options/Kits/Qt Versions and point
> > out where kit's qmake.exe is (e.g. C:\Qt\5.14.2\static\bin\qmake.exe).
> > Enter a few more things and voila, I had a valid bona fide kit and could
> > rebuild my projects into static .exe files.
> > 
> > Got me thinking, adding kits to Qt Creator will be something I have to
> > do quite often (at least once for every new Qt release). Ok it's easy
> > once you know how. But what if there was an easier way? Say at the end
> > of "mingw32-make install" it would create a .kit file (similar to a .pro
> > file) that has all the needed info for Qt Creator to add it
> > automagically, e.g. for my build Qt Creator would use a "static.kit"
> > file for adding (or replacing if there's already a kit named "static").
> > 
> > This of course would mean that Qt Creator has to understand the contents
> > of a .kit file (and for configure to write it correctly). And someone
> > has to specify the contents of such files. But I think it would really
> > be a nice Qt Creator feature, especially for that first time you have a
> > successful Qt build and want to try it ou as a kit.
> > 
> > Rgrds Henry
> 
> Hi Henry,
> 
> to me, this sounds like a good idea. Would you might putting it into a
> suggestion at https://bugreports.qt.io ?
> 
> Thank you for bringing it up!


I'm still waiting for a uniform naming convention. (see attached)

Project Kits:
* Android for armaeabi-v7a (Clang Qt 5.12.7 for Android ARMv7)
* Qt 5.12.7 for iOS

Both lines have issues:
*android - lists android multiple times, lists CPU arch multiple times, 
mentions Qt
*iOS - mentions Qt - of course it's Qt1

It of course gets lets readable when you have multiple Qt versions.

How about :
* 5.12.5 
** Android ARMV7
** Android ARMV8
** iOS
* 5.14.1
** Android Multiarch
** iOS



Just my devalued $.02.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Weird adb failure

[Jason H]

> /home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 pull 
> /system/lib/libc.so

I've seen this command hang, and even reboot the device. It hasn't happened to 
me in a while though, it used to be a daily occurrence.



> Sent: Thursday, May 14, 2020 at 8:57 AM
> From: "Christian Gagneraud" 
> To: "qt-creator" 
> Subject: [Qt-creator] Weird adb failure
>
> Hi there,
>
> I gave a shot at multiarch using Qt-5.14.
> I managed to generate the APK for my app (thanks to Qbs mailing list)
> I've selected arm64 and x86_64.
>
> But then when i hit run i get:
> Initializing deployment to Android device/simulator
> Deploying to 150c980e8288de07
> 00:50:34: Running steps for project Neon Factory Tools...
> 00:50:34: Starting: "/home/chgans/Android/Sdk/platform-tools/adb -s
> 150c980e8288de07 install -r
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/factory-testapp-0.0.apk"
> 00:50:34: The process "/home/chgans/Android/Sdk/platform-tools/adb"
> exited with code 255.
> 00:50:34: Pulling files necessary for debugging.
> 00:50:34: Package deploy: Running command
> "/home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 pull
> /system/bin/app_process
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/app_process".
> 00:50:34: Package deploy: Running command
> "/home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 pull
> /system/bin/app_process32
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/app_process".
> 00:50:34: Package deploy: Running command
> "/home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 pull
> /system/bin/linker
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/linker".
> 00:50:34: Package deploy: Running command
> "/home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07 pull
> /system/lib/libc.so
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/libc.so".
> Error while building/deploying project Neon Factory Tools (kit:
> Android for armeabi-v7a,arm64-v8a,x86,x86_64 (Clang Qt 5.14.2 for
> Android))
> When executing step "Deploy to Android device"
> 00:50:34: Elapsed time: 00:01.
>
> The weird thing is that if i copy/paste the command in a terminal, adb
> doesn't fails, and the APK is loaded:
> /home/chgans/Android/Sdk/platform-tools/adb -s 150c980e8288de07
> install -r 
> /home/chgans/Projects/build-FactoryTools-Android_for_armeabi_v7a_arm64_v8a_x86_x86_64_Clang_Qt_5_14_2_for_Android-Debug/Debug_Android__54f9cea5714846ce/TestApp.93c1d015/factory-testapp-0.0.apk
> Performing Streamed Install
> Success
> chgans@chgans-pc:~/Projects/neon-testapp$ echo $?
> 0
>
> I've tried all the commands, and they all succeed.
> Any idea what could be the problem?
>
> Thanks,
> Chris
> ___
> 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] 3 Compile issues (for projects) (4.12), 1 suggestion.

[Jason H]

Thanks Eike, I will integrate what you shared and give it a shot and further 
update my findings. 

> Sent: Monday, May 11, 2020 at 9:19 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: "qt-creator" 
> Subject: Re: [Qt-creator] 3 Compile issues (for projects) (4.12), 1 
> suggestion.
>
> 
> 
> > On May 7, 2020, at 18:21, Jason H  wrote:
> > 
> > 1. I have noticed for some time now, that QtC is sometimes compiling a file 
> > that is not in the currently selected build configuration -or- it is 
> > related to the next issue
> > 2. The compile output area shows the compile error s for the file that is 
> > currently visible. Well I should add that sometimes I have a split open so 
> > two files are visible.
> 
> The Issues pane shows both “issues from the compilation” and “issues from the 
> code model”.
> Have a look at the filter drop down menu in the output pane’s tool bar for a 
> list of issue categories.
> 
> So, the Issues pane shows code model issues from the currently visible 
> file(s). You can turn that off by unchecking the category in the dropdown.
> 
> > 3. I had an iteration of a file where there was a typo in a #define and 
> > QtC's checker just would just not let that error go after i corrected it.
> > Eventually I closed the file and re-opened it and the above it worked as it 
> > should.
> 
> What sometimes happens to me:
> - I edit a file, do not realize that there is an error.
> - I compile.
> - The issues pane now contains two items for the same issue: One from the 
> compilation error, one from the code model.
> - If I fix the error in code, the code model issue goes away, the compile 
> issue stays until I recompile.
> 
> Maybe something like that happens for you?
> 
> > Is anyone else experiencing this? This falls into one of those areas that 
> > occurs often enough to be frustrating but easy to fix. I don't know if 
> > there's any one else noticing this?
> > 
> > Suggestions:
> > It would be Really Cool if (tm):
> > 1. QtCreator tied our QtCreator preferences to our Qt account and would 
> > install them to new installs - when QtC get re-installed or we get a new 
> > machine. It'd be a nice value-add since logins are now required.
> > 
> > 
> > 
> > ___
> > 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
> Erich-Thilo-Straße 10
> 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

Re: [Qt-creator] 3 Compile issues (for projects) (4.12), 1 suggestion.

[Jason H]

> Sent: Thursday, May 07, 2020 at 7:08 PM
> From: "André Pönitz" 
> To: "Jason H" 
> Cc: "qt-creator" 
> Subject: Re: [Qt-creator] 3 Compile issues (for projects) (4.12), 1 
> suggestion.
>
> On Thu, May 07, 2020 at 06:21:32PM +0200, Jason H wrote:
> > 1. I have noticed for some time now, that QtC is sometimes compiling a file 
> > that
> > is not in the currently selected build configuration
> 
> The build configuration only sets parameters for your build system, Creator
> does not build anything directly, it's all done by the build system used.

I can see why you say that, but that could be the bug?
No ideas who the iOS file is being committed with the Android kit selected

> > -or- it is related to the next issue
> 
> > 2. The compile output area shows the compile error s for the file that is
> > currently visible. Well I should add that sometimes I have a split open so 
> > two
> > files are visible.
> 
> If the build errors do not contain enough information to identify a file
> e.g. because only a non-unique part of the file path is written it might
> be difficult to relate them to the file that caused the issue. Maybe what
> you are seeing is related to that.

My files are uniquely named. In the instant case, one is called 
platformshim_ios.cpp and the other is platform shim_and.cpp. Each is properly 
specd in the iOS {} or Android {} blocks in the pro. By all logic, the iOS file 
should not be compiled when the Android kit is selected.

> > 3. I had an iteration of a file where there was a typo in a #define and 
> > QtC's
> > checker just would just not let that error go after i corrected it.  
> > Eventually
> > I closed the file and re-opened it and the above it worked as it should.
> > 
> > Is anyone else experiencing this?  This falls into one of those areas that 
> > occurs
> > often enough to be frustrating but easy to fix.
> 
> If it's easy to fix we should transfer this discussion to 
> codereview.qt-project

Sorry I meant that the solution of closing and opening the file is easy.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] 3 Compile issues (for projects) (4.12), 1 suggestion.

[Jason H]

1. I have noticed for some time now, that QtC is sometimes compiling a file 
that is not in the currently selected build configuration -or- it is related to 
the next issue
2. The compile output area shows the compile error s for the file that is 
currently visible. Well I should add that sometimes I have a split open so two 
files are visible.
3. I had an iteration of a file where there was a typo in a #define and QtC's 
checker just would just not let that error go after i corrected it.
Eventually I closed the file and re-opened it and the above it worked as it 
should.

Is anyone else experiencing this? This falls into one of those areas that 
occurs often enough to be frustrating but easy to fix. I don't know if there's 
any one else noticing this?

Suggestions:
It would be Really Cool if (tm):
1. QtCreator tied our QtCreator preferences to our Qt account and would install 
them to new installs - when QtC get re-installed or we get a new machine. It'd 
be a nice value-add since logins are now required.



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

Re: [Qt-creator] Bug: 4.12: Android: always use not remembered

[Jason H]

https://bugreports.qt.io/browse/QTCREATORBUG-23918

Seems macOS and windows hosts affected.

> Sent: Thursday, April 23, 2020 at 7:47 PM
> From: "Jason H" 
> To: "qt-creator" 
> Subject: [Qt-creator] Bug: 4.12: Android: always use not remembered
>
> I keep checking the box, but it keeps being presented.
> ___
> 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] Bug: 4.12: Android: always use not remembered

[Jason H]

I keep checking the box, but it keeps being presented.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] [SPAM] 4.12 android desn't remember "always use" device

[Jason H]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Checking the checkbox for "Always use this device for this
   project" does not influence subsequent behavior. 

Content analysis details:   (5.8 points, 4.6 required)

 pts rule name  description
 -- --
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
 0.0 SPF_HELO_NONE  SPF: HELO does not publish an SPF Record
 0.0 FREEMAIL_FROM  Sender email is commonly abused enduser mail
provider (jhihn[at]gmx.com)
 1.0 PDS_TONAME_EQ_TOLOCAL_VSHORT Very short body and From looks like
 2 different emails
 2.0 PDS_TONAME_EQ_TOLOCAL_SHORT Short body with To: name matches
everything in local email
 2.0 SPOOFED_FREEMAIL   No description available.


--- Begin Message ---
Checking the checkbox for "Always use this device for this project" does not 
influence subsequent behavior.


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

[Qt-creator] Android log window doesn't work most of the time

[Jason H]

4.11.2, Catalina,
When building & running my android project only about 15% of the time do I get 
the ADB log content in the application output pane.
When it fails, it still runs, but I get partial output:
```
...
D lib_app.so: void Java_com_company_app_MyActivity_batteryChanged(JNIEnv *, 
jobject, jstring, double) "c" 0.84
D lib_app.so: void Java_com_company_app_MyActivity_batteryChanged(JNIEnv *, 
jobject, jstring, double) "c" 0.84


"com_company_app" died.

04-21 12:31:58.001   738   738 F DEBUG   :


"com_company_app died.
```

Note how the line isn't even complete. Sometimes there are many partial lines 
like that before being cut off. Note that while i killed the first run, the 
second run I did not kill, it report it as having "died" but is in fact still 
running.

However when using the Run button of the application output pane bar, it seems 
to always work.


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

Re: [Qt-creator] Tabs vs Spaces?

[Jason H]

 


I find that it falls short. Not so much a QtCreator issue, but in general if tab indentation is specified, the only place a tab-space combination should be allowed is in explicit strings. To allow tab-space or tab-space-space or tab-space-space-space (with n=4)  should not be allowed. Python almost enforces this with "Unexpected indent", where the entire block has to be consistently indented, so at least the whole block matches. 

 

I also kind0f remember some string you could put at the top of a file to specify to the editor what the settings are. Anyone know what that it called?  I googled but could not find it. Next is if QtC obeys that string?

 



Sent: Monday, March 09, 2020 at 9:44 AM
From: "Brendan Murphy" 
To: "Jason H" , "Bryan Bennetts" 
Cc: qt-creator 
Subject: Re: [Qt-creator] Tabs vs Spaces?


Hi Jason,
 

QtCreator also has an option to insert tabs AS spaces, which is what I tend to use because I like the single key press but want the uniformity of spaces.
 

So one tab press = n spaces
 

Hope that helps.

 

Cheers,

Brendan J. Murphy
 


Get Outlook for Android



From: Qt-creator  on behalf of Bryan Bennetts 
Sent: Friday, March 6, 2020 4:40:29 PM
To: Jason H 
Cc: qt-creator 
Subject: Re: [Qt-creator] Tabs vs Spaces?

 



Hi Jason,
 

You can use git smudge and clean filters so that local versions appear to have spaces, but the remote has tabs. Having said that, I've fiddled with them in the past for formatting they are a little scary IMHO.

 

Best plan is just to choose a format and get everyone to use it, regardless of personal preference. 'this is the project format - suck it up.'

 

As the others have said clang-format is a popular formatter at the moment, and is quite nicely integrated in QTC.

 

There are more than a few pre and post commit hooks out out on the Web to auto clang format to the configuration in the root of the project directory, the only shortfall I've seen in some is that they fail to format the working version at the same time so the dev will see a difference between the working version and the committed version that they might not anticipate. 

 

HTH, B. 

 

 


On Fri, 6 Mar 2020, 16:38 Jason H, <jh...@gmx.com> wrote:

I am a tabs guy. I change the Qt style to use tabs. I tab all the things!!

Anyway, I now have other contributors to my project that are spaces people. How can we live in harmony? One side effect is that it seems git considers whitespace changes so his code is indented with spaces, mine are tabs and it's making a mess in git.


Or should this be handled by git? (And if so, how?)


___
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] Using Qt Enums as QML object keys... Qt6?

[Jason H]

Sorry, all this should have gone to interest - please continue any discussion 
there.

/my bad

> Sent: Friday, March 06, 2020 at 12:23 PM
> From: "Jason H" 
> To: qt-creator 
> Subject: [Qt-creator] Using Qt Enums as QML object keys... Qt6?
>
> First, sometimes I find that not all Qt enums are exported to QML.
> Like the QProcess::ProcessState, IIRC. Are these bugs? Shouldn't all Qt enums 
> in QObject recived classes be Q_ENUM()ed?
>
> Next, QML's uage of these is normally an int, when I print these with 
> console.log() they come out as 0,1,2,3, etc. However, I was going to [ab]use 
> this and tried
> var nameForState = {
> QProcess.NotRunning: "QProcess::NotRunning",
> QProcess.Starting: "QProcess::Starting",
> QProcess.Running: "QProcess::Running",
> }
>
> But instead I have to provide an array:
> var nameForState = [ 
> "QProcess::NotRunning","QProcess::Starting","QProcess::Running"]
> then index.
> console.log("process state", index, nameForState[state]);
> But this is a weaker binding and sometimes the table in the docs is not 
> present, or if is present aren't ways in sorted order. Also QFlags are not 
> possible to do this way.
>
> I am hoping for Qt6, we can console.log() without this additional lookup? Or 
> at least use the object-based lookup and not the array version?
>
>
>
>
>
> ___
> 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] Using Qt Enums as QML object keys... Qt6?

[Jason H]

First, sometimes I find that not all Qt enums are exported to QML.
Like the QProcess::ProcessState, IIRC. Are these bugs? Shouldn't all Qt enums 
in QObject recived classes be Q_ENUM()ed?

Next, QML's uage of these is normally an int, when I print these with 
console.log() they come out as 0,1,2,3, etc. However, I was going to [ab]use 
this and tried
var nameForState = {
QProcess.NotRunning: "QProcess::NotRunning",
QProcess.Starting: "QProcess::Starting",
QProcess.Running: "QProcess::Running",
}

But instead I have to provide an array:
var nameForState = [ 
"QProcess::NotRunning","QProcess::Starting","QProcess::Running"]
then index.
console.log("process state", index, nameForState[state]);
But this is a weaker binding and sometimes the table in the docs is not 
present, or if is present aren't ways in sorted order. Also QFlags are not 
possible to do this way.

I am hoping for Qt6, we can console.log() without this additional lookup? Or at 
least use the object-based lookup and not the array version?





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

[Qt-creator] Tabs vs Spaces?

[Jason H]

I am a tabs guy. I change the Qt style to use tabs. I tab all the things!!

Anyway, I now have other contributors to my project that are spaces people. How 
can we live in harmony? One side effect is that it seems git considers 
whitespace changes so his code is indented with spaces, mine are tabs and it's 
making a mess in git.


Or should this be handled by git? (And if so, how?)


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

Re: [Qt-creator] Minor autocompletion suggestion annoyances

[Jason H]

Voted and following.

What really grinds my gears is QtC is the only editor with the is behavior, and 
I use a few editors, so I'm always having to remember QtC's very unique quoting 
rule.
(Yes you can turn it off but it turns it off always)

> Sent: Thursday, March 05, 2020 at 9:57 AM
> From: "André Hartmann" 
> To: "Jason H" , qt-creator 
> Subject: Re: [Qt-creator] Minor autocompletion suggestion annoyances
>
> Hi Jason,
> 
> >   void f(QObject *parent=null...)
> > 
> > Where ... is "ptr" for what I want.
> > But ... is suggested as "ptr_t".
> > But "ptr" is the second one in the list.  This is so close, but I'm curious 
> > as to why the longer is coming becoming before the shorter?
> > nullptr should be first by alphabetical and word frequency order.
> 
> Hit me too. It is tracked as
> https://bugreports.qt.io/browse/QTCREATORBUG-6242
> 
> > 
> > Also, still painfully dealing with QtC's default " behavior, which is to 
> > almost always insert 2.
> > I'm still suggesting to limit "-> "" to where the right of " is at EoL or 
> > white space. That would save so many corrections.
> > I realize I can turn it off, but I'd like to keep it exept when tot he 
> > right of the cursor is non-whitespace.
> 
> I'd also agree to this. I'm not sure if there is already a bugreport, 
> but that might be the case.
> 
> Regards, André
> 
> > 
> > Example:
> > convert this {x: 1} to JSON (ignoring selecting x then ", which is takign 
> > the hand off the keyboard for the mouse or more keystokes)
> > Step 1: insert ", get:
> > {""x:1}
> > Backapace to get rid of the extra ", arrive at:
> > {x: 1}
> > Hrmph. Insert " again
> > {""x:1}
> > Now arrow right once and backspace.
> > {"x:1}
> > Then arrow over once more and add ", and you'll be at the desired outcome. 
> > Interestingly, there wasn't a double " inserted this time.
> > 
> > Worse yet, forget that QtC is doing this and work right to left, and find 
> > yourself at:
> > {""x"":1}
> > Which is just a nightmare. But per my rules above,  {x :1} ->  {""x"" :1} 
> > So modify that to be only insert "" if there is white space on both sides.
> > 
> > 
> > I spend so much time fighting this, but it is also so close to working 
> > perfectly ('perfectlty' as defined by me)
> > 
> > 
> > 
> > Many thanks
> > ___
> > 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] Minor autocompletion suggestion annoyances

[Jason H]

 void f(QObject *parent=null...)

Where ... is "ptr" for what I want.
But ... is suggested as "ptr_t".
But "ptr" is the second one in the list.  This is so close, but I'm curious as 
to why the longer is coming becoming before the shorter?
nullptr should be first by alphabetical and word frequency order.

Also, still painfully dealing with QtC's default " behavior, which is to almost 
always insert 2.
I'm still suggesting to limit "-> "" to where the right of " is at EoL or white 
space. That would save so many corrections.
I realize I can turn it off, but I'd like to keep it exept when tot he right of 
the cursor is non-whitespace.

Example:
convert this {x: 1} to JSON (ignoring selecting x then ", which is takign the 
hand off the keyboard for the mouse or more keystokes)
Step 1: insert ", get:
{""x:1}
Backapace to get rid of the extra ", arrive at:
{x: 1}
Hrmph. Insert " again
{""x:1}
Now arrow right once and backspace.
{"x:1}
Then arrow over once more and add ", and you'll be at the desired outcome. 
Interestingly, there wasn't a double " inserted this time.

Worse yet, forget that QtC is doing this and work right to left, and find 
yourself at:
{""x"":1}
Which is just a nightmare. But per my rules above,  {x :1} ->  {""x"" :1} So 
modify that to be only insert "" if there is white space on both sides.


I spend so much time fighting this, but it is also so close to working 
perfectly ('perfectlty' as defined by me)



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

[Qt-creator] Integrated help mostly broken?

[Jason H]

Qt 5.14.1
Creator 4.11.1

Can someone confirm:
In Text QML Type documentation
Click on the "lineHeight" propery inthe proerty list.
Does it take you to the property documention or the top of the page?

I'm encountering a lot of things that do this al through out the help.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Lambda completion with ;

[Jason H]

Would it be possible to get QtC to provide the ; automatically for a lambda?
[=](){
|
}); // <- this ;

So that when hitting enter after the {
that the }); if provided and the cursor ends up placed above it and indented 
(where the | is)?

Currently, it will place the }) properly on enter, but doesn't automatically 
place the ;

It's a small detail but it would be greatly appreciated.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] iPhone XS, can't debug

[Jason H]

A while ago, this broke when Apple changed the format of their device IDS.

$ idevice_id -l
8020-0013252C0228002F

This now loops forever:

tryRemoteConnect
TransferAppSession(80200013252C0228002F, 
/Users/me/Projects/build-mobile_app-Qt_5_12_7_for_iOS-Debug/Debug-iphoneos/app.app)connectByPort
 on device 80200013252C0228002F port 30001 failed, AMDeviceStartService 
returned 61
tryRemoteConnect *failed* on remote port 30001

However works fine on iPhone 8+:
$ idevice_id -l
52df606c45119d77676ee6be5dbcdc01bb807a4f

tryRemoteConnect
TransferAppSession(52df606c45119d77676ee6be5dbcdc01bb807a4f, 
/Users/me/Projects/build-mobile_app-Qt_5_12_7_for_iOS-Debug/Debug-iphoneos/app.app)connectByPort
 on device 52df606c45119d77676ee6be5dbcdc01bb807a4f port 30001 failed, 
AMDeviceStartService returned 61
tryRemoteConnect *failed* on remote port 30001
handleNewRelayConnection
setting up relayer for new connection
tryRemoteConnect
tryRemoteConnect *succeeded* on remote port 30001

Seems the hyphen is breaking things?

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

Re: [Qt-creator] Another 4.11 issue

[Jason H]

Marge, it happened again!
Started a new project this time, and the HEADERS and SOURCES changes ended up 
in the first project.

> Sent: Thursday, February 20, 2020 at 10:10 AM
> From: "Christian Kandeler" 
> To: "qt-creator@qt-project.org" 
> Subject: Re: [Qt-creator] Another 4.11 issue
>
> On Thu, 20 Feb 2020 15:44:23 +0100
> "Jason H"  wrote:
>
> > I think we all know I've been using QtC for years. So I think I know what 
> > I'm doing. But maybe I'm going insane? I have been under a lot of pressure 
> > lately.
> >
> > Anyway, I add a C++ class to my project by right Clicking in Projects pane, 
> > "Add new..." C++/C++ Class, but it doesn't end up there. It ends up in the 
> > first (wrong) project! It specifically references ../right_project/class.h 
> > and ../right_project/class.cpp
>
> If you have a project where this is reproducible, please attach it at
> https://bugreports.qt.io/browse/QTCREATORBUG-23603.
>
>
> Christian
> ___
> 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] Another 4.11 issue

[Jason H]

Clarification: The files, and their location are correct, just the wrong .pro 
was modified to include them

Also: I like the new gray filenames if not part of the selected platform. Nice 
touch!


> Sent: Thursday, February 20, 2020 at 8:44 AM
> From: "Jason H" 
> To: qt-creator 
> Subject: [Qt-creator] Another 4.11 issue
>
> I think we all know I've been using QtC for years. So I think I know what I'm 
> doing. But maybe I'm going insane? I have been under a lot of pressure lately.
>
> Anyway, I add a C++ class to my project by right Clicking in Projects pane, 
> "Add new..." C++/C++ Class, but it doesn't end up there. It ends up in the 
> first (wrong) project! It specifically references ../right_project/class.h 
> and ../right_project/class.cpp
>
> I would think the only way to achieve this would be to change the path in 
> tthe C++ class wizard? (Which I did not do). Happened a few times yesterday. 
> I don't usually add classes, so cant't judge frequency. But I don't ever 
> remember any version of QtC doing this before.
>
> ___
> 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] Another 4.11 issue

[Jason H]

I think we all know I've been using QtC for years. So I think I know what I'm 
doing. But maybe I'm going insane? I have been under a lot of pressure lately.

Anyway, I add a C++ class to my project by right Clicking in Projects pane, 
"Add new..." C++/C++ Class, but it doesn't end up there. It ends up in the 
first (wrong) project! It specifically references ../right_project/class.h and 
../right_project/class.cpp

I would think the only way to achieve this would be to change the path in tthe 
C++ class wizard? (Which I did not do). Happened a few times yesterday. I don't 
usually add classes, so cant't judge frequency. But I don't ever remember any 
version of QtC doing this before.

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

Re: [Qt-creator] OSX Menu alignment

[Jason H]

I did attempt that, but reading it was not showing me much (I blame myself with 
failure to interpret, really) will attempt screenshots next time.

> Sent: Friday, February 14, 2020 at 9:39 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: "fro...@tungware.se" , "qt-creator@qt-project.org" 
> 
> Subject: Re: [Qt-creator] OSX Menu alignment
>
> 
> 
> > On 14. Feb 2020, at 16:23, Jason H  wrote:
> > 
> > So upgrading to 4.11.1 fixed it.
> > But now I have a new problem. Sometimes when building it freezes and then 
> > starts taking up 100% CPU.
> 
> What does activity monitor say, is it the Qt Creator process? Or something 
> started by Qt Creator?
> If it is the Qt Creator process, does “Sample Process” in activity monitor 
> give any insights?
> 
> > If I abort it, then I can never compile again, it always freezes. 
> > 4.10 did not exhibit this behavior.
> > 
> > 
> >> Sent: Thursday, February 13, 2020 at 4:25 AM
> >> From: "Henry Skoglund" 
> >> To: qt-creator@qt-project.org
> >> Subject: Re: [Qt-creator] OSX Menu alignment
> >> 
> >> Same here, OSX 10.15.3, 2 Screens, QtC 4.11.1 on the right, popups 
> >> always aligned properly.
> >> 
> >> However, sometimes, usually in the morning after I've started my Mac, 
> >> right-clicking on my project name in the top left area (I have the 
> >> Projects view active) causes Qt Creator 4.11.1 to crash (I've attached 
> >> the log in the end). This can happen 1 or 2 times, then I'm fine all 
> >> day. Haven't bothered to report this, since I have to reboot etc. to 
> >> reproduce the crash.
> >> 
> >> On 2020-02-13 10:09, ekke wrote:
> >>> doesn't happen for me
> >>> OSX 10.14.6
> >>> 2 Screens
> >>> QtC on right screen
> >>> 
> >>> Am 13.02.20 um 08:40 schrieb Eike Ziller:
> >>>> Should not happen, and does not happen for me, so more details are 
> >>>> needed.
> >>>> 
> >>>> (i.e. bug report with information about Qt Creator version, macOS 
> >>>> version, dump from Help > System Information, check if it also 
> >>>> happens with standard Qt examples like “Application Example" etc).
> >>>> 
> >>>> Br, Eike
> >>>> 
> >>>>> On 12. Feb 2020, at 21:17, Jason H  wrote:
> >>>>> 
> >>>>> Additionally, if I move the window and right click on the first 
> >>>>> project to close it, it is really offset to the right. (Attached)
> >>>>> 
> >>>>>> Sent: Wednesday, February 12, 2020 at 3:14 PM
> >>>>>> From: "Jason H" 
> >>>>>> To: qt-creator 
> >>>>>> Subject: [Qt-creator] OSX Menu alignment
> >>>>>> 
> >>>>>> I know OSX handling of desktops is bread dead. But... It would be 
> >>>>>> great if QtC could not position popups off the screen. This is a 
> >>>>>> capture of the left edge of my right screen, where QtC resides.
> >>>>>> 
> >>>>>> 
> >> Crash 
> >> log---
> >> Process:   Qt Creator [35609]
> >> Path:  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt 
> >> Creator
> >> Identifier:org.qt-project.qtcreator
> >> Version:   4.11.1 (4.11.1)
> >> Code Type: X86-64 (Native)
> >> Parent Process:??? [1]
> >> Responsible:   Qt Creator [35609]
> >> User ID:   501
> >> 
> >> Date/Time: 2020-02-13 10:13:30.817 +0100
> >> OS Version:Mac OS X 10.15.3 (19D76)
> >> Report Version:12
> >> Anonymous UUID:81A9BC8C-3367-B330-126B-29DE38632838
> >> 
> >> 
> >> Time Awake Since Boot: 4300 seconds
> >> 
> >> System Integrity Protection: enabled
> >> 
> >> Crashed Thread:0  Dispatch queue: com.apple.main-thread
> >> 
> >> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
> >> Exception Codes:   KERN_INVALID_ADDRESS at 0x0028
> >> Exception Note:EXC_CORPSE_NOTIFY
> >> 
> >> Termination Signal:Segmentation fault: 11
> >> T

[Qt-creator] Odd Crash, tool tip related

[Jason H]

I don't know why it crashed, but I had just saved (Ctrl-S) and closed (clicked 
the X) a UI file that was in text mode.

Process:   Qt Creator [51485]
Path:  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator
Identifier:org.qt-project.qtcreator
Version:   4.11.1 (4.11.1)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   Qt Creator [51485]
User ID:   501

Date/Time: 2020-02-17 10:48:02.264 -0600
OS Version:Mac OS X 10.14.6 (18G103)
Report Version:12
Bridge OS Version: 4.1 (17P1081)
Anonymous UUID:334B0A41-53C6-7D51-BD65-64A23C95424F

Sleep/Wake UUID:   2DBE10A4-23FD-455F-841E-1CAE7FC3CBED

Time Awake Since Boot: 37 seconds
Time Since Wake:   1400 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x1800
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [51485]

VM Regions Near 0x1800:
-->
__TEXT 00010ac4a000-00010ac5e000 [   80K] r-x/rwx 
SM=COW  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtWidgets0x00010b021992 
QTipLabel::placeTip(QPoint const&, QWidget*) + 418 (qtooltip.cpp:409)
1   org.qt-project.QtWidgets0x00010b021d02 
QToolTip::showText(QPoint const&, QString const&, QWidget*, QRect const&, int) 
+ 242 (qtooltip.cpp:515)
2   org.qt-project.QtWidgets0x00010aff471d 
QWidget::event(QEvent*) + 2269 (qwidget.cpp:9006)
3   org.qt-project.QtWidgets0x00010b19cf5f 
QToolButton::event(QEvent*) + 319 (qtoolbutton.cpp:1002)
4   org.qt-project.QtWidgets0x00010afb95ba 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266 
(qapplication.cpp:3686)
5   org.qt-project.QtWidgets0x00010afbae73 
QApplication::notify(QObject*, QEvent*) + 1667 (qapplication.cpp:3351)
6   org.qt-project.QtCore   0x00010bec6ae4 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 
(qcoreapplication.cpp:1092)
7   org.qt-project.QtWidgets0x00010afb7bc7 
QApplication::event(QEvent*) + 1607 (qapplication.cpp:1904)
8   org.qt-project.QtWidgets0x00010afb95ba 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266 
(qapplication.cpp:3686)
9   org.qt-project.QtWidgets0x00010afbaa46 
QApplication::notify(QObject*, QEvent*) + 598
10  org.qt-project.QtCore   0x00010bec6ae4 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 
(qcoreapplication.cpp:1092)
11  org.qt-project.QtCore   0x00010bf2195f 
QTimerInfoList::activateTimers() + 991 (qtimerinfo_unix.cpp:645)
12  libqcocoa.dylib 0x00010e249892 
QCocoaEventDispatcherPrivate::activateTimersSourceCallback(void*) + 18 
(qcocoaeventdispatcher.mm:123)
13  com.apple.CoreFoundation0x7fff48b19de3 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14  com.apple.CoreFoundation0x7fff48b19d89 __CFRunLoopDoSource0 
+ 108
15  com.apple.CoreFoundation0x7fff48afd74b 
__CFRunLoopDoSources0 + 195
16  com.apple.CoreFoundation0x7fff48afcd15 __CFRunLoopRun + 1189
17  com.apple.CoreFoundation0x7fff48afc61e CFRunLoopRunSpecific 
+ 455
18  com.apple.HIToolbox 0x7fff47d5b1ab 
RunCurrentEventLoopInMode + 292
19  com.apple.HIToolbox 0x7fff47d5aee5 
ReceiveNextEventCommon + 603
20  com.apple.HIToolbox 0x7fff47d5ac76 
_BlockUntilNextEventMatchingListInModeWithFilter + 64
21  com.apple.AppKit0x7fff460f377d _DPSNextEvent + 1135
22  com.apple.AppKit0x7fff460f246b 
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 
+ 1361
23  com.apple.AppKit0x7fff460ec588 -[NSApplication run] 
+ 699
24  libqcocoa.dylib 0x00010e24a623 
QCocoaEventDispatcher::processEvents(QFlags) + 
2579 (qcocoaeventdispatcher.mm:430)
25  org.qt-project.QtCore   0x00010bec2b6f 
QEventLoop::exec(QFlags) + 431 (atomic:929)
26  org.qt-project.QtCore   0x00010bec70f2 
QCoreApplication::exec() + 130 (qcoreapplication.cpp:1400)
27  org.qt-project.qtcreator0x00010ac56016 main + 15318
28  libdyld.dylib   0x7fff74a783d5 start + 1

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

[Qt-creator] OSX Menu alignment

[Jason H]

I know OSX handling of desktops is bread dead. But... It would be great if QtC 
could not position popups off the screen. This is a capture of the left edge of 
my right screen, where QtC resides.


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

Re: [Qt-creator] Project hierarchy

[Jason H]

Ctrl-K seems nice.

I've been experimening with the views and I kinda like the class view, but the 
problem is QML does not appear in it. So it seems file approach is the only way 
with QtQuick projects...? Maybe the QML items should appear int he Class View 
as well?

I still really like the idea of grouping bu filename and proving buttons of the 
extension. Seems like it would bring everything into view (pun unintentional)

> Sent: Monday, February 10, 2020 at 3:50 PM
> From: "Filippo Cucchetto" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] Project hierarchy
>
> Not an answer but i simply use CTRL+K and input a prefix of the
> filename. I rarely use the file browser at all
>
> Il giorno lun 10 feb 2020 alle ore 18:57 Jason H  ha scritto:
> >
> > I'm wondering if it is possible to change the grouping the in the project 
> > explorer. My project has added many files and scrolling between Headers and 
> > Sources is getting tiresome.
> >
> > There is filesystem view, but I thought it would be cool to have a view 
> > that has lines which group common parts of a filename followed by the 
> > extension: filename: [.h] [.cpp]
> > The class view isn't good either because it takes you to a declaration. How 
> > can I jump to an implementation without having to go through the .h file?
> > The class view could also offer direct jumping to the the declaration or 
> > the implementation.
> >
> > Just some thoughts...
> >
> >
> >
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > https://lists.qt-project.org/listinfo/qt-creator
>
>
>
> --
> Filippo Cucchetto
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Project hierarchy

[Jason H]

I'm wondering if it is possible to change the grouping the in the project 
explorer. My project has added many files and scrolling between Headers and 
Sources is getting tiresome.

There is filesystem view, but I thought it would be cool to have a view that 
has lines which group common parts of a filename followed by the extension: 
filename: [.h] [.cpp]
The class view isn't good either because it takes you to a declaration. How can 
I jump to an implementation without having to go through the .h file?
The class view could also offer direct jumping to the the declaration or the 
implementation.

Just some thoughts...



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

[Qt-creator] [SPAM] Add a linter warning

[Jason H]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  I'm not sure what it takes, but it would be a good idea I
  think to have a warning in QML (or anywhere really) when you declare a var
   that is already a property. I just spent entirely too long debugging a 
problem
   because I named it "data" which is already a thing, and a very important
  one at that! [...] 

Content analysis details:   (4.8 points, 4.6 required)

 pts rule name  description
 -- --
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
 0.0 SPF_HELO_NONE  SPF: HELO does not publish an SPF Record
 0.0 FREEMAIL_FROM  Sender email is commonly abused enduser mail 
provider
(jhihn[at]gmx.com)
 2.0 PDS_TONAME_EQ_TOLOCAL_SHORT Short body with To: name matches
everything in local email
 2.0 SPOOFED_FREEMAIL   No description available.


--- Begin Message ---
I'm not sure what it takes, but it would be a good idea I think to have a 
warning in QML (or anywhere really) when you declare a var that is already a 
property. I just spent entirely too long debugging a problem because I named it 
"data" which is already a thing, and a very important one at that!
--- End Message ---
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Fw: [Development] Changes to Qt offering

[Jason H]

Mr Jackson,
Please see below and vent accordingly.


> Sent: Monday, January 27, 2020 at 9:34 AM
> From: "Lars Knoll" 
> To: "Qt development mailing list" 
> Subject: [Development] Changes to Qt offering
>
> Hi all,
> 
> The Qt Company has done some adjustments to the Qt will be offered in the 
> future. Please check out https://www.qt.io/blog/qt-offering-changes-2020 . 
> 
> The change consists of three parts. 
> 
> One is a change in policy regarding the LTS releases, where the LTS part of a 
> release is in the future going to be restricted to commercial customers. All 
> bug fixes will (as agreed on the Qt Contributor Summit) go into dev first. 
> Backporting bug fixes is something that the Qt Company will take care of for 
> these LTS branches. We’ve seen over the past that LTS support is something 
> mainly required by large companies, and should hopefully help us get some 
> more commercial support for developing Qt further.
> 
> The second change is that a Qt Account will be in the future required for 
> binary packages. Source code will continue to be available as currently. This 
> will simplify distribution and integration with the Marketplace. In addition, 
> we want open source users to contribute to Qt or the Qt ecosystem. Doing so 
> is only possible with a valid Qt Account (Jira, code review and the forums 
> all require a Qt Account).
> 
> The third change is that The Qt Company will in the future also offer a lower 
> priced product for small businesses. That small business product is btw not 
> limited to mobile like the one Digia had some years ago, but covers all of Qt 
> for Device Creation.
> 
> None of these changes should affect how Qt is being developed. There won’t be 
> any changes to Open Governance or the open development model.
> 
> Best regards,
> Lars
> 
> ___
> Development mailing list
> developm...@qt-project.org
> https://lists.qt-project.org/listinfo/development
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Code model could not parse, but compiled, iOS Framework

[Jason H]

> An include of  will look in all framework paths for 
> “A.framework/Headers/B.h”.

Excellent.
 
> - Check in Tools > C++ > Inspect C++ Code Model > Project Parts > Header 
> Paths, that you have the path with openvc2.framework in it as a FrameworkPath 
> listed.

It is not listed.

> - Does the editor complain about the include? Or is the include actually 
> found, but other problems occur which lead to the symbols not being available?

Yes.

> - Do you have any code model warnings that do not show up inline in the 
> editor? Look for a warning sign in the editor’s toolbar.
Yes.

I wonder how exactly I need to specify it.  
https://doc.qt.io/qt-5/qmake-platform-notes.html#using-frameworks says:
LIBS += -F/path/to/framework/directory/ 
but is that the opencv2.framework directory, or the ios directory (see below)

I've tried variations of:
LIBS += -F$$PWD/ios -framework opencv2

Where project is :
project/
project/project.pro
project/main.cpp
project/ios/Info.plist
project/ios/opencv2.framework/
project/ios/opencv2.framework/Headers/...
project/ios/opencv2.framework/Versions/...
project/ios/opencv2.framework/...

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

[Qt-creator] Code model could not parse, but compiled, iOS Framework

[Jason H]

I'm trying to add OpenCV to a mobile app. Works fine on android, but on iOS Qt 
Creator is tell ing me it can't parse the included file.

In the ios setion of the .pro:
LIBS += -F$$PWD/ios -framework opencv2
INCLUDEPATH+=$$PWD/ios/opencv2.framework/Headers  ((should I even need 
this?))

The app is able to compile though. I copied opencv2.framework from the build 
location.

I get the red errors in the code edit window of  "use of undeclared identifer 
'cv'..."

What do I need to do to make QtC/code model happy? (4.10.2) It seems that the 
framework directory structure ($$PWD/ios/opencv2.framework/Headers/*.hpp) 
breaks the #includes of opencv2/*.hpp

I tried to add a symlink:
ln -s $$PWD/ios/opencv2.framework/Headers  $$PWD/ios/opencv2
and changed: INCLUDEPATH+=$$PWD/ios

And that worked, but I don't think I should have to provide a symlink?

How should this work?






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

Re: [Qt-creator] Qt Creator 4.11 frequently becomes non-responsive

[Jason H]

I don't know Dmitry's problem, but I can say with certainty that the link you mentioned is not it. The bug you linked to is a problem with Xcode and it's provided python implementation. Creator also remains somewhat responsive while your core is maxed out.

 




Sent: Saturday, December 21, 2019 at 7:29 PM
From: "Dmitry Volosnykh" 
To: "Eike Ziller" 
Cc: qt-creator 
Subject: Re: [Qt-creator] Qt Creator 4.11 frequently becomes non-responsive



Hi Adam, there's somewhat similar issue filed in Jira: https://bugreports.qt.io/browse/QTCREATORBUG-23336

Initially, it is focused on macOS, but maybe you will find your experiences the same, then the status of this issue might be changed to a wider scope.

 


On Fri, Dec 20, 2019 at 5:38 PM Eike Ziller  wrote:



> On 20. Dec 2019, at 14:38, Adam Light  wrote:
>
> Hi
>
> I'm using Qt Creator 4.11.0 on Windows 10. This is the official 64-bit build.
>
> I'm frequently encountering Creator become non-responsive for many seconds, even into minutes. The OS adds "Not Responding" to the title bar and the mouse cursor turns into the spinning blue ring.
>
> I have disabled the ClangCodeModel plugin (and restarted) because in our experience that plugin tends to impact performance. But things are still very sluggish. Even if Qt is responding, it can take a minute for syntax highlighting of a small file to appear, sometimes opening a small file takes a very long time, etc.
>
> I collected some traces of a recent non-responsive event with xperf and it looks like something deep within CPlusPlus4.dll is taking all of the time, but I don't have .pdb files for Creator to analyze further.
>
> Is it possible to get PDB files for the official Creator builds?

http://download.qt-project.org/official_releases/qtcreator/4.11/4.11.0/installer_source/windows_msvc2017_x64/qtcreator-debug.7z

> Does the Qt company have a symbols server?
>
> A colleague has complained to me of similar problems with the same project on Windows but he's using Creator 4.10.2. So I'm not sure if this is something new to 4.11 or if I'm just seeing it for the first time on this machine.
>
> Thanks for any suggestions about what might be going wrong or how to get symbols.
>
> Adam
> ___
> 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
Erich-Thilo-Straße 10
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



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

[Qt-creator] [SPAM] Debugging mode steals keyboard focus

[Jason H]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  On OSX, when I try to debug an Android app, (hit the debug
   button) then switch to another app and start typing (the 
compile
   steps take some time) that the QtCreator text editor steals the focus. Has
   anyone else observed this? Anyone on other platforms (win, lin)? [...] 

Content analysis details:   (4.8 points, 4.6 required)

 pts rule name  description
 -- --
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.4984]
 0.0 FREEMAIL_FROM  Sender email is commonly abused enduser mail 
provider
(jhihn[at]gmx.com)
 0.0 SPF_HELO_NONE  SPF: HELO does not publish an SPF Record
 2.0 PDS_TONAME_EQ_TOLOCAL_SHORT Short body with To: name matches
everything in local email
 2.0 SPOOFED_FREEMAIL   No description available.


--- Begin Message ---
On OSX, when I try to debug an Android app, (hit the debug button) then switch 
to another app and start typing (the compile steps take some 
time) that the QtCreator text editor steals the focus. Has anyone else observed 
this? Anyone on other platforms (win, lin)?




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

Re: [Qt-creator] Fwd: [Development] Qt 5.14.0 and Qt Creator 4.11.0 released

[Jason H]

That's a pretty hideous mouse pointer!!

> Sent: Friday, December 13, 2019 at 12:36 AM
> From: "Oleg Shalnev" 
> To: qt-creator@qt-project.org
> Subject: [Qt-creator] Fwd: [Development] Qt 5.14.0 and Qt Creator 4.11.0 
> released
>
> -- Forwarded message -
> От: Oleg Shalnev 
> Date: пт, 13 дек. 2019 г. в 02:24
> Subject: Re: [Development] Qt 5.14.0 and Qt Creator 4.11.0 released
> To: developm...@qt-project.org 
> 
> 
> Ladies and gentlemen! I have no idea what's going on with QtCreator 4.11.
> 
> 1) Where is custom clang-tidy check rules.
> [image: image.png]
> 2) clang code model works completely wrong. Don't find simple things.
> [image: image.png]
> 
> 3) After turning clang code mode off code highlights wrong too
> [image: image.png]
> 
> 4) no way to set clang+ccache kit. QtCreator forget settings back to gcc
> after reload.
> 
>  I was only working on the last version 20 minutes ago. Now I can't even
> downgrade to 4.10.
> What is going on with the most amazing tool in c++ world?
> 
> чт, 12 дек. 2019 г. в 14:45, Jani Heikkinen :
> 
> > Hi everyone,
> >
> > We have released Qt 5.14.0 and Qt Creator 4.11.0 today, see
> > https://www.qt.io/blog/qt-5.14-has-released and
> > https://www.qt.io/blog/qt-creator-4.11.0-is-released.
> >
> > Thanks to everyone involved!
> >
> > br,
> > Jani Heikkinen
> > Release Manager
> >
> >
> > ___
> > Development mailing list
> > developm...@qt-project.org
> > https://lists.qt-project.org/listinfo/development
> >
> 
> 
> -- 
> Oleg Shal  (AriSha Integration Initiative)
> --
> e-mail  : oleg@ arisha.online ,
> oleg.shal...@gmail.com
> cell,Viber,WhatsUp,Telegram : +7 (918) 741 7217
> 
> 
> 
> -- 
> Oleg Shal  (AriSha Integration Initiative)
> --
> e-mail  : oleg@ arisha.online ,
> oleg.shal...@gmail.com
> cell,Viber,WhatsUp,Telegram : +7 (918) 741 7217
> ___
> 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] LLDB CPU usage 100% on macOS Catalina (10.15)

[Jason H]

Interestingly clang for android does not have the same problem.

> Sent: Friday, December 06, 2019 at 2:35 PM
> From: "Michael Jackson" 
> To: "Jason H" 
> Cc: Qt-creator 
> Subject: Re: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
>
> Initially looks like an issue with the Xcode 11.2 version. Our OS versions 
> are different but Xcode is the same.
> 
> --
> Mike Jackson 
> 
> On 12/6/19, 1:49 PM, "Jason H"  wrote:
> 
> Mine is only 15" running 10.14.6
> XCode Version 11.2 (11B52)
> Though this was also the same on my 2016 13 model as well.
> 
> I should note that I mainly debug mobile apps. iOS and Android, but I'm 
> currently debugging an OSX app communicating with a mobile app and it is lldb 
> is pegged on 1 CPU. (screenshot added to bug)
>  
> 
> 
> 
> > Sent: Friday, December 06, 2019 at 12:13 PM
> > From: "Michael Jackson" 
> > To: "Jason H" 
> > Cc: Qt-creator 
> > Subject: Re: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
> >
> > I have a 2013 MacBook Pro (mid 2013) that I did *not* have this problem 
> at all. 
> > 
> > What version of Xcode are you running?
> > What model of Mac do you have? 
> > 
> > For me it is a 2019 16" MacBook Pro with Xcode 11.2.1
> > 
> > --
> > Michael Jackson | Owner, President
> >   BlueQuartz Software
> > [e] mike.jack...@bluequartz.net
> > [w] www.bluequartz.net <http://www.bluequartz.net>
> > 
> > On 12/6/19, 10:35 AM, "Jason H"  wrote:
> > 
> > I'm on Mojave and that is my experience as well. You can't debug on 
> battery for very long.
> > 
> > 
> > > Sent: Friday, December 06, 2019 at 9:51 AM
> > > From: "Michael Jackson" 
> > > To: Qt-creator 
> > > Subject: [Qt-creator] LLDB CPU usage 100% on macOS Catalina 
> (10.15)
> > >
> > > I recently got a new MacBookPro and so was forced to use macOS 
> Catalina. I just finally go around to debugging some code through QtCreator 
> (4.10.1) and while I was debugging the fans were screaming so I popped open 
> activity monitor and noticed that LLDB is spinning full a single CPU core. 
> This is while I am sitting at a breakpoint so the application is doing 
> nothing. 
> > > 
> > > Has anyone else seen this? Is this normal under Catalina (10.15)? 
> I can’t imagine the hit to my battery life if I needed to debug while out of 
> the office.
> > > 
> > > Thanks
> > > --
> > > Michael Jackson | Owner, President
> > >   BlueQuartz Software
> > > [e] mike.jack...@bluequartz.net
> > > [w] www.bluequartz.net <http://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] LLDB CPU usage 100% on macOS Catalina (10.15)

[Jason H]

Mine is only 15" running 10.14.6
XCode Version 11.2 (11B52)
Though this was also the same on my 2016 13 model as well.

I should note that I mainly debug mobile apps. iOS and Android, but I'm 
currently debugging an OSX app communicating with a mobile app and it is lldb 
is pegged on 1 CPU. (screenshot added to bug)
 



> Sent: Friday, December 06, 2019 at 12:13 PM
> From: "Michael Jackson" 
> To: "Jason H" 
> Cc: Qt-creator 
> Subject: Re: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
>
> I have a 2013 MacBook Pro (mid 2013) that I did *not* have this problem at 
> all. 
> 
> What version of Xcode are you running?
> What model of Mac do you have? 
> 
> For me it is a 2019 16" MacBook Pro with Xcode 11.2.1
> 
> --
> Michael Jackson | Owner, President
>   BlueQuartz Software
> [e] mike.jack...@bluequartz.net
> [w] www.bluequartz.net <http://www.bluequartz.net>
> 
> On 12/6/19, 10:35 AM, "Jason H"  wrote:
> 
> I'm on Mojave and that is my experience as well. You can't debug on 
> battery for very long.
> 
> 
> > Sent: Friday, December 06, 2019 at 9:51 AM
> > From: "Michael Jackson" 
> > To: Qt-creator 
> > Subject: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
> >
> > I recently got a new MacBookPro and so was forced to use macOS 
> Catalina. I just finally go around to debugging some code through QtCreator 
> (4.10.1) and while I was debugging the fans were screaming so I popped open 
> activity monitor and noticed that LLDB is spinning full a single CPU core. 
> This is while I am sitting at a breakpoint so the application is doing 
> nothing. 
> > 
> > Has anyone else seen this? Is this normal under Catalina (10.15)? I 
> can’t imagine the hit to my battery life if I needed to debug while out of 
> the office.
> > 
> > Thanks
> > --
> > Michael Jackson | Owner, President
> >   BlueQuartz Software
> > [e] mike.jack...@bluequartz.net
> > [w] www.bluequartz.net <http://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] LLDB CPU usage 100% on macOS Catalina (10.15)

[Jason H]

Feel free to add your experience to: https://bugreports.qt.io/browse/QTCREATORBUG-23336

 

 
 

Sent: Friday, December 06, 2019 at 10:44 AM
From: "Denis Rouzaud" 
To: "Jason H" 
Cc: "Michael Jackson" , qt-creator@qt-project.org
Subject: Re: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)


I experience the same!
 


Le ven. 6 déc. 2019 à 16:36, Jason H <jh...@gmx.com> a écrit :

I'm on Mojave and that is my experience as well. You can't debug on battery for very long.


> Sent: Friday, December 06, 2019 at 9:51 AM
> From: "Michael Jackson" <mike.jack...@bluequartz.net>
> To: Qt-creator <qt-creator@qt-project.org>
> Subject: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
>
> I recently got a new MacBookPro and so was forced to use macOS Catalina. I just finally go around to debugging some code through QtCreator (4.10.1) and while I was debugging the fans were screaming so I popped open activity monitor and noticed that LLDB is spinning full a single CPU core. This is while I am sitting at a breakpoint so the application is doing nothing.
>
> Has anyone else seen this? Is this normal under Catalina (10.15)? I can’t imagine the hit to my battery life if I needed to debug while out of the office.
>
> Thanks
> --
> Michael Jackson | Owner, President
>       BlueQuartz Software
> [e] mike.jack...@bluequartz.net
> [w] www.bluequartz.net <http://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] LLDB CPU usage 100% on macOS Catalina (10.15)

[Jason H]

I'm on Mojave and that is my experience as well. You can't debug on battery for 
very long.


> Sent: Friday, December 06, 2019 at 9:51 AM
> From: "Michael Jackson" 
> To: Qt-creator 
> Subject: [Qt-creator] LLDB CPU usage 100% on macOS Catalina (10.15)
>
> I recently got a new MacBookPro and so was forced to use macOS Catalina. I 
> just finally go around to debugging some code through QtCreator (4.10.1) and 
> while I was debugging the fans were screaming so I popped open activity 
> monitor and noticed that LLDB is spinning full a single CPU core. This is 
> while I am sitting at a breakpoint so the application is doing nothing. 
> 
> Has anyone else seen this? Is this normal under Catalina (10.15)? I can’t 
> imagine the hit to my battery life if I needed to debug while out of the 
> office.
> 
> Thanks
> --
> 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] MacOS: mouseReleaseEvent crash log

[Jason H]

I clicked "Abort debugging"

Process:   Qt Creator [33928]
Path:  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator
Identifier:org.qt-project.qtcreator
Version:   4.10.2 (4.10.2)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   Qt Creator [33928]
User ID:   501

Date/Time: 2019-11-27 15:37:42.954 -0500
OS Version:Mac OS X 10.14.6 (18G103)
Report Version:12
Bridge OS Version: 4.1 (17P1081)
Anonymous UUID:334B0A41-53C6-7D51-BD65-64A23C95424F

Sleep/Wake UUID:   F17D2D14-481C-4D2B-B6F9-030AD2C22282

Time Awake Since Boot: 23 seconds
Time Since Wake:   11000 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread
Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x3add3c5b7f70
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [33928]

VM Regions Near 0x3add3c5b7f70:
MALLOC_LARGE   00013b4be000-00013bcbe000 [ 8192K] rw-/rwx 
SM=PRV
-->
MALLOC_NANO6000-60003000 [768.0M] rw-/rwx 
SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libCore.dylib   0x00011263bda8 
Core::OutputWindow::mouseReleaseEvent(QMouseEvent*) + 232
1   org.qt-project.QtWidgets0x00010d18706d 
QWidget::event(QEvent*) + 445
2   org.qt-project.QtWidgets0x00010d22d92d 
QFrame::event(QEvent*) + 45
3   org.qt-project.QtCore   0x00010e4ade24 
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 148
4   org.qt-project.QtWidgets0x00010d14b618 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 248
5   org.qt-project.QtWidgets0x00010d14e488 
QApplication::notify(QObject*, QEvent*) + 7336
6   org.qt-project.QtCore   0x00010e4adb74 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
7   org.qt-project.QtWidgets0x00010d14bf50 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, 
QWidget**, QPointer&, bool, bool) + 896
8   org.qt-project.QtWidgets0x00010d1a654e 0x10d13b000 + 439630
9   org.qt-project.QtWidgets0x00010d1a5235 0x10d13b000 + 434741
10  org.qt-project.QtWidgets0x00010d14b62d 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
11  org.qt-project.QtWidgets0x00010d14ca32 
QApplication::notify(QObject*, QEvent*) + 594
12  org.qt-project.QtCore   0x00010e4adb74 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
13  org.qt-project.QtGui0x00010d7234e5 
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
 + 3397
14  org.qt-project.QtGui0x00010d70aa5b 
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
 + 219
15  libqcocoa.dylib 0x00010df33b30 0x10deff000 + 215856
16  libqcocoa.dylib 0x00010df34298 0x10deff000 + 217752
17  com.apple.CoreFoundation0x7fff2e655de3 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
18  com.apple.CoreFoundation0x7fff2e655d89 __CFRunLoopDoSource0 
+ 108
19  com.apple.CoreFoundation0x7fff2e63974b 
__CFRunLoopDoSources0 + 195
20  com.apple.CoreFoundation0x7fff2e638d15 __CFRunLoopRun + 1189
21  com.apple.CoreFoundation0x7fff2e63861e CFRunLoopRunSpecific 
+ 455
22  com.apple.HIToolbox 0x7fff2d8971ab 
RunCurrentEventLoopInMode + 292
23  com.apple.HIToolbox 0x7fff2d896ded 
ReceiveNextEventCommon + 355
24  com.apple.HIToolbox 0x7fff2d896c76 
_BlockUntilNextEventMatchingListInModeWithFilter + 64
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] [SPAM] Mac TouchBar question

[Jason H]

I hope not. It's brand new because my last one was suffering from battery 
cut-out issue.

> Sent: Wednesday, November 27, 2019 at 4:38 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] [SPAM] Mac TouchBar question
>
> 
> 
> > On Nov 26, 2019, at 17:01, Jason H  wrote:
> > 
> > I have no idea how the TouchBar on recent macs work. But sometimes when I 
> > hit "fn" on the keyboard the touch bar does not always change to the 
> > function keys "F1 ... F12"
> > Is there a way to identify the issue? Is this even a QtCreator thing or is 
> > it just buggy MacOS?
> 
> Qt Creator just tells macOS that it has a touch bar and its contents, I don’t 
> think we have anything to do with what is happening on fn.
> Maybe you are suffering from the overall MacBook keyboard degradation issue...
> 
> -- 
> Eike Ziller
> Principal Software Engineer
> 
> The Qt Company GmbH
> Erich-Thilo-Straße 10
> 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] [SPAM] Mac TouchBar question

[Jason H]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  I have no idea how the TouchBar on recent macs work. But 
sometimes
   when I hit "fn" on the keyboard the touch bar does not always change to the
   function keys "F1 ... F12" Is there a way to identify the issue? Is this
  even a QtCreator thing or is it just buggy MacOS? [...] 

Content analysis details:   (4.8 points, 4.6 required)

 pts rule name  description
 -- --
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.4997]
 0.0 FREEMAIL_FROM  Sender email is commonly abused enduser mail 
provider
(jhihn[at]gmx.com)
 0.0 SPF_HELO_NONE  SPF: HELO does not publish an SPF Record
 2.0 PDS_TONAME_EQ_TOLOCAL_SHORT Short body with To: name matches
everything in local email
 2.0 SPOOFED_FREEMAIL   No description available.


--- Begin Message ---
I have no idea how the TouchBar on recent macs work. But sometimes when I hit 
"fn" on the keyboard the touch bar does not always change to the function keys 
"F1 ... F12"
Is there a way to identify the issue? Is this even a QtCreator thing or is it 
just buggy MacOS?

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

[Qt-creator] OSX crash on monitor change

[Jason H]

Removed 2 monitors from my computer. Happened 2x today

Process:   Qt Creator [68542]
Path:  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator
Identifier:org.qt-project.qtcreator
Version:   4.10.2 (4.10.2)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   Qt Creator [68542]
User ID:   501

Date/Time: 2019-11-13 21:47:28.341 -0600
OS Version:Mac OS X 10.14.6 (18G103)
Report Version:12
Bridge OS Version: 4.1 (17P1081)
Anonymous UUID:334B0A41-53C6-7D51-BD65-64A23C95424F

Sleep/Wake UUID:   7C161453-908F-495F-B54A-B6624C705A52

Time Awake Since Boot: 11 seconds
Time Since Wake:   19 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x0014
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [68542]

VM Regions Near 0x14:
-->
__TEXT 000104f28000-000104f3c000 [   80K] r-x/rwx 
SM=COW  /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libqcocoa.dylib 0x000108473d47 0x108468000 + 48455
1   libqcocoa.dylib 0x0001084e 0x108468000 + 63358
2   com.apple.SkyLight  0x7fff5af16f66 
displayConfigFinalizedProc + 239
3   com.apple.SkyLight  0x7fff5af0d5c2 
CGSPostLocalNotification + 420
4   com.apple.SkyLight  0x7fff5af0d1b8 (anonymous 
namespace)::notify_datagram_handler(unsigned int, CGSDatagramType, void*, 
unsigned long, void*) + 93
5   com.apple.SkyLight  0x7fff5af10b5e 
CGSDatagramReadStream::dispatch_next_main_queue_datagram() + 242
6   com.apple.SkyLight  0x7fff5b1650f2 invocation function 
for block in 
CGSDatagramReadStream::dispatch_main_queue_datagrams_async(dispatch_queue_s*, 
CGSDatagramReadStream*) + 54
7   libdispatch.dylib   0x7fff61ca95f8 
_dispatch_call_block_and_release + 12
8   libdispatch.dylib   0x7fff61caa63d 
_dispatch_client_callout + 8
9   libdispatch.dylib   0x7fff61cb568d 
_dispatch_main_queue_callback_4CF + 1135
10  com.apple.CoreFoundation0x7fff35d7ca37 
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
11  com.apple.CoreFoundation0x7fff35d7c161 __CFRunLoopRun + 2289
12  com.apple.CoreFoundation0x7fff35d7b61e CFRunLoopRunSpecific 
+ 455
13  com.apple.HIToolbox 0x7fff34fda1ab 
RunCurrentEventLoopInMode + 292
14  com.apple.HIToolbox 0x7fff34fd9ee5 
ReceiveNextEventCommon + 603
15  com.apple.HIToolbox 0x7fff34fd9c76 
_BlockUntilNextEventMatchingListInModeWithFilter + 64
16  com.apple.AppKit0x7fff3337277d _DPSNextEvent + 1135
17  com.apple.AppKit0x7fff3337146b 
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 
+ 1361
18  com.apple.AppKit0x7fff3336b588 -[NSApplication run] 
+ 699
19  libqcocoa.dylib 0x00010849c013 0x108468000 + 213011
20  org.qt-project.QtCore   0x0001060eafef 
QEventLoop::exec(QFlags) + 431
21  org.qt-project.QtCore   0x0001060f0182 
QCoreApplication::exec() + 130
22  org.qt-project.qtcreator0x000104f33b63 main + 15139
23  libdyld.dylib   0x7fff61cf73d5 start + 1

Thread 1:: com.apple.CFSocket.private
0   libsystem_kernel.dylib  0x7fff61e3361a __select + 10
1   com.apple.CoreFoundation0x7fff35daa2d2 __CFSocketManager + 
635
2   libsystem_pthread.dylib 0x7fff61eeb2eb _pthread_body + 126
3   libsystem_pthread.dylib 0x7fff61eee249 _pthread_start + 66
4   libsystem_pthread.dylib 0x7fff61eea40d thread_start + 13

Thread 2:: QThread
0   libsystem_kernel.dylib  0x7fff61e3436e poll + 10
1   org.qt-project.QtCore   0x000106146060 
qt_safe_poll(pollfd*, unsigned int, timespec const*) + 608
2   org.qt-project.QtCore   0x0001061478ba 
QEventDispatcherUNIX::processEvents(QFlags) + 858
3   org.qt-project.QtCore   0x0001060eafef 
QEventLoop::exec(QFlags) + 431
4   org.qt-project.QtCore   0x000105f2605c QThread::exec() + 140
5   org.qt-project.QtCore   0x000105f26fd3 0x105f05000 + 139219
6   libsystem_pthread.dylib 0x7fff61eeb2eb _pthread_body + 126
7   libsystem_pthread.dylib 0x7fff61eee249 _pthread_start + 66
8   

Re: [Qt-creator] iOS not being detected

[Jason H]

xcode-select --reset to the rescue!


> Sent: Monday, November 11, 2019 at 4:44 PM
> From: "Jason H" 
> To: qt-creator 
> Subject: [Qt-creator] iOS not being detected
>
> I'm moving to a new computer. I have the iOS Qt stuff installed. I installed 
> brew after Qt, and now it doesn't see my iOS kit.
> I've re-installed Qt completely 3 times. Also it seems that Qt Creator keeps 
> picking up the previous install's preferences, which I would like to delete 
> as I work on this issue.
>
> Help?
>
>
> Js-MacBook-Pro:~ j$ xcode-select -p
> /Library/Developer/CommandLineTools
> Js-MacBook-Pro:~ j$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
> package-id: com.apple.pkg.CLTools_Executables
> version: 11.2.0.0.1.1571444319
> volume: /
> location: /
> install-time: 1573507327
> groups: 
> com.apple.FindSystemFiles.pkg-group___
> 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] iOS not being detected

[Jason H]

I'm moving to a new computer. I have the iOS Qt stuff installed. I installed 
brew after Qt, and now it doesn't see my iOS kit.
I've re-installed Qt completely 3 times. Also it seems that Qt Creator keeps 
picking up the previous install's preferences, which I would like to delete as 
I work on this issue.

Help?


Js-MacBook-Pro:~ j$ xcode-select -p
/Library/Developer/CommandLineTools
Js-MacBook-Pro:~ j$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.2.0.0.1.1571444319
volume: /
location: /
install-time: 1573507327
groups: com.apple.FindSystemFiles.pkg-group___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Which Camera?

[Jason H]

When I'm in QML and I've "import QtMultimedia 5.12" when I hit F1 on "Camera" 
it takes me to the Qt3D Camera, not the QtMultimedia camera.

Unfortunately we have a name collision in Qt. Similarly, QCamera is another 
example.

1. How can I get QtCreator to give help on the right camera? Normally, I would 
expect the "Choose Topic" dialog to appear. It does not. (it also says "Unknown 
Component" for Video)
1.1 F1 on "Video" brings up the Choose Topic dialog, but there is only one 
entry, "Video QML Type"

This is on MacOS, building a iOS project with Qt 5.12.5, QtC 4.10.1




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

Re: [Qt-creator] How to control font in compile output

[Jason H]

To be fair, it's not clear what those +- icons refer to, they are adjacent to the filter combo. They do have hover tool tips, which help. I think an argument could be made for moving them by the Maximize button? Then where they are, should be the  < > buttons, which would follow the Find / Replace mini pane precedent.

 

 

 

Sent: Friday, October 25, 2019 at 10:52 AM
From: "Michael Jackson" 
To: "Stanislav Ershov" , qt-creator@qt-project.org
Subject: Re: [Qt-creator] How to control font in compile output




Hilariously enough I am looking *everywhere* for some setting for the font. I _completely_ missed the “+” and “-“ buttons in the header part of the output pane. *Big* face palm….

 


--


Mike Jackson 

 


From: Qt-creator  on behalf of Stanislav Ershov 
Date: Friday, October 25, 2019 at 10:50 AM
To: Qt-creator 
Subject: Re: [Qt-creator] How to control font in compile output



 



To control font size, you can focus on output pane, and use ctrl+wheel.


 



пт, 25 окт. 2019 г. в 17:46, Michael Jackson :





QtCreator 4.10.1. How to set the font and font size in the compile output (and probably the application output also). I am on Windows and the compile output font is rather large. Not “stupid huge” which would be the case if my display scaling was off (it is set to 100%). I have been looking through all the settings and nothing is jumping out at setting the font size for those output panes.

 

Thanks

--

Mike Jackson 



___
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



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

[Qt-creator] Debug button not enabling

[Jason H]

I've noticed several times now that the Qt Creator 4.10.1 Debug icon (below 
Build/Play and above the Build hammer) is staying gray when nothing is 
happening. I can't seem to get it back...
Things I've tried:
- changing the active project
- running qmake for a project
- mix/max-imumizing the window
- build the project
- rebuild the current project
- close a project
- close all projects
- open a project after closing all

Only thing that works is closing QtC entirely.

Is there a way I can track down what is going on?


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

Re: [Qt-creator] Deployment of SerialTerminal plugin

[Jason H]

I'd argue that there should be a plugin screen in QtC, like there is in OctoPi, 
Cura, Chrome, Firefox, npm, Qpm, etc., where the user can browse & download 
plugins (or in Qt's case probably build)

> Sent: Tuesday, October 15, 2019 at 2:03 AM
> From: "Richard Weickelt" 
> To: qt-creator@qt-project.org
> Subject: Re: [Qt-creator] Deployment of SerialTerminal plugin
>
> Hi,
>
> > the Serial Terminal plugin was added to Qt Creator in spring 2018. It
> > still has the experimental state, but I think the biggest problem is
> > that it is not included in the official Qt Creator builds. A lot of
> > potential users might not even know it exists.
> >
> > Given the ongoing support for microcontrollers in Qt Creator, I think it
> > would be a good opportunity to deliver this plugin with Creator. It's
> > only dependency seems to be QSerialPort, which is a relatively
> > lightweight module and therefore should not hurt much.
>
> it would be useful. I guess the percentage of users creating QtCreator from
> source is close to 0. What is needed to get the Serial Terminal plugin out
> of the "experimental" state?
> ___
> 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] Deployment of SerialTerminal plugin

[Jason H]

> Sent: Sunday, October 13, 2019 at 2:59 PM
> From: "André Hartmann" 
> To: qt-creator 
> Subject: [Qt-creator] Deployment of SerialTerminal plugin
>
> Hi all,
> 
> the Serial Terminal plugin was added to Qt Creator in spring 2018. It
> still has the experimental state, but I think the biggest problem is
> that it is not included in the official Qt Creator builds. A lot of
> potential users might not even know it exists.
> 
> Given the ongoing support for microcontrollers in Qt Creator, I think it
> would be a good opportunity to deliver this plugin with Creator. It's
> only dependency seems to be QSerialPort, which is a relatively
> lightweight module and therefore should not hurt much.

O_o

Without knowing anything about this, it would probably be a help since I talk 
to 3D printers (Arduinos) and other serial things quite often. 

It would also be very cool if it could simulate a serial device so I could 
mimic real hardware.

How would I go about finding and installing this plug in? I looked in 
Preferences, nothing there, tried About Plugins.. doesn't seem to have an 
on-line repository search & install feature?


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

Re: [Qt-creator] 4.10.1: new issues on OSX

[Jason H]

https://bugreports.qt.io/browse/QTCREATORBUG-23064

> Sent: Tuesday, October 08, 2019 at 10:22 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] 4.10.1: new issues on OSX
>
> New in 4.10.1 compared to 4.10.0 ?
> We haven’t changed the Qt version between these two, so if there is a 
> difference between them, I wonder what triggers it.
> 
> Please create a bugreport.
> 
> Br, Eike
> 
> > On 8. Oct 2019, at 16:01, Jason H  wrote:
> > 
> > When moving the QtC wonder between monitors, it's really big, or really 
> > small. Please see attached.
> > - Small UI: Moved from Retina display to 1920x1080 display (DVI)
> > - Large UI: Moved from 1080p to Retina display
> > 
> > Eventually it will correct itself. But this is annoying, and new. It never 
> > used to do this. > 2019-10-08 at 9.57.54 AM.png>___
> > 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
> Erich-Thilo-Straße 10
> 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] linting error with QML State machine

[Jason H]

No matter what I do, it is not happy.
Either it says Invalid property name "target" when using a namespace, or it 
complains that State cannot have children even if there is no QtQuick import.
See attached.

Per https://doc.qt.io/qt-5/qmlstatemachine.html, "Using Both QtQuick and 
QtQml.StateMachine Imports" there should be a way to resolve this, but I'm not 
even using a QtQuick import.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] 4.10.1 release?

[Jason H]

Really glad to hear it, but I'm also waiting for a fix for QTCREATORBUG-22950
Since the only thing I really debug is iOS these days. Unfortunately, there's 
no movement visible from the issue. 

> Sent: Monday, October 07, 2019 at 9:03 AM
> From: "Tuukka Turunen" 
> To: "André Pönitz" , "Denis Rouzaud" 
> 
> Cc: "qt-creator@qt-project.org" 
> Subject: Re: [Qt-creator] 4.10.1 release?
>
> 
> Hi,
> 
> Release content is fine, but we found a problem in the installer / packaging 
> side.
> 
> We are trying to get the Creator 4.10.1 released as early tomorrow as 
> possible. 
> 
> Like Andre said, snapshots can be used meanwhile: 
> http://download.qt.io/snapshots/qtcreator/4.10/4.10.1/ 
> 
> Apologies for the delay in getting the fix released. 
> 
> Yours,
> 
>   Tuukka
> 
> On 04/10/2019, 10.21, "Qt-creator on behalf of Tuukka Turunen" 
>  wrote:
> 
> Hi,
> 
> We aim to release Creator 4.10.1 on Monday with the fix for XCode + other 
> fixes.
> 
> Yours,
> 
>   Tuukka
> 
> On 03/10/2019, 11.18, "Qt-creator on behalf of André Pönitz" 
>  wrote:
> 
> On Thu, Oct 03, 2019 at 09:54:38AM +0200, Denis Rouzaud wrote:
> > Hi list,
> > 
> > I would like to know if there any chance to get a bugfix release 
> any time
> > soon? i.e. before 4.11.
> 
> Someone else might want to comment on that.
> 
> 
> In any case, there are snapshots at
> 
>http://download.qt.io/snapshots/qtcreator/4.10/4.10.1/
> 
> that should be fairly close to anything that might be released as 
> 4.10.1.
> 
> The adaptations to the LLDB of Xcode 11 are included.
> 
> > The issue of not being able to use lldb with Xcode 11 is quite 
> annoying and
> > many people are asking online.
> 
> Indeed.
> 
> Andre'
> 
> ___
> 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
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Unable to debug with latest XCode

[Jason H]

Ah cool. Also XCode 11 broke being able to push apps to iPhones from Creator. 
https://bugreports.qt.io/browse/QTCREATORBUG-22950

> Sent: Wednesday, October 02, 2019 at 11:41 AM
> From: "Jyrki Yli-Nokari" 
> To: "Alexandru Croitor" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] Unable to debug with latest XCode
>
> They moved to python 3. There are two patches to the lldb python interface 
> file, run them and it will work again
>
> > Alexandru Croitor  kirjoitti 2.10.2019 kello 18.20:
> >
> > Perhaps it's this issue https://bugreports.qt.io/browse/QTCREATORBUG-22955
> >
> >> On 2. Oct 2019, at 17:17, Andy  wrote:
> >>
> >> Jason:
> >>
> >> It's not just you. I have the same problem.
> >>
> >> I just tried to debug a non-Qt command-line application and had the same 
> >> thing - "Debugging starts" and then it hangs. In the bottom-right it says 
> >> "Launching Debugger" with about 10% of the bar filled in. (Obviously I 
> >> don't get the QML popups.)
> >>
> >> In the debug panel it says "Setting up inferior..." whatever that means 
> >> (see attached).
> >>
> >> ---
> >> Andy Maloney  //  https://asmaloney.com
> >> twitter ~ @asmaloney
> >>
> >>
> >>
> >> On Wed, Oct 2, 2019 at 10:43 AM Jason H  wrote:
> >> I upgraded my XCode to 11 (it goes to 11!) (Qt calls it "SDK 10.15") and I 
> >> can't debug.
> >> All it says is:
> >> 09:39:23: Debugging starts
> >> the debug panes pop up, empty, and it just sits there. I can't kill it by 
> >> the usual means (no red square, attached), but I can kill it by closing 
> >> the output pane. At which time I get two popups (attached)
> >>
> >> Has anyone else seen this with XC11? Known issue, or should I report it in 
> >> Jira
> >>
> >>
> >> ___
> >> 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
> ___
> 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] Unable to debug with latest XCode

[Jason H]

I upgraded my XCode to 11 (it goes to 11!) (Qt calls it "SDK 10.15") and I 
can't debug.
All it says is:
09:39:23: Debugging starts
the debug panes pop up, empty, and it just sits there. I can't kill it by the 
usual means (no red square, attached), but I can kill it by closing the output 
pane. At which time I get two popups (attached)

Has anyone else seen this with XC11? Known issue, or should I report it in Jira


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

[Qt-creator] [SPAM] 4.10.0 Secchi Disk on opening

[Jason H]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  I thought I'd share an observation, I'm on a 2017 MBP and
  when I open QtC, it presents the welcome screen, fully populated. It 
immediately
   beachballs, then secchi disks, then beach balls again, then I get a normal
   mouse pointer. It takes about 12 seconds. I'm not sure what QtC is doing,
   but it'd be great if I could open a project since that takes some time as
   well. [...] 

Content analysis details:   (4.8 points, 4.0 required)

 pts rule name  description
 -- --
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.4964]
 0.0 FREEMAIL_FROM  Sender email is commonly abused enduser mail 
provider
(jhihn[at]gmx.com)
 0.0 SPF_HELO_NONE  SPF: HELO does not publish an SPF Record
 2.0 PDS_TONAME_EQ_TOLOCAL_SHORT Short body with To: name matches
everything in local email
 2.0 SPOOFED_FREEMAIL   No description available.


--- Begin Message ---
I thought I'd share an observation, I'm on a 2017 MBP and when I open QtC, it 
presents the welcome screen, fully populated. It immediately beachballs, then 
secchi disks, then beach balls again, then I get a normal mouse pointer. It 
takes about 12 seconds. I'm not sure what QtC is doing, but it'd be great if I 
could open a project since that takes some time as well.

There are 23 projects in the recent projects list, and 1 session.

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

[Qt-creator] Setting device name in 4.10.0

[Jason H]

Looks like I'm supposed to be able to set the device name?

But when I hit Ok, nothing happens (aside from dialog being closed)

I would expect the name in the Deploy selector to be updated?

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

Re: [Qt-creator] A really minor observation about QML & properties

[Jason H]

I don't _think_ this is how Qt APIs work though? Maybe I missed something, Qt 
classically has not used get() as a getter, but still provide properties 
and getters of the same name?  I had expected to be told something about how to 
change my declaration.

For example, QML Item instantiates QQuickItem. both have "clip".
 Q_PROPERTY(bool clip READ clip WRITE setClip NOTIFY clipChanged)

This is a property of Item, and a public function (getter) of QQuickItem. I 
assume there is some magic that tells QtC to know that when completing clip, to 
not add "()" ?

Also, for the member version, the docs don't say it, but I assume there is a 
standard setter generated with the if-value-change notify guard?




> Sent: Monday, September 09, 2019 at 3:29 PM
> From: "Damian Ivanov" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] A really minor observation about QML & properties
>
> Hi Jason,
>
> The READ function should have a different name like getName() the
> string before Read is what is exposed to QML.
> Also you could use MEMBER but READ and WRITE functions are more
> flexible in the end.
> https://doc.qt.io/qt-5/properties.html
>
> Regards,
> Damian
>
> On Mon, Sep 9, 2019 at 9:32 PM Jason H  wrote:
> >
> > When I make my own QML components in C, and I have a property and a slot 
> > named he same:
> > Q_PROPERTY(QString name READ name WRITE setName ...)
> >
> > When I'm typing, QtCreator appends "()" when I tab-complete rather than 
> > just completing the name.
> > x.na[TAB] -> x.name()
> > vs x.na[TAB] -> x.name (and continue on as: `= "name"`
> >
> > Usually when this is the case in QML, I want just to use it as a property 
> > not a function. I've not observed this with Qt's built-in classes. Does 
> > anyone know what I'm doing differently/wrong/could be doing better?
> >
> > Creator 4.9.2
> >
> >
> > ___
> > 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] A really minor observation about QML & properties

[Jason H]

When I make my own QML components in C, and I have a property and a slot named 
he same:
Q_PROPERTY(QString name READ name WRITE setName ...)

When I'm typing, QtCreator appends "()" when I tab-complete rather than just 
completing the name.
x.na[TAB] -> x.name()
vs x.na[TAB] -> x.name (and continue on as: `= "name"`

Usually when this is the case in QML, I want just to use it as a property not a 
function. I've not observed this with Qt's built-in classes. Does anyone know 
what I'm doing differently/wrong/could be doing better?

Creator 4.9.2


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

[Qt-creator] A very small Tooltip detail observation

[Jason H]

QVector v;

v.remove( -> tooltip [2 of 2| void remove(int i, int n)]

However the documentation says: "void QVector::remove(int i, int count)"

I had expected the tooltip to be [2 of 2| void remove(int i, int count)]

Not sure where these are being generated from, not necessarily an issue, or a 
QtCreator issue at that.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] This is seriously getting old.

[Jason H]

> All of this seems to work perfectly fine here with Qt Creator 4.9.2 from the 
> online installer, Qt 5.12.4 Desktop, macOS 10.14.6, dummy “Qt Quick 
> Application - Stack” with qmake.
> 
> Reg. Qt Quick Designer maybe check that
> Preferences > Qt Quick > Qt Quick Designer > QML Emulation Layer is using the 
> fallback emulation with the default path, but that wouldn’t explain errors in 
> the text editor afaik.
> 
> Br, Eike
> 
> > On 29. Aug 2019, at 21:47, Jason H  wrote:
> > 
> > OSX, Qt 5.12.1 and others installed (5.12.4 too)
> > 
> > I can't use the QML designer mode because it doesn't know QtQuick.Window or 
> > .Controls. But it compiles just fine. Installed Qt 5.12.4 and it doesn't 
> > show up as a kit, except for iOS and Android. I was going to try to use the 
> > form designer, but I get an error because it doesn't know what Window or 
> > Controls are and dumps me into an editor.


All my installs are done via installer (no source builds). Over the last two 
years on this machine, I've had various Qt versions, I think starting with 5.9 
or 5.10. I have used the installer to remove then and have settled on Qt 5.12.1 
(just installed 5.12.4, can't use it because not showing up except for mobile)

Indeed QML Emulation Layer is bing used, but the path is red and empty, but is 
saying $HOME/Qt/Qt Creator.app/Contents/Resources/qmldesigner ($HOME is my own 
shorthand)
I pressed reset paths, it became black. Nothing changed.  (the dir does exist, 
as a qt.conf and more (see below))
Went back into Preferences, it's red and empty again.
Tried Use EmulationLayer, pressed reset path, it got set to 
$HOME/.config/QtProject/qtcreator/qmlpuppet/ which does not exist. the 
qmlpuppet is not there. There is a qmlpuppet in $HOME/Qt/Qt 
Creator.app/Contents/Resources/qml/qmlpuppet Should it be that?


qt.conf:
[Paths]
Imports = ../../Imports/qtquick1
Qml2Imports = ../../Imports/qtquick2
Plugins = ../../PlugIns

Much thanks for the help! I look forward to finally getting this working!

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

[Qt-creator] This is seriously getting old.

[Jason H]

OSX, Qt 5.12.1 and others installed (5.12.4 too)

I can't use the QML designer mode because it doesn't know QtQuick.Window or 
.Controls. But it compiles just fine. Installed Qt 5.12.4 and it doesn't show 
up as a kit, except for iOS and Android. I was going to try to use the form 
designer, but I get an error because it doesn't know what Window or Controls 
are and dumps me into an editor.

Why is this still an issue?
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Deep TabNine

[Jason H]

Someone beat me to it too: https://github.com/zxqfl/TabNine/issues/103
 

Sent: Monday, July 29, 2019 at 11:06 AM
From: "Ariel Molina" 
To: "Jason H" 
Cc: qt-creator 
Subject: Re: [Qt-creator] Deep TabNine



You got me first. And they say the algorithms mined Github. So mining the Qt codebase would help on best practices specific to Qt.
 

Ariel
 


El lun., 29 de julio de 2019 10:03 a. m., Jason H <jh...@gmx.com> escribió:

Slashdot is running a sotrry bout an AI-powered editor extension Deep TabNine. https://tabnine.com/blog/deep
This seems to work via the language server protocol. IT pposts Python and C++ (and others)

What would it take to hook this up to 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] Deep TabNine

[Jason H]

Isn't that what any code completer is fundamentally?

> Sent: Monday, July 29, 2019 at 11:15 AM
> From: "Marco Bubke" 
> To: "Jason H" , qt-creator 
> Subject: Re: [Qt-creator] Deep TabNine
>
> Looks a little bit like copy 'n paste programming on steroids. ;-)
>
> On 29/07/2019 17:02, Jason H wrote:
> > Slashdot is running a sotrry bout an AI-powered editor extension Deep 
> > TabNine. https://tabnine.com/blog/deep
> > This seems to work via the language server protocol. IT pposts Python and 
> > C++ (and others)
> >
> > What would it take to hook this up to 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

[Qt-creator] Deep TabNine

[Jason H]

Slashdot is running a sotrry bout an AI-powered editor extension Deep TabNine. 
https://tabnine.com/blog/deep
This seems to work via the language server protocol. IT pposts Python and C++ 
(and others)

What would it take to hook this up to Qt-Creator?

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

[Qt-creator] Web Assembly?

[Jason H]

I'm watching Lars' QtWS18 keynote (just uploaded today). He mentioned 
WebAssembly is a big thing for Qt... So when can I select a WebAssembly as a 
deployment target?

Note: I still think WebAssembly is a terrible idea and QML should be it's own 
BSD licenced web technology. But I want to keep an open mind.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Dealing with python projects

[Jason H]

> Thanks for your feedback Chris, and Jason,
> hopefully you can help QtCreator to improve on the Python support.
> I will be more than happy to review your patches.

I'm not sure if you saw my previous suggestions, but for thoroughness:
1. I need something that either uses a conventional entry point or allows me to 
specify it. (like -e for c compiler)

2. Something that uses Python 3. Yes I know Mac only ships with Python 2, but 
Python 2 is coming to an end in 7 months.

3. Something that allows me to use the shebang #!/... to specify an 
interpreter. In particular, /usr/bin/env is good at picking one, i.e. 
/usr/bin/env python3, which sidesteps the hard-coding of the binary to a 
specific path and picks it up from the user's environment.

4. Unfortunately all python projects will be called "main" in the project 
explorer. Maybe the entry point should be $1.py where $1 is the name of the 
project and/or directory?


There is lack of clarity on what the proper python project file format is. I 
wonder why the existing C++ infrastructure can't be re-used? The differences 
(as I currently understand them):
1. No compiler - this is just a no-op.

2. The C convention entrypoint of main() is not present, therefore we need to 
specify it. (i.e. either use -e main like for clang or 
PYTHON_ENTRYPOINT=main.py) Python scripts often also have a library/main test:
if __name__== '__main__':
pass  # I am the entry script, parse sys.argv, etc. (great for testing)
else:
pass  # I am invoked as a library providing functions

Also entry points usually executable and have a shebang, though this is not 
needed.

3. SOURCES should be .py files and merged with DISTFILES for copy into the 
build dir. HEADERS can be ignored?


Questions:
1. Maybe there can be a pythtondeployqt?

2. Could we have a mixed-mode project where some C/C++ is built along with the 
python? Python Extending is a thing 
(https://docs.python.org/3/extending/index.html) Not sure if Qt provides Python 
helpers like Qt Android JNI helpers for calling functions and workin with Java 
Objects?


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

Re: [Qt-creator] Dealing with python projects

[Jason H]

Andre's Razor: Never attribute to lack of vision what that which can be 
attributed to lack of resources. :-)

> Sent: Wednesday, April 24, 2019 at 2:20 PM
> From: "André Pönitz" 
> To: "Jason H" 
> Cc: "Christian Gagneraud" , qt-creator 
> 
> Subject: Re: [Qt-creator] Dealing with python projects
>
> On Wed, Apr 24, 2019 at 06:29:52PM +0200, Jason H wrote:
> > Check out this thread:
> > https://lists.qt-project.org/pipermail/qt-creator/2019-March/007865.html
> > 
> > I also requested documentation on .pyproject and why a standard python 
> > project
> > format was not used. I think it isn't meant to be a proper python IDE, just 
> > one
> > good enough for PySide. Which is a shame.
> 
> A while ago I found out that missing features in software I use are not
> necessarily caused by people lacking interest or not seeing the light
> but simply by limited resources.
> 
> Andre'
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Dealing with python projects

[Jason H]

Check out this thread: 
https://lists.qt-project.org/pipermail/qt-creator/2019-March/007865.html

I also requested documentation on .pyproject and why a standard python project 
format was not used. I think it isn't meant to be a proper python IDE, just one 
good enough for PySide. Which is a shame.


> Sent: Tuesday, April 23, 2019 at 8:49 PM
> From: "Christian Gagneraud" 
> To: qt-creator 
> Subject: [Qt-creator] Dealing with python projects
>
> Hi there,
>
> I've started to use QtCreator for some of my python-based projects.
> I've configured a python language server [1], and the result is quite
> encouraging.
>
> I've tried "Import Existing Project" that creates a
> ".creator" project file but is imho too basic and C/C++
> oriented.
> I saw the '.pyproject' option, but i couldn't find any documentation.
> It seems to be tailored for python+Qt.
> So I recently switched to using Qbs. It currently allows me to
> organise my python files, and QtCreator is happy with this "broken"
> qbs project (broken=cannot be built).
> One interesting feature is that i can configure QtC to run the test
> webserver using a simple wrapper script. And with a project type of
> "python" (or whatever is not recognised by qbs) QtC skip the build
> process.
> What would be nice now is to have my unit tests integrated... :)
> My test command can generate JUnit XML files.
>
> I'm curious to know how other users deal with python projects, fancy
> share your workflow?
>
> Chris
>
> [1] https://github.com/palantir/python-language-server
> ___
> 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] Generate missing members

[Jason H]

That would be very cool... But in the nearer term, if the result of the move to 
cpp didn't leave me in the cpp, but kept me in the  header, that would be very 
cool as well.

> Sent: Friday, April 12, 2019 at 12:49 PM
> From: "Konstantin Tokarev" 
> To: "Jason H" , qt-creator 
> Subject: Re: [Qt-creator] Generate missing members
>
>
>
> 12.04.2019, 18:16, "Jason H" :
> > I am really liking this refactor option!. But is there any way to generate 
> > them in the .cpp? Currently Im using this refactor option, but I'd rather 
> > the stuff just appear in the CPP to start with... Using the move to .cpp 
> > refactor is a little clunky because it requires switching between files and 
> > you have to hunt down where in the .h it placed them. If there was a 
> > "Generate missing members in %class.cpp" that would be amazing.
>
> https://bugreports.qt.io/browse/QTCREATORBUG-19364
>
> >
> > Also, sometimes the indentation is wonky. (under indented) in the .h
> >
> > ___
> > Qt-creator mailing list
> > Qt-creator@qt-project.org
> > https://lists.qt-project.org/listinfo/qt-creator
>
> --
> Regards,
> Konstantin
>
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Generate missing members

[Jason H]

I am really liking this refactor option!. But is there any way to generate them 
in the .cpp? Currently Im using this refactor option, but I'd rather the stuff 
just appear in the CPP to start with... Using the move to .cpp refactor is a 
little clunky because it requires switching between files and you have to hunt 
down where in the .h it placed them. If there was a "Generate missing members 
in %class.cpp" that would be amazing.


Also, sometimes the indentation is wonky. (under indented) in the .h

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

[Qt-creator] Crazy idea 202: main.cpp wizards

[Jason H]

There are some things that just always happen in main.cpp, this is particularly 
true for QML stuff that happens for engine initialization.

It would be cool if:
1. There was a wizard/automated way to add a QObject-derived class to the main.
1a. Insert #include  if needed
1b. insert qmlRegisterType("com.mycompany.%PROJECTNAME%", 1, 0, 
"MyObject");
2. Support the other QML registration functions qmlRegisterSingletonType
3. Register Enums and the like.

There may be other non-QML template stuff appropriate in main. I don't know if 
this is hard or not but if there was a section:

/* Begin QtCreator Wizard Generated code. Do not edit, code managed by 
QtCreator */
 qmlRegisterType("com.mycompany.%PROJECTNAME%", 1, 0, "MyObject");
/* End QtCreator Wizard Generated code */

I also saw on stack exchange 
https://stackoverflow.com/questions/20089196/how-to-access-c-enum-from-qml
where the example has a static declareQML() function that registers itself. I 
don't know if this is preferred or not. Seems like more code and would make 
something like this harder. But if that is to continue, maybe have a thing in 
the class creation wizard to do that, or use that as the place to trigger the 
qmlRegisterType in main.cpp?

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

Re: [Qt-creator] Python support in 4.9

[Jason H]

Addendum: 
https://chriswarrick.com/blog/2014/09/15/python-apps-the-right-way-entry_points-and-scripts/

Implicitly I suggest that QtC be inline with eggs or setup.py ecripts, like it 
is compatible with cmake, and no wheels be re-invented.



> Sent: Wednesday, March 27, 2019 at 2:09 PM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] Python support in 4.9
>
> 
> 
> > On Mar 1, 2019, at 21:46, Jason H  wrote:
> > 
> > I was just taking a look at the beta, and am sharing my findings.
> > 
> > 1. it looks like there isn't a way to import an existing python project?
> > 1a. With an existing project how do I configure a .pyproject file, 
> > including specify the file with main / QApplication / entry point?
> 
> I think there currently is no transitioning implemented.
> If I understand that correctly the default entry point for a .pyproject is 
> the first file in the “files” list.
> (But you can create run configurations that start any of the python source 
> files in the project.)
> 
> > 2. I also created and selected the default Qt for Python - Window project 
> > and hit run, and I got:
> > 15:25:00: Starting /usr/bin/python 
> > /Users/jhihn/Projects/test_pythonwindow/main.py...
> > 
> > Traceback (most recent call last):
> >  File "/Users/jhihn/Projects/test_pythonwindow/main.py", line 3, in 
> >from PySide2.QtWidgets import QApplication, QMainWindow
> > ImportError: No module named PySide2.QtWidgets
> > 15:25:00: /usr/bin/python exited with code 1
> > 
> > But if I run it from the command line it works: 
> > python main.py   # works
> 
> I assume you are on macOS and I’d guess that this is related to the usual 
> “environment in Terminal is different than environment in applications 
> started from Finder/Dock/Spotlight”.
> Does it work when opening Qt Creator from the Terminal with open /Qt 
> Creator.app ?
> Or, which python executable are you actually using on the terminal, possibly 
> from Brew? The default in the python run configuration in Qt Creator seems to 
> be /usr/bin/python.
> 
> > 3. Starting QtCreator is slow. I get a beach ball and then a Secchi disk. 
> > Takes about 10 seconds.
> 
> Could you create a bugreport and attach a “Sample Process” from Activity 
> Monitor?
> 
> > 
> > 4. Unfortunately all python projects will be called "main" in the project 
> > explorer.
> > Maybe the entry point should be $1.py where $1 is the name of the 
> > directory? i.e. test_pythonwindow (see attached)
> 
> You mean when creating the project with the wizard?
> 
> I see that in the the “empty” wizard. That could be improved.
> In the “window” wizard you can specify any name for the project name and main 
> python file (default based on the main class name)
> 
> > 5. How do I specify python3 for a project? It seems to default to python 2?
> 
> You can specify the exact python interpreter to use in the run configuration. 
> I don’t see a way to change the default (which seems to be /usr/bin/python).
> 
> Br,
> 
> -- 
> 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

Re: [Qt-creator] Python support in 4.9

[Jason H]

> Sent: Wednesday, March 27, 2019 at 2:09 PM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] Python support in 4.9
>
> 
> 
> > On Mar 1, 2019, at 21:46, Jason H  wrote:
> > 
> > I was just taking a look at the beta, and am sharing my findings.
> > 
> > 1. it looks like there isn't a way to import an existing python project?
> > 1a. With an existing project how do I configure a .pyproject file, 
> > including specify the file with main / QApplication / entry point?
> 
> I think there currently is no transitioning implemented.
> If I understand that correctly the default entry point for a .pyproject is 
> the first file in the “files” list.
> (But you can create run configurations that start any of the python source 
> files in the project.)

There is no documentation (that I can find) about .pyproject file format.
There is no compatibilty (I assume) with python eggs. (SOURCES.txt, etc.)

> > 2. I also created and selected the default Qt for Python - Window project 
> > and hit run, and I got:
> > 15:25:00: Starting /usr/bin/python 
> > /Users/jhihn/Projects/test_pythonwindow/main.py...
> > 
> > Traceback (most recent call last):
> >  File "/Users/jhihn/Projects/test_pythonwindow/main.py", line 3, in 
> >from PySide2.QtWidgets import QApplication, QMainWindow
> > ImportError: No module named PySide2.QtWidgets
> > 15:25:00: /usr/bin/python exited with code 1
> > 
> > But if I run it from the command line it works: 
> > python main.py   # works
> 
> I assume you are on macOS and I’d guess that this is related to the usual 
> “environment in Terminal is different than environment in applications 
> started from Finder/Dock/Spotlight”.
> Does it work when opening Qt Creator from the Terminal with open /Qt 
> Creator.app ?
> Or, which python executable are you actually using on the terminal, possibly 
> from Brew? The default in the python run configuration in Qt Creator seems to 
> be /usr/bin/python.

So changing the python interpreter worked, per #5 below. Thanks!

> > 3. Starting QtCreator is slow. I get a beach ball and then a Secchi disk. 
> > Takes about 10 seconds.
> 
> Could you create a bugreport and attach a “Sample Process” from Activity 
> Monitor?

This seems to be fixed in the RC. 

> > 4. Unfortunately all python projects will be called "main" in the project 
> > explorer.
> > Maybe the entry point should be $1.py where $1 is the name of the 
> > directory? i.e. test_pythonwindow (see attached)
> 
> You mean when creating the project with the wizard?

Yes, screenshot attached. It defaults to main.py, but per Python, this should 
be __init__.py or %%PROJECTNAME%%.py

> I see that in the the “empty” wizard. That could be improved.
> In the “window” wizard you can specify any name for the project name and main 
> python file (default based on the main class name)

Cool. This is currently madness :-) (See other screenshot)
 
> > 5. How do I specify python3 for a project? It seems to default to python 2?
> 
> You can specify the exact python interpreter to use in the run configuration. 
> I don’t see a way to change the default (which seems to be /usr/bin/python).

The QtC should always detect and run the shebang, if present.
Typically my shebang looks like:
#1/usr/bin/env python3

Note Python2 support ends Jan 1 2020 (8 months from now)
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] [Development] [Announce] Qt Creator 4.9 RC released

[Jason H]

> We are happy to announce the release of Qt Creator 4.9 RC!
>
> https://blog.qt.io/blog/2019/03/27/qt-creator-4-9-rc-released/

QTCREATORBUG-20617
QTCREATORBUG-20697

The OSX & WINDOWS scrollbar issue where the find & lint locations (green & 
yellow, respectively) move is still there. At best it is annoying, at worst, it 
just doesn't work. I can have the dark area which represents the current view 
area centered over a find location and it's not anywhere in the view.

Plus as you scroll, they move. Sometimes a lot.

It'd be embarrassing to continue to release this with such a large visual 
defect.




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

Re: [Qt-creator] Python support in 4.9

[Jason H]

With QtC at RC1, I'm still looking for answers to these questions:

> 1. it looks like there isn't a way to import an existing python project?
> 1a. With an existing project how do I configure a .pyproject file, including 
> specify the file with main / QApplication / entry point?

> 4. Unfortunately all python projects will be called "main" in the project 
> explorer.
> Maybe the entry point should be $1.py where $1 is the name of the directory? 
> i.e. test_pythonwindow (see attached)

> 5. How do I specify python3 for a project? It seems to default to python 2?

I think regular users will have similar ones. 
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Clang code model issues

[Jason H]

> I wonder how slow "a tad slow on Windows" is?
>
> I recently did some speed measurements on Windows
> https://cristianadam.eu/20190318/speeding-up-libclang-on-windows/
>
> I don't know if the 4.9-rc1 has fixed the Windows missing code model
> debug messages, which you could use to find out how slow it is.
>
> Qt Creator is saving the clang code model internal files in %temp%.
> I noticed a speed bump if I used a ram drive to have the %temp% directory
> saved
> in memory, just like you would have on Linux with /tmp.


Something like this might be affected by having a virus scanner installed. 
Installing sophos increased my IPA signing from 5 mind to 26 minutes. Some 
efforts were made to adjust the scanner policy for xcode, but we never got 
below 25 minutes.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] 4.9 beta "close project" feature

[Jason H]

> I just have tried 4.9.beta 2 build and I noticed very annoying feature:
> 
> When you close project, ALL your open files are closed too! It is awful! 
> I found that it was done in
> 
> https://bugreports.qt.io/browse/QTCREATORBUG-15721
> 
> Why anyone decided it is a good change?  I don't want to close all my files.
> 
> My scenario:
> 
> - open project
> 
> - open some files , work-work;
> 
> - create some commits an a branch
> 
> - after work is done, I need to rebase my branch. So I close Qt Creator 
> project, do rebase and open it again. I usually still have all my files 
> opened!

I was one person who requested this feature, but it may not be working right? 
It shouldn't close _all_ the files, just the files of the project that is being 
closed. If I multiple projects loaded (I usually do) I don't want all my files 
closed anytime I close one of the projects.

From the .pro being closed, SOURCES,HEADERS,RESOURCES,DISTFILES should be 
closed.

If you need to edit the files of a project after the project is closed, why 
close the project?

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

[Qt-creator] Overzealous Autocomplete redux

[Jason H]

QMap map {
 {"Apple", "AAPL"},
};

After typing the comma, if I am in a class, I find myself in a popup with the 
member function names of the class that I am in.
If I am not in a class, I get the popup that is attached.

Is there a way to not have this happen, but still have usable autocomplete? I 
would posit that the popup in this situation is errant. Usually when I'm 
initializing these mappings there a quite a few, so the constant popup is 
annoying.

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

[Qt-creator] Moving markers in scrollbar.

[Jason H]

I hope the scrollbar marks are stable by the 4.9 release. In most cases they 
are an annoyance, but in some cases they are wholly wrong and despite being in 
the shaded area, the actual location is not on-screen. And you're not sure 
whether it's up or down...

(examples attached) They all get squished together when in the gray area___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Problems with 4.9 beta

[Jason H]

1. I created a new project, with Qt 5.12.1, I guess that I created it for iOS, 
but the graphic in the left column where you pick your kit does not show the 
iOS image (phone + apple logo) it's giving me the desktop icon. When I tried to 
build it, it ran the iOS toolchain though. (Attached)


2. I was adding some classes (3) via context menu ("Add New... ") and the 
entire menu became disabled aside from "Close all files in project XXX" and 
"Close project XXX". Some time later they became available again. (Attached)

3. Selecting a custom base class does not automatically include the header in 
the generated header. (Old issue, but maybe one day...)___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Python support in 4.9

[Jason H]

I was just taking a look at the beta, and am sharing my findings.

1. it looks like there isn't a way to import an existing python project?
1a. With an existing project how do I configure a .pyproject file, including 
specify the file with main / QApplication / entry point?

2. I also created and selected the default Qt for Python - Window project and 
hit run, and I got:
15:25:00: Starting /usr/bin/python 
/Users/jhihn/Projects/test_pythonwindow/main.py...

Traceback (most recent call last):
  File "/Users/jhihn/Projects/test_pythonwindow/main.py", line 3, in 
from PySide2.QtWidgets import QApplication, QMainWindow
ImportError: No module named PySide2.QtWidgets
15:25:00: /usr/bin/python exited with code 1

But if I run it from the command line it works: 
python main.py   # works

3. Starting QtCreator is slow. I get a beach ball and then a Secchi disk. Takes 
about 10 seconds.

4. Unfortunately all python projects will be called "main" in the project 
explorer.
Maybe the entry point should be $1.py where $1 is the name of the directory? 
i.e. test_pythonwindow (see attached)

5. How do I specify python3 for a project? It seems to default to python 2?









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

Re: [Qt-creator] Crazy small feature idea

[Jason H]

Excellent. It's rather buried though. 3 clicks for singing I'd use _many_ times 
a day? 

I've been wondering if it would be better to have a tool that takes a complete 
class and splits it out into .h and .cpp? It would look more like Java and 
would do a long way to DRY and eliminate the need for this in general, not just 
for Qt...

> Sent: Friday, March 01, 2019 at 10:24 AM
> From: "Eike Ziller" 
> To: "Jason H" 
> Cc: qt-creator 
> Subject: Re: [Qt-creator] Crazy small feature idea
>
> 
> 
> > On 28. Feb 2019, at 22:32, Jason H  wrote:
> > 
> > It would be cool if
> > 
> > While in a .c[pp] or .m[m] file, I could right click and from the context 
> > menu split the pane and bring up a the corresponding .h[pp]. (Or vice-vera)
> > Similar to "Switch Between Function Declaration/definition”.
> 
> Tools > C++ > Open Corresponding Header/Source in Next Split
> 
> -- 
> 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