Re: [Qt-creator] Performance of the editor (with git plugin)

[André Hartmann]

Hi Björn,

Sorry for the inconvenience.

Could you please create a bugreport for this so it is not forgotten?

Meanwhile, I think you don't need to deactivate the whole git plugin,
it would be enough to disable Instant Blame in Edit > Preferences >
Version Control > Git.

I can understand that getAuthorName takes some time because it is
synchronous, but it would be nice to know which part of instantBlame()
takes that much time because everything here should be async.

Best regards,
André

Am 13.05.23 um 23:21 schrieb Björn Schäpers:

Am 11.05.2023 um 22:35 schrieb Björn Schäpers:

Hi there,

I recently got a new machine at work, sadly with a new(ly configured)
anti virus software. And the performance of QtCreator when editing
went down. I thought the anti virus was to blame (in a way it is,
because if it's deactivated everything is fine again),

[...]

When I click into another editor (split view) or press F4 I've to wait
about 3 seconds before I can continue to work.

Kind regards,
Björn.

While this is being worked on (and I tried that patch) I discovered my
delay comes from somewhere else. A little bit (de-)activating plugins to
see who is to blame I can say my main delay is produced by the lambda
"setupBlameForEditor" in GitPluginPrivate::steupInstantBlame.

I put some qDebug timings in that function, the call to
GitClient::instance()->getAuthor(workingDirectory) takes something
between 1.1 and 1.4 seconds, and in the end the call to instantBlame()
takes another 1.2 to 1.3 seconds.

While I still try to convince my IT department that tools like git are
not dangerous and should not be delayed by the anti virus, for now I
disable the git plugin. But it would be nice if maybe this code could
run on a different thread so that it doesn't block the main loop.

Björn.





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

Re: [Qt-creator] Any plans to support python debugging?

[André Hartmann]

Hi André,

thanks for the historical treatise.

It's quite interesting that the Python debugger is already 13 years old!

For my usage, I don't expect a 100% perfect product, so what we have now
is already on a high level.

There are however two bugs that make the debugger unusable for me:

* QTCREATORBUG-28733 (global Python strings)
* QTCREATORBUG-28734 (running in Terminal)

If these could be fixed then everything else is low priority because me
and my colleagues can start using the debugger. Until then there will
probably be no new bugreports from my side.

If you have patches I'm open to test them and give feedback.

Thanks again for the great product. Please keep up the good work!

Regards, André

Am 03.02.23 um 09:18 schrieb A. Pönitz:

On Mon, Jan 30, 2023 at 02:47:33PM +0100, André Hartmann wrote:

Hi Christian,

indeed it works. One requirement seems to be a .pyproject file [1],
containing your Python file. Then you get a debug and a run button.

Very nice!

My breakpoint was ignored first and the app stopped at the first line,
but I then could run until the breakpoint. I could inspect the
variables, step over instructions. Just what you expect from a debugger.

Awesome!

Now my question: Is this an official feature? I.e. can I create
bugreports when I discover small bugs? Also, there does not seem to be
much documentation, I guess few people working with that feature therefore?


Thanks for that wonderful IDE. I cannot imagine working with something else.

Regards,
André

[1] I've created an Empty Qt for Python Application as there was no
"Python without Qt" app template, but that instantly worked when I
replaced the main.py with my simple Python code.
[...]


Regarding the "officiality":

I added the python debugger during the "big debugger rewrite" in 2010
bacically only to have another example of setup that should be supported
at least conceptually to get the DebuggerEngine API right. Python/PDB
was chosen as it operated a bit differently then the C/C++ debuggers GDB
and CDB (LLDB came later) insofar that it runs "in process" of the
debuggee and the typesystem is different).

As it "happens to work", is small and is occasionally used there are
enough reasons to keep it around.

You have noticed that the integration in the project management system
(by .pyproject, previously .pyqtc) is clumsy. That's mainly due to the
lack of possibilities to do it better back then; and it also one of the
reasons that's not quite official and documented: I simply don't think
it's in a good enough shape to be worth spending time on that.

Having said that, times are changing. The project management side is
much more flexible nowadays, and on the debugger side I'll probably have
to look into the Debugger Adapter Protocol at some time, i.e. I expect
some activity in the general area towards the end of the year / Creator
~12 time frame. If there are bug reports for the python debugger
indicating interest and if there are possibly even people around to test
stuff I guess it should be possible to spend a few cycles on it ;-}

Andre'



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

Re: [Qt-creator] Any plans to support python debugging?

[André Hartmann]

Hi Alexandru,

thanks for the link to the report, I'll watch it.

I currently have no mixed mode debugging requirement, but that might
change in future.

Thanks and regards,
André

Am 30.01.23 um 13:27 schrieb Alexandru Croitor:

Hi,

I think this bug report is related to mixed mode debugging.

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


On 30. Jan 2023, at 13:19, Christian Stenger via Qt-creator 
 wrote:

Hi Andre,

If you're talking about debugging pure Python QC should just work.
If you mean debugging an application that is based on C++ and may end up inside 
Python code this is not possible at the current state.

IIRC we had some discussion some time ago, but so far we had not the time to 
have a deeper look. I think there's not even a bugreport / feature request for 
this to be able to vote on.

BR,
Christian


From: Qt-creator  on behalf of André Hartmann 

Sent: Monday, January 30, 2023 1:04 PM
To: qt-creator
Subject: [Qt-creator] Any plans to support python debugging?

Hi Creator developers and users,

when I see my colleagues installing vscode just to debug python,
I wonder if Creator couldn't do that too?

We already have good Python support with the language server, Qt itself
has Python bindings and Creators debugger interface uses Python dumpers,
so my question: are there any plans to support debugging Python code?

Thanks and best regards,
André
--
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] Any plans to support python debugging?

[André Hartmann]

Hi Christian,

indeed it works. One requirement seems to be a .pyproject file [1],
containing your Python file. Then you get a debug and a run button.

Very nice!

My breakpoint was ignored first and the app stopped at the first line,
but I then could run until the breakpoint. I could inspect the
variables, step over instructions. Just what you expect from a debugger.

Awesome!

Now my question: Is this an official feature? I.e. can I create
bugreports when I discover small bugs? Also, there does not seem to be
much documentation, I guess few people working with that feature therefore?

Thanks for that wonderful IDE. I cannot imagine working with something else.

Regards,
André

[1] I've created an Empty Qt for Python Application as there was no
"Python without Qt" app template, but that instantly worked when I
replaced the main.py with my simple Python code.

Am 30.01.23 um 13:19 schrieb Christian Stenger:

Hi Andre,

If you're talking about debugging pure Python QC should just work.
If you mean debugging an application that is based on C++ and may end up inside 
Python code this is not possible at the current state.

IIRC we had some discussion some time ago, but so far we had not the time to 
have a deeper look. I think there's not even a bugreport / feature request for 
this to be able to vote on.

BR,
Christian


From: Qt-creator  on behalf of André Hartmann 

Sent: Monday, January 30, 2023 1:04 PM
To: qt-creator
Subject: [Qt-creator] Any plans to support python debugging?

Hi Creator developers and users,

when I see my colleagues installing vscode just to debug python,
I wonder if Creator couldn't do that too?

We already have good Python support with the language server, Qt itself
has Python bindings and Creators debugger interface uses Python dumpers,
so my question: are there any plans to support debugging Python code?

Thanks and best regards,
André
--
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] Any plans to support python debugging?

[André Hartmann]

Hi Creator developers and users,

when I see my colleagues installing vscode just to debug python,
I wonder if Creator couldn't do that too?

We already have good Python support with the language server, Qt itself
has Python bindings and Creators debugger interface uses Python dumpers,
so my question: are there any plans to support debugging Python code?

Thanks and best regards,
André
--
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Closing pinned files

[André Hartmann]

Hi Mitch,

first of all, I'm no user of this feature, so I had to google it first.
But let me add my opinion:

Seeing the motivation for the feature - to keep files in the Open
Documents list and in the Locator - leads to the question:

Do you really want to forbid to actually close the split containing the
file, or do you just want to keep the file name in the Open Documents list?

If the latter is sufficient, then no user question is needed.

If the split should indeed actually stay open, I'd prefer a yellow info
box at the document top:

  "File is pinned, unpin to close" [Unpin & Close] [X]

as this is the least intrusive way (I really don't like messageboxes).

Another possibility would be to keep the file/split open but show the
next file in the list, until all unpinned files are closed.

But the point I'm with you: pinned files should not close without
confirmation, and therefore I don't think a global setting allowing that
is useful.

Best regards,
André

Am 21.10.22 um 11:45 schrieb EXT Mitch Curtis via Qt-creator:

… and Close All will be unaffected by this change; it just won’t do
anything, as before, as it’d be too disruptive.

*From:*Qt-creator  *On Behalf Of *EXT
Mitch Curtis via Qt-creator
*Sent:* Friday, 21 October 2022 5:43 PM
*To:* qt-creator@qt-project.org
*Subject:* [Qt-creator] Closing pinned files

For a while now I’ve been meaning to implement
https://bugreports.qt.io/browse/QTCREATORBUG-25964
 to save myself the
trouble of accidentally closing pinned files. Currently, pinned files
are only immune from Close All, but closing via Ctrl+W, context menu,
etc. will still close them without any prompt.

I’m curious if anyone has opinions on potential solutions to this.
Should we:

- Ask the user if they want to close the pinned file, defaulting to
“No”, and with the option to never ask again? To me, allowing the option
to never ask again seems to defeat the purpose of pinning files; it’s
too easy to accidentally close pinned files in the future.

- Tell the user that pinned files cannot be closed, and that they have
to be unpinned first. This option is perhaps less convenient, but in my
experience, I almost never want to close pinned files, so it seems more
foolproof. For those that dislike this, perhaps there could be a link to
the settings to permanently disable it.

What do you think?


___
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] "-j" options to make. Where do they come from? Can I change the value?

[André Hartmann]

Dear Toralf,

The jobs option was introduced in response to
https://bugreports.qt.io/browse/QTCREATORBUG-18414

You can fine tune that in the Projects > Build & Run > Build > Build
Steps. It should also be possible to add a smaller jobs option (e.g.
-j2) to the MAKEFLAGS variable so new projects use that.

> If I have 4 jobs with 4 cores, that can mean all of them are
> saturated, and the system becomes completely unresponsive.

I only have this problem if I specify more jobs than available cores.

Best regards,
André

Am 09.02.22 um 11:13 schrieb Toralf Lund:

I'm using Qt Creator on a system that has 4 CPU cores. It seams like
that means "make" will always be run with argument "-j4". Is there a way
I can change the number 4 to something smaller? Where does the option
come from anyway?

A problem I have is that certain compile or link steps will use all the
capacity of one core, and parallel jobs typically start on separate
cores. If I have 4 jobs with 4 cores, that can mean all of them are
saturated, and the system becomes completely unresponsive. Meaning I
have to just sit and wait for the build to finish, while I prefer to run
it "in the background" (even if it it takes longer that way) and
continue to work on something else.

OS is CentOS Stream 8.

- Toralf


___
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] Clicking on Fortran issues in Issues tab does not open the file in editor

[André Hartmann]

Dear Goran,

my guess is, that the line numbers in the format file(line) irritate the
parser - you can see the filename has the additional (line) while the
line column is empty. Afaik, Intel compilers are modeled after Microsoft
ones which uses such format in contrast to gcc, which has file:line:column.

I'd suggest you to create a report at bugreports.qt.io, to include the
screenshots from this mail and _important_ a plain text of the compile
output. If possible, include a working (C++) compiler error and a
non-working (fortran). Maybe that's enough to extend the parser unit
tests and make your case work.

Please add a link to the bugreport here as reply so others can follow.

Thanks and best regards,
Andre

On 22.08.21 21:06, Goran Žauhar via Qt-creator wrote:

Hi there!

I have application written in Fortran and C++. CMake and ninja are used
for compiling. Fortran compiler is Intel Fortran (ifort).

I use QtCreator for development and I am very happy with the setup but
I have one annoying issue with QtCreator: ifort warnings/errors are
present in Issues tab but clicking on them does not open the file in
editor.

C++ issues in Issues tab work as expected - clicking on them does
indeed open the file in editor and the cursor is positioned in the line
with the error/warning.

I have experimented with Custom Output parsers but without any luck.

I have attached the screenshot of the Issues tab, Compiler Output tab
and Error dialog.

Can I somehow configure QtCreator to overcome this or is it issue with
how QtCreator parses compiler output?

Thank you,
/Goran


___
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] Request advices for Qt Creator plugin developers to adopt API changes easily

[André Hartmann]

Hi all,

sorry for hijacking this thread, but having a terminal integrated into
Creator sounds like a great addition.

There has been https://bugreports.qt.io/browse/QTCREATORBUG-8511 plus
duplicates for years, so maybe that is the chance to get that thing in?

Best regards,
André

On 13.02.21 07:52, André Pönitz wrote:

On Wed, Feb 03, 2021 at 11:04:20PM +0800, Vincent Hui wrote:

Hi Andre',


Hi.


Sorry for my late reply.
Now the contributors of ros_qtc_plugin are preparing upstreaming
ros_qtc_plugin to Qt Creator repository.

[1]https://github.com/ros-industrial/ros_qtc_plugin/issues/406#issuecomment-766868092
Would you mind giving them some advices how to upstream ros_qtc_plugin to
Qt Creator repository quickly. I think upstreaming ros_qtc_plugin can
greatly benefit to both of ROS community of Qt community.
br,
Vincent


Sorry, this fell through the cracks.

We had a short chat in the meantime here.

There are currently two possible ways to integrate plugins into Creator,
first a "full integration" in the Creator core code base, with all the benefits
and all the restrictions, and second an integration as submodule in the
super-repo, which currently contains Creator proper as submodule, as well
as a Haskell support plugin and a plugin for the fossil source control system.
The super-repo is located at http://code.qt.io/cgit/qt-creator/qtc-super.git/

The long term plan is to move more to the modular (i.e. super-repo) path.
It also looks like the ros_qtc_plugin seems to have a hard dependency
on QTerminalWidget which would probably be hard to get into the
Creator core because that would need the license agreement be accepted
from the QTerminalWidget folks.

So the suggestion is to choose the second option, i.e. have
https://code.qt.io/cgit/qt-creator/plugin-ros.git similar to what is there for
plugin-haskell and plugin-fossil, and link that as submodule from qtc-super.

This would require:
- someone to request the creation of this repo on the
   developm...@qt-project.org mailing list
   and create a corresponding jira task. Anyone could do that, if you don't
   want to, I'd do it,
- in that request we need to name someone who will feel responsible for it,
   suggestion here is that this is you or someone else from the ROS community

The implications of being in the super-repo are:
- the plugin will get "automatical" updates when internal Creator API changes,
   so it is kept *compilable*, but final verification of a "working" state will
   (often) be left to the "responsible person"
- the plugin will *not* be part of the pre-compiled Qt Creator binaries or the
   Qt install.
- there will be pre-build binaries for the plugin created for each Qt Creator
   release, at https://github.com/qt-creator/plugin-ros/releases/..., which
   can be used together with the pre-compiled Qt Creator binaries.
- there would be no hard requirement to stick to Qt Creator coding style rules.

If that sounds ok for you we'd need the name of the "responsible person"
to request the repo.

If it is not ok for you, we can have a second look on whether integration into
the Creator core distribution would be possible. That would start with
clarifying the state of the QTermWidget dependency.

Best regards,
Andre'



On Wed, 8 May 2019 at 05:31, André Pönitz <[2]apoen...@t-online.de> wrote:

  On Tue, May 07, 2019 at 04:16:17PM +0800, Vincent Hui wrote:
  > Hi,
  >
  > Thank for developing Qt Creator such a great IDE.
  >
  > I am a user of ROS Qt Creator Plug-in
  > <[3]https://github.com/ros-industrial/ros_qtc_plugin>. After a new
  version of
  > Qt Creator had been released, it took the developer of ROS plugin a
  long
  > time to adopt Qt Creator API changes to support a new version of Qt
  Creator.
  >
  > My question is how to let plugin developers to adopt API changes
  easily so
  > that tey can release newer pulgins quickly ?

  The changes are all visible in git, so in principle anyone interested
  could
  follow up immediately.

  However, I see and know that this is quite some effort.

  One potential workaround is to develop the plugin in-tree, i.e. submit
  it
  to the Qt Creator source on [4]codereview.qt-project.org. If it is
  accepted
  there it will at least get mechanical adapted to API changes. Release
  testing and/or feature work will not be covered.

  Andre'

References

Visible links
1. 
https://github.com/ros-industrial/ros_qtc_plugin/issues/406#issuecomment-766868092
2. mailto:apoen...@t-online.de
3. https://github.com/ros-industrial/ros_qtc_plugin
4. http://codereview.qt-project.org/

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



___
Qt-creator mailing 

Re: [Qt-creator] access to gdb console

[André Hartmann]

Hi Stefan,

you probably want to comment and vote on
https://bugreports.qt.io/browse/QTCREATORBUG-19870 as ultimate solution.

Until then, you can use the left part of Views > Views > Debugger Log to
insert GDB commands.

Note that you can also add gdb startup commands at Tools > Options >
Debugger > GDB.

Best regards,
André

On 29.12.20 20:46, Stefan Seefeld wrote:

Hello,

I'm working on a big project including many C++ libraries and
applications, as well as a number of Python bindings (extension modules).

In some cases, I need to start the debugger (gdb), set up the
environment (e.g. run `exec target python3`), then start the target app
(often enough a Python wrapper script). (The process is described here:
https://www.boost.org/doc/libs/1_75_0/libs/python/doc/html/faq/how_do_i_debug_my_python_extensi.html)

While I'm comfortable doing all of this from a terminal, I have
difficulties figuring out how to do this from within qtcreator.

Could someone please help ? Does qtcreator give access to the debugger
console ?

Thanks !

Stefan
--

   ...ich hab' noch einen Koffer in Berlin...


___
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] How do you debug QtCreator

[André Hartmann]

Hi Björn,

if you really need to debug on Windows, use a MSVC build of Creator, 
that is times faster than a MinGW build.


However, the best experience is still on Linux.

Best regards,
André

Am 07.12.2020 um 22:13 schrieb Björn Schäpers:
Seriously, I did it on the weekend to find a bug I now have fixed. But 
it took a massive amount of time until the Creator started with gdb 
attached, similar switching sessions took ages.


I'm on Windows 64 Bit and use MinGW 64 Bit.

Or do you normally not debug directly?
___
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] Has anyone got the new custom parsers running?

[André Hartmann]

Hi Christian,

I'm feeling stupid now... I totally missed the fact that the parser 
needs to be enabled in the projects Run settings - which totally makes 
sense.


You already have a hint there where to configure the parsers, however 
having a hint in the reverse direction would have helped:


https://codereview.qt-project.org/c/qt-creator/qt-creator/+/309675

Thank you all for your help, it works nicely now.

Best regards,
André

Am 07.08.20 um 15:12 schrieb Christian Stenger:

Hi Andre,

I had a similar issue...: you have custom output parsers on the build *and* on 
the run settings of a project.
I had added them only to the build settings and wondered as well.. Enabling 
them on the run settings helped here..

BR,
Christian


From: Qt-creator  on behalf of Christian Kandeler 

Sent: Friday, August 7, 2020 2:56 PM
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] Has anyone got the new custom parsers running?

On Fri, 7 Aug 2020 14:02:06 +0200
André Hartmann  wrote:


I've created a project with a main.cpp like that:

#include 

int main()
{
   printf("main.cpp:5: Hello World\n");
   return 0;
}

Running that gives me the following Application Output:

13:49:52: Starting /home/user/build-Test/Test ...
main.cpp:5: Hello World
13:49:52: /home/user/build-Test/Test exited with code 0

I've then added a new Custom Output Parser in Tools > Options >
Build & Run > Custom Output Parsers with the following
pattern: "(.*):(\d+): (.*)" (without quotes, of course), which
passed the test text "main.cpp:5: Hello World" (without quotes) in
the  Custom Parser dialog. Capturing stdout and stderr was both enabled.

After pressing Ok, I've run my program again, the output appeared in
Application Output, but nothing happened in the Issues pane.

I've expected the message to appear in the Issues pane.

Is there any obvious wrong in my test?


No, and your example works for me.
Are you sure you're not filtering anything relevant? Note that custom parsers currently 
all have the type "compile output", even for run configurations.


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




--
André Hartmann, Dipl. Ing. (FH)
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de
Tel: +49.351.26996-43 | Fax: +49.351.26996.21

iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Tanju Gleisberg, Tobias Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

iseg on LINKEDIN | Let´s stay connected!
iseg on YOUTUBE | Tutorials and more ...
iseg on TWITTER | please follow!
iseg CATALOG | download iseg´s latest product catalog as PDF
iseg DOWNLOADS | manuals, software, firmware and more...
iseg high voltage power supply

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Has anyone got the new custom parsers running?

[André Hartmann]

Hi Christian,

thanks for your answer. Ok, here's what I did.

I've created a project with a main.cpp like that:

#include 

int main()
{
printf("main.cpp:5: Hello World\n");
return 0;
}

Running that gives me the following Application Output:

13:49:52: Starting /home/user/build-Test/Test ...
main.cpp:5: Hello World
13:49:52: /home/user/build-Test/Test exited with code 0

I've then added a new Custom Output Parser in Tools > Options >
Build & Run > Custom Output Parsers with the following
pattern: "(.*):(\d+): (.*)" (without quotes, of course), which
passed the test text "main.cpp:5: Hello World" (without quotes) in
the  Custom Parser dialog. Capturing stdout and stderr was both enabled.

After pressing Ok, I've run my program again, the output appeared in
Application Output, but nothing happened in the Issues pane.

I've expected the message to appear in the Issues pane.

Is there any obvious wrong in my test?

Best regards,
André

Am 07.08.20 um 12:13 schrieb Christian Kandeler:

On Fri, 7 Aug 2020 09:01:25 +0200
André Hartmann  wrote:


To my understanding, I can use the parsers to catch patterns in the
Compile and Application output and bring them to the Issues tab.


Correct.


However, I didn't manage to do that with Qt Creator 4.13-rc2 (from
Online Installer), no matter which patterns I try.

What am I missing?


Difficult to say without a concrete example.


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




--
André Hartmann, Dipl. Ing. (FH)
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de
Tel: +49.351.26996-43 | Fax: +49.351.26996.21

iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Tanju Gleisberg, Tobias Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

iseg on LINKEDIN | Let´s stay connected!
iseg on YOUTUBE | Tutorials and more ...
iseg on TWITTER | please follow!
iseg CATALOG | download iseg´s latest product catalog as PDF
iseg DOWNLOADS | manuals, software, firmware and more...
iseg high voltage power supply

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

[Qt-creator] Has anyone got the new custom parsers running?

[André Hartmann]

Hi all,

I wanted to try the custom parsers in the Build & Run section.

To my understanding, I can use the parsers to catch patterns in the 
Compile and Application output and bring them to the Issues tab.


However, I didn't manage to do that with Qt Creator 4.13-rc2 (from 
Online Installer), no matter which patterns I try.


What am I missing?

Thanks and best regards,
André

--
André Hartmann, Dipl. Ing. (FH)
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de
Tel: +49.351.26996-43 | Fax: +49.351.26996.21

iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Tanju Gleisberg, Tobias Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

iseg on LINKEDIN | Let´s stay connected!
iseg on YOUTUBE | Tutorials and more ...
iseg on TWITTER | please follow!
iseg CATALOG | download iseg´s latest product catalog as PDF
iseg DOWNLOADS | manuals, software, firmware and more...
iseg high voltage power supply

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Stepping down as maintainer of Qt Creator's C/C++ language support

[André Hartmann]

Am 18.05.20 um 08:31 schrieb Nikolai Kosjar:

Hiya,

as this is my last month with the Qt Company, I'm stepping down as the 
maintainer of Qt Creator's C/C++ language support.


It was my pleasure to work with some extraordinary ladies and gentlemen. 
Thank you.


The Qt Company is interested in a successor. Until a long-term 
replacement is found/evolves, Christian Kandeler will keep an eye on the 
C/C++ language support.


Nikolai


Dear Nikolai,

I like to thank you very much for your work on Qt Creator and the 
integration of Clang & Co. during the last 8 years. It was always good 
and joyful working with you. I have probably driven you crazy more than 
once with my extraordinary bug reports and suggestions, but you managed 
that easily.


So thanks for making Creators C++ integration really awesome. I wish you 
all the best on your future path!


And because it comes up: Christian, you did a great job polishing the 
Project Management subsystem during the last 18 month. A lot of really 
old bugs were resolved, so I like to express my respect. All the best 
with your new tasks, too.


Best regards,
André

--
André Hartmann, Dipl. Ing. (FH)
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de
Tel: +49.351.26996-43 | Fax: +49.351.26996.21

iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Tanju Gleisberg, Tobias Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

iseg on LINKEDIN | Let´s stay connected!
iseg on YOUTUBE | Tutorials and more ...
iseg on TWITTER | please follow!
iseg CATALOG | download iseg´s latest product catalog as PDF
iseg DOWNLOADS | manuals, software, firmware and more...
iseg high voltage power supply

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail. Das unerlaubte
Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Create SplitView in EditorManager programmatically

[André Hartmann]

Dear Vidhya Arun,

Please note that there is currently a markdown viewer in development / 
review: https://codereview.qt-project.org/c/qt-creator/qt-creator/+/287928


Maybe your plugin and the markdown viewer can join forces - after all 
the use case should be similar.


Regards, André

Am 06.03.20 um 15:33 schrieb Eike Ziller:




On 6. Mar 2020, at 15:29, Eike Ziller  wrote:




On 6. Mar 2020, at 15:15, Vidhya Arun  wrote:

Hello All

I am creating a plugin for ascii doc preview for which I need to create a 
splitView in the EditorManager.
My idea is to create a plainTextEdit in one side of Editor and a previewer in 
the other split.

Are there any methods exposed directly from TextEditor or EditorManager plugin 
to create this split view (The split Side by side functionality that we are 
able to do it manually in QtCreator editor is what am trying to call 
programatically )


The only options that you have programmatically are 
"EditorManager::openEditor(filename, Id(), EditorManager::OpenInOtherSplit)” 
(opens document in “next” split view, creates split view if there is none yet),


That is available for any editor-opening method, like 
EditorManager::openEditorWithContents, which might be more appropriate if you 
create an in-memory preview.


and possibly "EditorManager::openEditor(, 
EditorManager::SwitchSplitIfAlreadyVisible)", which does not open the document in 
the current view, if it is already visible in a different view.
Otherwise splits are currently not exposed to the outside.





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden.

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

Re: [Qt-creator] Minor autocompletion suggestion annoyances

[André Hartmann]

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

Re: [Qt-creator] Compliment for the generic highlighter support

[André Hartmann]

Hi Denis,

> Andre, you rejoice too much.

Maybe. But I was really positive impressed in that moment, and I wanted
to give it back.

Some motivation is needed from time to time. I write 100 bugreports or
so per year, so giving positive feedback will be good.

> But still it is not possible to set a custom rules to highlight the
> some specific compiler keywords (e.g. for a bare-metal programming)
> yet. :)

Yeah, there are dozens of areas that can be improved. And bit by bit
they will :)

Best regards,
André


On 13.02.20 16:59, Denis Shienkov wrote:

Hi all,

Andre, you rejoice too much.

But still it is not possible to set a custom rules to highlight the some
specific compiler keywords (e.g. for a bare-metal programming) yet. :)

BR, Denis

чт, 13 февр. 2020 г. в 11:07, André Hartmann mailto:andre.hartm...@iseg-hv.de>>:

Hi Qt Creator developers,

I just want to send out a bit Thank You for the usability of the
generic
highlighter.

I opened a Yocto project in a fresh installed Qt Creator. It offered me
to download to KSyntaxHighligher definitions, which worked well, and my
.bb file was instantly highlighted.

I then opened an .inc file and another toolbar offered to select the
correct highlighting here, because multiple definitions exists for the
generic extension .inc. After selecting "Bitbake" it was highlighted
properly.

I'm really impressed - that's how I expect software to work.

Keep up this high quality.

Best regards,
André

___
Qt-creator mailing list
Qt-creator@qt-project.org <mailto: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] Compliment for the generic highlighter support

[André Hartmann]

Hi Qt Creator developers,

I just want to send out a bit Thank You for the usability of the generic 
highlighter.


I opened a Yocto project in a fresh installed Qt Creator. It offered me 
to download to KSyntaxHighligher definitions, which worked well, and my 
.bb file was instantly highlighted.


I then opened an .inc file and another toolbar offered to select the 
correct highlighting here, because multiple definitions exists for the
generic extension .inc. After selecting "Bitbake" it was highlighted 
properly.


I'm really impressed - that's how I expect software to work.

Keep up this high quality.

Best regards,
André

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

Re: [Qt-creator] CONFIG variables not as expected

[André Hartmann]

Hi again Bob,

> Anyway, my remaining question is whether there is a straightforward
> way to detect in the .pro file which Microsoft compiler is being used?
> It used to be easy.

So you are saying, there is a regression in Qt 5.14 and you cannot 
detect the MSVC compiler anymore? Then please report that with a minimal 
reproducing example at bugreports.qt.io (and provide a link here so 
others can follow).


Thanks and regards,
André

Am 02.01.20 um 09:01 schrieb Bob Babcock:

=?UTF-8?Q?Andr=c3=a9_Hartmann?=  wrote in
news:c499ad3a-900e-da5a-aec4-19768014a...@iseg-hv.de:


In your first mail you talked about MinGW, now MSVC, so I still don't
get the full picture of your problem. You will need to provide some
more information.


I build with both, but don't mix them.  The MinGW part of my questions was
answered by your previous post.  I'm mostly a windows guy, but I have
written code that works in both Windows and Linux.


For C++ libraries, that's correct, you cannot mix MinGW and MSVC. For
libraries with pure C interface, it does not matter.
Note that MSVC2015 and 2017 are binary compatible, so you can exchange
libs.


I guess I knew that, but somehow it just feels wrong.  From a quick search,
looks like 2019, which I haven't touched yet, is also binary compatible.
Are they also compatible when you consider compilation flags, new C++
feature support, and bugs to work around? Those are some reasons why you
might want to detect which MSVC compiler is being used.

Anyway, my remaining question is whether there is a straightforward way to
detect in the .pro file which Microsoft compiler is being used?  It used to
be easy.

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

Re: [Qt-creator] CONFIG variables not as expected

[André Hartmann]

Hi Bob,


but detecting the compiler version is more awkward.

Why?


I can do
win32-msvc2015 { Do stuff... }
but not
win32-msvc2017 { Do stuff... }

The only way I see to tell that it's 2017 is to check if it isn't any other
MS compiler that I use.  Perhaps it's silly, but I try to maintain
compatibility with 2013, 2015 and 2017 and Qt back to 5.9x.


In your first mail you talked about MinGW, now MSVC, so I still don't 
get the full picture of your problem. You will need to provide some more 
information.



I use some 3rd party libraries that are built separately and it seems
safest to use libraries built with a matching compiler. 


For C++ libraries, that's correct, you cannot mix MinGW and MSVC. For 
libraries with pure C interface, it does not matter.


Note that MSVC2015 and 2017 are binary compatible, so you can exchange libs.

Regards, André


Less important, I include compiler version in my About screen and use > DEFINES 
to get that info into the code.



___
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] CONFIG variables not as expected

[André Hartmann]

Hi Bob,


I'm using Qt 5.14.0 and the bundled Creator 4.11.0 under Windows 7.
In a new or previously existing project using qmake, I display the contents
of CONFIG by message($$CONFIG) in the .pro file.

For a msvc3015 project, I see win32-msvc2015 in the list values.

For a msvc2017 project, I do not see win32-msvc2017 or anything similar.

For a gcc project, I do not see debug_and_release like I do with msvc
projects.


That's probably the outcome from QTBUG-78445, which resulted in QTBUG-80792

There is work ongoing to *allow* separate Qt debug builds again, but the
official release will (most likely) only contain release DLLs with
separate debug information.

> I can add CONFIG *= debug_and_release so I get debug and release build
> subdirectories

I'm actually doing the other way round, as I'm always shadow-building,
so the additional only complicate things.

> but detecting the compiler version is more awkward.

Why?

Best regards,
André

https://bugreports.qt.io/browse/QTBUG-78445
https://bugreports.qt.io/browse/QTBUG-80792




___
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

[André Hartmann]

Thanks a lot, Eike!

Regards, André

On 24.10.19 12:32, Eike Ziller wrote:

FYI
the SerialTerminal plugin is now part of the binary snapshots.

Br, Eike


On 14. Oct 2019, at 20:50, André Hartmann  wrote:

Hi Jason,


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?

That's the reason I wrote the mail. The plugin is integrated into
Creators source repository [1], but not build with the official packages.

You have two options for now:

1. Build Creator yourself
2. Find someone the builds Creator for you (e.g. a Linux distri)

Best regards,
André

[1]
https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/serialterminal


On 14.10.19 15:35, Jason H wrote:




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




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

Re: [Qt-creator] Deployment of SerialTerminal plugin

[André Hartmann]

On 15.10.19 19:00, André Pönitz wrote:

On Tue, Oct 15, 2019 at 09:03:40AM +0200, Richard Weickelt wrote:

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?


Some description of what it does and how, a.k.a. "Basic documentation"
would be nice.


I've started to write some lines here:
https://codereview.qt-project.org/c/qt-creator/qt-creator/+/277700

Still WIP but feel free to add you comments and ideas.


For bonus points, something that resembles a test. Even a purely manual
one in the form of "Open X;  Click Y; Type Z  - Expected result: ABC"


That is mostly for the developer ensuring the plugin still works as
expected, right?

André


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

Re: [Qt-creator] Deployment of SerialTerminal plugin

[André Hartmann]

Hi Jason,

> 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?

That's the reason I wrote the mail. The plugin is integrated into
Creators source repository [1], but not build with the official packages.

You have two options for now:

1. Build Creator yourself
2. Find someone the builds Creator for you (e.g. a Linux distri)

Best regards,
André

[1]
https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/serialterminal


On 14.10.19 15:35, Jason H wrote:




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] Deployment of SerialTerminal plugin

[André Hartmann]

Hi Leena,

> It is indeed really hard to find. As a first step, you could add it to
> the wiki page that lists Qt Creator plugins:
>
> https://wiki.qt.io/Qt_Creator_Plug-in_Gallery

Done: https://wiki.qt.io/Qt_Creator_Plug-in_Gallery#Serial_Terminal

Regards, André


Am 14.10.19 um 09:54 schrieb Riitta-Leena Miettinen:

Hello,

It is indeed really hard to find. As a first step, you could add it to 
the wiki page that lists Qt Creator plugins:


https://wiki.qt.io/Qt_Creator_Plug-in_Gallery

I should probably link to the page from somewhere in the Qt Creator Manual.

Cheers,

Leena

Leena Miettinen

Sr. Documentation Engineer

The Qt Company GmbH

Erich-Thilo-Str. 10

D-12489 Berlin

riitta-leena.mietti...@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


*From: *André Pönitz <mailto:apoen...@t-online.de>
*Sent: *Monday, October 14, 2019 5:06 AM
*To: *André Hartmann <mailto:aha_1...@gmx.de>
*Cc: *qt-creator <mailto:qt-creator@qt-project.org>
*Subject: *Re: [Qt-creator] Deployment of SerialTerminal plugin

On Sun, Oct 13, 2019 at 08:59:09PM +0200, André Hartmann wrote:
 > 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.

A lot of potential users might also not know what it could do.

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] Deployment of SerialTerminal plugin

[André Hartmann]

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.

Best Regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] ?==?utf-8?q? Setup of CMake based projects

[André Hartmann]

Hi all,

Sorry for hijacking this thread, but I instantly created a suggestion
[1] that tangents this topic.

Not only with CMake, also with other build systems there are often
several steps needed after checking out a project and before working on it.

I remember Tobias mentioned the wish to create a wizard for such setup
tasks a long time ago, but I didn't find a Jira task, therefore I
created one.

Please feel free to join the discussion there.

Regards,
André

[1] https://bugreports.qt.io/browse/QTCREATORBUG-23041

On 04.10.19 11:31, Cornelis Bockemühl wrote:

Dear Tobias,

 >The CMake version is great, it already has fileapi! Unfortunately your
 >Creator is too old to make use of it.
 >
 >For the CMake version you use, the 4.11 snapshots will work best. You
 >can find binaries over at
 >https://download.qt.io/snapshots/qtcreator/4.11/ , so no need to build
 >this yourself.
 >
 >You really want fileapi, that is way more stable than server-mode,
 >especially when you run of and just run cmake yourself while creator
 >is running. CMake does not like that at all:-)

Regarding the versions, I just see that I am living in a somehow "confused
state"! And of course the story on the Linux computer is different from
that on the Windows system.

Linux:

For quite some time I was working on OpenSuse Leap 42.3. Other than on
Windows, on many Linux systems there is an "official" Qt support on board,
and this was for me some QtCreator (I forgot the version), with Qt 5.6.2.
And it stayed like that as long as the version was there, while my project
urgently needed something more recent, at least Qt 5.9.

It gave me some grey hairs to finally install a completely independent
Qt development system, because there were initially some troubles because
it seems like the OpenSuse people had a special compilation of Qt and all,
with some kind of tags in the binaries that should guarantee that you
only use all the same "official version". Ok, Linux would not be Linux if
you could not change also that, but it took me some effort.

And with that I finally ended up with my "own system", with QtCreator 4.4
and Qt 5.9.2.

Now, a couple of months ago, I updated my OpenSuse system from 42.3 to
version 15.1 (funny numbering system, but who cares...). And now that you
are talking about versions, I am realizing that with my "own system" I am
actually now behind the "official" OpenSuse versions, which are QtCreator
version 4.8.2 and Qt 5.9.7.

But what I am going to do now is simply "stay detached" - once I am there
already! So at the moment I am indeed downloading a very fresh 4.11.beta
release from 1 Oct. I assume that I can install it simply next to the
existing installation, so nothing that I can lose if something really
goes wrong - I assume! Download is running - will take some time on my
rather slow connection here, but that's not a problem...

(Only I think I should take care of my *.user files when testing a brand
new beta of QtCreator - if ever I consider to possibly switch back to
"good old safe terrain"! But I already know that QtCreator does not simply
"kill" it in case it rejects an existing version...)

Windows:

Here things are "easier" in the way that Windows does absolutely nothing
on it's own on that system but you have plenty of other trouble - like
the different "build tool versions" - and it gave me another set of grey
hairs finally finding out what is what - and that it is absolutely
essential to have compatible versions there! And in this case the numbering
is far more weird than the logic of OpenSuse - it is just totally mad.
But what I know now is that my versioning status on Windows is

msvc2015 == version 14.00 == toolset 140 == compiler version 1900

Which looks for me like I could also install that latest QtCreator on
the windows system, because from the naming of the binary I conclude
that you also compiled with toolset 140 (and moving to another one is
a major operation - from tools and tool sets to all the projects...)

On the Windows system, my current "state of the art" is QtCreator 4.9.0,
with also Qt 5.9.2. Basically I mostly cared about the Qt version for
my projects, and with the creator I updated from time to time if the tool
told me that there is something new - but this only happens on Windows.

 >> >Where are those (relative to the source directory)?
 >>
 >> They are separate folders, like parallel to the sources folder, and
 >> also debug and release are separate. It's for me the most sensible
 >> setup - and with ParaView I think it's not possible otherwise.
 >
 >Do they match the naming scheme creator has for those directories?

No, they don't! I considered that creator naming too complicated, so my
current directory trees are something like

project
- sources
- release
- debug
- docs
- ...

On the windows system I made it even shorter (like src, rel, deb...)
because still nowadays it happens that certain Windows tools are doing
crazy things if paths are getting long...

[...]

 >Creator 

Re: [Qt-creator] Class rename refactoring with file renaming problems.

[André Hartmann]

Hi Oleg,

I just did some tests with qmake based projects and did not encounter
any problems.

Can you please create a report at bugreports.qt.io and attach a
minimal CMake project so the problem can be reproduced.

Thanks, Andre

Am 26.04.19 um 21:01 schrieb Oleg Shal:

Oh. Sorry Andre.
1) My system is Linux 5.0.0-13-generic #14-Ubuntu SMP
2) cmake project. Project files are situated in special Build directory.
[image: image.png]
3) I used renaming tool on this project with some namespaces some weeks ago
with no problems.
4) I created super simple test with one Application class and no
namespaces. The same situation.
Only one file was suggested for renaming.
[image: image.png]

пт, 26 апр. 2019 г. в 21:06, Andre Hartmann :


Hi Oleg,

that feature is included in Creator for some time (I think since 4.6). I'm
so far not aware of a regression, therefore:

Can you provide more information about your project?

* you are working on Linux, right?
* which project manager (qmake, CMake, QBS) is it?
* the path to your file and the namespace looks very long, can you check a
file with shorter path?

Best would be to create a report at bugreports.qt.io, preferred with a
minimal project that shows the problem.

Thanks and regards,
Andre

Am Freitag, 26. April 2019 schrieb Oleg Shal:

Good Day!

In 4.9 rc very good feature was introduced. Class renaming with file
renaming.
This feature working good in rc.
In release it's seems like an error. Only one file is suggested for
renaming.

Thank's a lot!

[image: image.png]

--
Oleg Shal  (AriSha Integration Initiative)
--
e-mail  : oleg@ arisha.online ,
oleg.shal...@gmail.com
cell,Viber,WhatsUp,Telegram : +7 (918) 741 7217



--
Von meinem Jolla gesendet
___
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] 4.9 beta "close project" feature

[André Hartmann]

Hi Ekke,


no - I have not tried Git integration in Creator yet
I like it to manage all my projects independent from IDE in one external
Tool: Git Tower app on macOS:


Ok - fair enough.


  * QtCreator projects for Android / iOS on macOS
  * QtCreator projects for Windows10 in Parallels VM on macOS with
shared project folders
  * Momentics (Eclipse) projects for BlackBerry 10 (yes: still some
updates and support, even new projects)
  * Eclipse projects for my XText/XTend DSL projects generating C++ Code
from DSL models into my QtC projects sources


Hmm, that looks like a very special way to do cross-platform ;)


Also I really like Git Tower Application on macOS


Yeah, I understand that. My question is: what can be improved in
Creator, i.e. which features are better implemented in other apps.
If someone else has the comparison, please write me :)

Regards,
André


Am 20.03.19 um 18:11 schrieb André Hartmann:

Hi Ekke,


(BTW: I have disabled all version control plugins and doing all the
git > stuff outside QtC with Tower app)

Out of personal interest, have you tried the Git integration in Creator
(recently)? There are a lot of things that conceptually work much better
than an external tool - annotate the current file, jump from a diff to
the source code, commit from within the editor... I rarely use external
tools. Even Interactive Rebase is integrated.

So my question is: What is missing in Creators Git integration?

Thanks and regards,
André

ekke


Am 20.03.19 um 16:36 schrieb mapron:

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!

- If I try to rebase without closing project, QtC just hangs.

I know it is maybe another bug, but still, I have a bunch of scenarios
when it is totally undesirable.

- open project, leave it CMakeLists.txt for split view, open another
one, close other projects (just imagine you have in memory 5 large
projects!), but use some files from them.

You could say "you could open CMakeLists.txt as usual file" , I say "I
also could use some files fo split view, which located deeply in tree;
I want to quickly add them to locator (godlike feature!), and then use
in splits in other project..."

summary: Developers! Leave my files alone! It's IDE, it amed to edit
files. Give them for me back please :)

p.s. maybe option for this behavior?


___
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] 4.9 beta "close project" feature

[André Hartmann]

Hi Ekke,


(BTW: I have disabled all version control plugins and doing all the git > stuff 
outside QtC with Tower app)

Out of personal interest, have you tried the Git integration in Creator
(recently)? There are a lot of things that conceptually work much better
than an external tool - annotate the current file, jump from a diff to
the source code, commit from within the editor... I rarely use external
tools. Even Interactive Rebase is integrated.

So my question is: What is missing in Creators Git integration?

Thanks and regards,
André

ekke


Am 20.03.19 um 16:36 schrieb mapron:

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!

- If I try to rebase without closing project, QtC just hangs.

I know it is maybe another bug, but still, I have a bunch of scenarios
when it is totally undesirable.

- open project, leave it CMakeLists.txt for split view, open another
one, close other projects (just imagine you have in memory 5 large
projects!), but use some files from them.

You could say "you could open CMakeLists.txt as usual file" , I say "I
also could use some files fo split view, which located deeply in tree;
I want to quickly add them to locator (godlike feature!), and then use
in splits in other project..."

summary: Developers! Leave my files alone! It's IDE, it amed to edit
files. Give them for me back please :)

p.s. maybe option for this behavior?


___
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] 4.9 beta "close project" feature

[André Hartmann]

Hi mapron,

> https://bugreports.qt.io/browse/QTCREATORBUG-15721
> Why anyone decided it is a good change?  I don't want to close all my
> files.

Well, it was a request and some people think it is a good idea to do so.
Some disagree - like you. So please create a new suggestion (and post a
link to that here), so BOTH work flows are possible.

> p.s. maybe option for this behavior?

I think there should just be two menu entries. So you can choose every
time. An option is to static.

> - 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!
>
> - If I try to rebase without closing project, QtC just hangs.

I do use the Interactive Rebase within QtCreator VERY often. I sometimes
have problems on Windows, when an open file cannot be overwritten by the
rebase. Otherwise it works quite well.

Can you create a bugreport for this problem too and link it here?

Regards,
André

Am 20.03.19 um 16:36 schrieb mapron:

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!

- If I try to rebase without closing project, QtC just hangs.

I know it is maybe another bug, but still, I have a bunch of scenarios
when it is totally undesirable.

- open project, leave it CMakeLists.txt for split view, open another
one, close other projects (just imagine you have in memory 5 large
projects!), but use some files from them.

You could say "you could open CMakeLists.txt as usual file" , I say "I
also could use some files fo split view, which located deeply in tree; I
want to quickly add them to locator (godlike feature!), and then use in
splits in other project..."

summary: Developers! Leave my files alone! It's IDE, it amed to edit
files. Give them for me back please :)

p.s. maybe option for this behavior?


___
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] Coding style for lambdas with empty parameter list

[André Hartmann]

Hi all,

I recently found an inconsistency regarding empty lambda parameter lists
between [1] and [2]. While the first states, that parentheses have to be
written always, the latter is missing this section.

My request to syncronize both [3] lead to the conclusion, to change the rule,
so that empty parameter lists should be written as

 [] { // lambda content }

instead

 []() { // lambda content }

If anyone has objections against this change, please vote at [3]. 
I'll keep this commit open a while and adopt the Wiki [1] once the change
is approved without objections.

Thanks and regards,
André

[1] https://wiki.qt.io/Coding_Conventions#Lambdas
[2] https://code.woboq.org/qt5/qt-creator/doc/api/coding-style.qdoc.html#772
[3] https://codereview.qt-project.org/249192
___
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Re: [Qt-creator] Qt creator + Clang model = major annoyance

[André Hartmann]

Hi,

 

first, Happy New Year to all, and thanks for the great work you all did the last
decade to improve the IDE we all love most.

 

I like to add my story: When I started working with QtCreator 9 years ago, I was
mostly impressed by the fluent editor. It was a joy working with that, the code
just streamed out of my fingers. I did not have to think if there is already a
closing brace, I just typed ')' and it always worked as expected. Unfortunately,
over time the editor experience degraded, for example the following bugs:

 

* QTCREATORBUG-16946
* QTCREATORBUG-18872
* QTCREATORBUG-21767

 

One more important point for the CCM is completion of Qt connect statements. It
does not work anymore for the old-style connects (QTCREATORBUG-20737), which is
a pain maintaining old code bases, but I _could_ live with it.

 

Even worse is, that completing new-style connects has open issues too:

 

* QTCREATORBUG-13558
* QTCREATORBUG-20840

 

Why do I write this: Well, for me the editor is the most important part of the IDE.
It should not get in my way. Slow code completions, missing navigation, missing
online help really slow me down and are therefore frustrating.

 

I really like the idea of founding money for additional core team members. There
are enough open issues that could be worked on.

 

Don't get me wrong: The overall quality is good, there are just the rough corners
that need to be polished. And I really hope to still use Creator in 10 years,
with the same joy I started with.

 

Thanks for reading, and a successful 2019 to everyone.

 

André

 

Gesendet: Sonntag, 06. Januar 2019 um 18:55 Uhr
Von: "Michael Jackson" 
An: "NIkolai Marchenko" , qt-creator 
Betreff: Re: [Qt-creator] Qt creator + Clang model = major annoyance




On some points I agree, but being on macOS my choices are pretty limited for an IDE. xCode? Uh no. Eclipse? No way. What else is there? QtCreator is pretty much the only choice I have. I am hoping that the QtCreator team can carve out some time in 2019 to look into some of the speed issues with the clang backend.


Frankly my issue with the old parser was _because_ of boost. The original code model would _never_ want to parse our use of boost which made code completions pretty non-existent in our boost heavy code. When the CCM successfully parses the file the complete is spot on, it just takes forever to parse the code. One thing that I have noticed is that if I turn off all the clang-tidy and clazy checks then the speed on first opening is pretty decent (I’m on a 2012 Mac Pro with dual Xeon so not the fastest CPUs in the world). If I turn on the clang-tidy checks that I want then the time to get even the function list is abysmal. I would think a 2 stage parse of the file might work better with 2 threads: 1 for the initial parser and one for the clang-tidy checks. Waiting 30 seconds (or sometimes never) for a function list to appear seems like a deficiency in my mind.

 

Again, I really appreciate how far QtCreator has come from the “old days” in the 2.x versions. I have used it through the 1.5 years of “dark ages” where debugging on macOS was basically non-existent due to LLDB being so immature. QtCreator works way better with our CMake heavy projects and all of the external libraries that we used. I think it just needs some polish on the CCM parsing and reaction times put into it in 2019.

 

--

Michael Jackson | Owner, President

  BlueQuartz Software

[e] mike.jack...@bluequartz.net

[w] www.bluequartz.net 

 

 



On 1/4/19, 8:20 PM, "Qt-creator on behalf of NIkolai Marchenko"  wrote:




 




Qt creator is rapidly becoming a source of major annoyance ever since clang code model was introduced.



 



It's slow, sometimes taking 30+ seconds to react to F2



What's worse, it reacts to it once you gave up and navigated somewhere manually and makes you suddenly type stuff in plces you won't expect.



 



It's buggy, fails on boost and fails to produce a highlight on everything that depends on it



 



It's too easy to break, A single symbol it doesn't detect breaks highlighting and hint for the whole file chain, whether stuff later down the line requires that symbol or not.



 



While I understand the desire to stop reimplementing the wheel with code parser, the Clang Code Model made Qt Creator strictly worse for any complex project to the point I catch myself wanting to use something else on a regular basis. This wasn't the case ever before CCM was introduced.



___ 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

Re: [Qt-creator] Quick test or scratch-pad mode in qtc?

[André Hartmann]

Hi Alexis,

> I was wondering if this would be totally stupid to have a mode in QTC
> were we could code in a single source with no Build System setup?
[...]
> is so convenient to just start writing code without any setup.

Sounds good.

> But this has many drawbacks like, no or almost no completion, no debug
> and needs internet.

So may I ask what your goal is? Is it:

* Proof that your code compiles?
* Run a small (console) application?
* Look at the generated assembly output?

In principle, one could think of a "scratch" wizard, that

* Creates a project with a unique name like
  "QTC-Scatch-2018-12-22-17-08"
* Uses qmake as build system
* Uses the default "desktop" kit with it's Qt version
  and compiler
* Adds a main.cpp and opens it in the editor

You could than choose other compilers through the usual Projects mode,
build, run and debug your project. Other compiler options could be set 
in the Project .pro file.


That would reduce the setup to two or three clicks and looks simple 
enough to be integrated without big effort.


What do you think?

Best regards,
André


Am 22.12.18 um 12:12 schrieb Jeandet Alexis:

Hello,

I was wondering if this would be totally stupid to have a mode in QTC
were we could code in a single source with no Build System setup?
I always go to websites like coliru, godbolt, wandbox,... to do some
tests(test concepts, see if I can template something,...) because this
is so convenient to just start writing code without any setup. But this
has many drawbacks like, no or almost no completion, no debug and needs
internet.

In QTC I would easily see a section in welcome page "scratch-pad" with
previous ones and a button to create a new one. I don't think we should
care about file location or any setup, source files could be stored in
QTC user data folder. Maybe we could just switch among available
compilers and set manually compile args like godbolt.

Am I the only one who miss this feature?
If no I will definitely open a BR.

Best regards and happy holidays,
Alexis.


___
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] Changing the default editor for a MIME type

[André Hartmann]

> If you add *.dts as a pattern to the text/plain mime type, I’d expect 
them to be opened in the plain text editor instead.


Thanks Eike, that worked! :)





On Nov 27, 2018, at 08:10, André Hartmann  wrote:

I'm a step further:

I deleted the pattern *.dts from audio/vnd.dts, and after a restart it opens 
the files in a text editor, but with Clang annotations.

So it seems, Creator uses a C++ editor to edit the file. A "normal" text editor 
would have been enough.


If you add *.dts as a pattern to the text/plain mime type, I’d expect them to 
be opened in the plain text editor instead.

Br, Eike


Anyway, I can edit my files now.

Regards,
André


Hello,
I'd like to edit some Linux Kernel Device Tree files (*.dts) in QtCreator.
Unfortunately this extension is mapped to audio/dts and has Binary Editor as 
handler.
It seems there is no way to change that assignment - what am I missing?
Regards,
André


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




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

Re: [Qt-creator] Changing the default editor for a MIME type

[André Hartmann]

I'm a step further:

I deleted the pattern *.dts from audio/vnd.dts, and after a restart it 
opens the files in a text editor, but with Clang annotations.


So it seems, Creator uses a C++ editor to edit the file. A "normal" text 
editor would have been enough.


Anyway, I can edit my files now.

Regards,
André


Hello,

I'd like to edit some Linux Kernel Device Tree files (*.dts) in QtCreator.

Unfortunately this extension is mapped to audio/dts and has Binary 
Editor as handler.


It seems there is no way to change that assignment - what am I missing?

Regards,
André


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

[Qt-creator] Changing the default editor for a MIME type

[André Hartmann]

Hello,

I'd like to edit some Linux Kernel Device Tree files (*.dts) in QtCreator.

Unfortunately this extension is mapped to audio/dts and has Binary 
Editor as handler.


It seems there is no way to change that assignment - what am I missing?

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

Re: [Qt-creator] Snapshot builds for 4.8

[André Hartmann]

Hi Eike,

sorry to bother again, but the Windows snapshot seems to stuck at 
October 23, even if the download page [1] claims the last snapshot has 
been build on October 27.


Can you please have a look at this issue? Thanks!

[1] https://download.qt.io/snapshots/qtcreator/4.8/4.8.0-beta2/2573

Am 23.10.18 um 16:55 schrieb André Hartmann:

Thanks Eike!

Am 23.10.18 um 16:45 schrieb Eike Ziller:
I’ve got cloned a job to do Qt 5.11 based snapshots until we got it 
figured out

https://download.qt.io/snapshots/qtcreator/4.8/4.8.0-beta2/

On Oct 23, 2018, at 08:35, André Hartmann  
wrote:


Hi Eike,

To build with Qt 5.12 we needed to update our macOS machines, but 
unfortunately the new macOS 10.13 setups act up in our build 
infrastructure…


But could we at least have snapshots for Windows and Linux?

Or stay with 5.11 as long as there is no final solution for 5.12?

We have nearly two weeks since the last snapshot and I'd like to test 
the changes since them in production...


Thanks,
André

Am 23.10.18 um 07:37 schrieb Eike Ziller:
On Oct 22, 2018, at 17:44, Michael Jackson 
 wrote:


Has there been any movement on this issue? I like to test out the 
latest builds for performance issues. The 4.8 Beta is working 
pretty good on my system (2012 Mac Pro, macOS 10.13) but I need to 
throw our really large project at it. Thanks for the great work on 
this product.

Movement yes, success no.
To build with Qt 5.12 we needed to update our macOS machines, but 
unfortunately the new macOS 10.13 setups act up in our build 
infrastructure…

Br, Eike

--
Michael Jackson | Owner, President
  BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net <http://www.bluequartz.net>

On 10/18/18, 2:37 AM, "Qt-creator on behalf of Eike Ziller" 
behalf of eike.zil...@qt.io> wrote:





On 17. Oct 2018, at 23:04, Orgad Shaneh  wrote:

Hi,

I've just noticed that there are no snapshot builds for the past 
week (and there is no beta2 directory). Is this intentional?


    No, I’ve been fighting a bit with upgrading them to Qt 5.12, 
but I hope to have them up again soon.




http://download.qt.io/snapshots/qtcreator/4.8/

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


    --
    Eike Ziller
    Principal Software Engineer

    The Qt Company GmbH
    Rudower Chaussee 13
    D-12489 Berlin
    eike.zil...@qt.io
    http://qt.io
    Geschäftsführer: Mika Pälsi,
    Juha Varelius, Mika Harjuaho
    Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht 
Charlottenburg, HRB 144331 B


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



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





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail.
Any unauthorized 

Re: [Qt-creator] Snapshot builds for 4.8

[André Hartmann]

Thanks Eike!

Am 23.10.18 um 16:45 schrieb Eike Ziller:

I’ve got cloned a job to do Qt 5.11 based snapshots until we got it figured out
https://download.qt.io/snapshots/qtcreator/4.8/4.8.0-beta2/


On Oct 23, 2018, at 08:35, André Hartmann  wrote:

Hi Eike,


To build with Qt 5.12 we needed to update our macOS machines, but unfortunately 
the new macOS 10.13 setups act up in our build infrastructure…


But could we at least have snapshots for Windows and Linux?

Or stay with 5.11 as long as there is no final solution for 5.12?

We have nearly two weeks since the last snapshot and I'd like to test the 
changes since them in production...

Thanks,
André

Am 23.10.18 um 07:37 schrieb Eike Ziller:

On Oct 22, 2018, at 17:44, Michael Jackson  wrote:

Has there been any movement on this issue? I like to test out the latest builds 
for performance issues. The 4.8 Beta is working pretty good on my system (2012 
Mac Pro, macOS 10.13) but I need to throw our really large project at it. 
Thanks for the great work on this product.

Movement yes, success no.
To build with Qt 5.12 we needed to update our macOS machines, but unfortunately 
the new macOS 10.13 setups act up in our build infrastructure…
Br, Eike

--
Michael Jackson | Owner, President
  BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net <http://www.bluequartz.net>

On 10/18/18, 2:37 AM, "Qt-creator on behalf of Eike Ziller" 
 wrote:




On 17. Oct 2018, at 23:04, Orgad Shaneh  wrote:

Hi,

I've just noticed that there are no snapshot builds for the past week (and 
there is no beta2 directory). Is this intentional?


No, I’ve been fighting a bit with upgrading them to Qt 5.12, but I hope to 
have them up again soon.



http://download.qt.io/snapshots/qtcreator/4.8/

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


--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
HRB 144331 B

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



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



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

Re: [Qt-creator] Snapshot builds for 4.8

[André Hartmann]

Hi Eike,

> To build with Qt 5.12 we needed to update our macOS machines, but 
unfortunately the new macOS 10.13 setups act up in our build infrastructure…


But could we at least have snapshots for Windows and Linux?

Or stay with 5.11 as long as there is no final solution for 5.12?

We have nearly two weeks since the last snapshot and I'd like to test 
the changes since them in production...


Thanks,
André

Am 23.10.18 um 07:37 schrieb Eike Ziller:



On Oct 22, 2018, at 17:44, Michael Jackson  wrote:

Has there been any movement on this issue? I like to test out the latest builds 
for performance issues. The 4.8 Beta is working pretty good on my system (2012 
Mac Pro, macOS 10.13) but I need to throw our really large project at it. 
Thanks for the great work on this product.


Movement yes, success no.
To build with Qt 5.12 we needed to update our macOS machines, but unfortunately 
the new macOS 10.13 setups act up in our build infrastructure…

Br, Eike


--
Michael Jackson | Owner, President
  BlueQuartz Software
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net 

On 10/18/18, 2:37 AM, "Qt-creator on behalf of Eike Ziller" 
 wrote:




On 17. Oct 2018, at 23:04, Orgad Shaneh  wrote:

Hi,

I've just noticed that there are no snapshot builds for the past week (and 
there is no beta2 directory). Is this intentional?


No, I’ve been fighting a bit with upgrading them to Qt 5.12, but I hope to 
have them up again soon.



http://download.qt.io/snapshots/qtcreator/4.8/

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


--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, 
HRB 144331 B

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



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



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

Re: [Qt-creator] Branches side-panel

[André Hartmann]

Hi all,

as there has been no further comment so far, I'll ask in a more direct way:

Is it Ok to completely replace the Git Branches dialog with a Git 
Branches side panel?


Regards,
André

Am 07.07.2018 um 13:45 schrieb André Hartmann:

Hi all,

first apologize for breaking the thread, I only had a "digest mail 
account" till now.


Thanks Orgad for bringing this topic up. I hoped it would raise more 
interest though...


For my motivation: I dislike the Git branches dialog, as it always gets 
in the way. Usually, when working with branches you need to see diffs or 
resolve conflicts, so you need the editor windows too. As we now have 
the left and right side panel, I thought it would be a good idea to move 
this dialog to these panels.


The branches window itself is very useful as it allows *a lot* of Git 
operations to be done, so I think having it visible always is a good 
option. I'd move it to the right side panel, so it disappers while 
debugging (you don't need it during debugging).


I don't use the programs mentioned by Michael, but I think we get a lot 
closes to them with this panel.


The only questions that arises now is: Should it already get a wider 
scope, i.e. should it not only contain the branches window but also the 
changed files list, a "fast commit" window, etc.?


What do you think?

One more note: The side panels are a bit more mouse-centric, as many 
options are in context menus. That is no big problem for me (and I'm 
already using the keyboard very much!), but may hurt others. Any opinion 
on this?


A compromise would even be, if the side panels could be un-docked and 
docked again. But I think we don't have the needed infrastructure for now.


Thanks for reading this long mail. I'm awaiting your opinions :)

Regards,
André

Am 05.07.2018 um 07:58 schrieb qt-creator-requ...@qt-project.org:

Send Qt-creator mailing list submissions to
qt-creator@qt-project.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.qt-project.org/mailman/listinfo/qt-creator
or, via email, send a message with subject or body 'help' to
qt-creator-requ...@qt-project.org

You can reach the person managing the list at
qt-creator-ow...@qt-project.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Qt-creator digest..."


Today's Topics:

    1. Re: Branches side-panel (Michael Jackson)
    2. Re: QtCreator 4.7 RC Feedback (Michael Jackson)
    3. Re: QtCreator 4.7 RC Feedback (Eike Ziller)


--

Message: 1
Date: Wed, 04 Jul 2018 22:17:39 -0400
From: Michael Jackson 
To: 
Subject: Re: [Qt-creator] Branches side-panel
Message-ID: 
Content-Type: text/plain;    charset="UTF-8"

I would love to see a "workspace" that basically 
incorporates the functionality of something like SourceTree or 
GitKraken into QtCreator. I don't actually know what 
QtCreator has to offer by way of Git functionality because those 2 
applications are that good.


--
Mike Jackson

?On 7/4/18, 9:10 AM, "Qt-creator on behalf of Mathias Hasselmann" 
behalf of math...@taschenorakel.de> wrote:


 Hi Orgad,
 I'd totally love to see (much) better git integration in 
QtCreator and
 replacing the branches dialog would with a panel be a great start 
for a
 more natural git experience in QtCreator. I'd really love to see 
such

 change!
 Thanks,
 Mathias
 Am 02.07.2018 um 19:49 schrieb Orgad Shaneh:
 > Hi,
 >
 > There is a pending change
 > <https://codereview.qt-project.org/217408> by Andr? Hartmann that
 > introduces a Branches side-panel for Git.
 >
 > The current dialog is not modal, which I find a bit confusing, 
and it
 > has many buttons with dynamic enable/disable state. It also 
hides the

 > main window when open.
 >
 > Before we proceed with it, I'd like to hear your opinions:
 >
 >   * Do you like it as a panel?
 >   * Do you prefer the panel or the current dialog?
 >   * How about removing the dialog and replacing it by the panel?
 >
 > Thanks,
 > - Orgad
 >
 >
 > ___
 > Qt-creator mailing list
 > Qt-creator@qt-project.org
 > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator




--

Message: 2
Date: Wed, 04 Jul 2018 22:32:40 -0400
From: Michael Jackson 
To: "qt-creator@qt-project.org" 
Subject: Re: [Qt-creator] QtCreator 4.7 RC Feedback
Message-ID: <49133341-7a34-45b1-8af3-ad9cea9e9...@bluequartz.net>
Content-Type: text/plain; charset="

Re: [Qt-creator] Proposal: Increase requirements for compiling Qt Creator to GCC>=5.3

[André Hartmann]

Hi Davide,

> Wasn't gcc 5.3 already used to build Qt Creator?

That may have been the case for the precompiled version already,
but you *could* compile Creator yourself with older gcc versions.

The current change is about *requiring* gcc 5.3.

Regards,
André

Am 19.07.2018 um 01:35 schrieb Davide Coppola:

Wasn't gcc 5.3 already used to build Qt Creator?

At least that's what I see checking the help of 4.7 and 4.6.x.

On Tue, 17 Jul 2018 at 09:59, Eike Ziller <mailto:eike.zil...@qt.io>> wrote:


1 1/2 years ago we started requiring GCC 4.9 or later for compiling
Qt Creator.

This compiler was first released over 4 years ago and even in its
newest incarnation is almost 2 years old, so it is time to move on.
As far as my research (e.g. https://distrowatch.com) tells me, all
major Linux distributions provide at least GCC 5.3 in their
stable/LTS version (CentOS/RHEL only through the devtoolset package,
but they didn’t provide 4.9 directly either).

So I propose requiring GCC 5.3, starting with Qt Creator 4.8 (which
currently is branch ‘master').

Br, Eike

-- 
Eike Ziller

Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io <mailto: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 <mailto:Qt-creator@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/qt-creator



--
*Davide Coppola*

*website:*http://www.davidecoppola.com
*blog:*http://blog.davidecoppola.com

<http://plus.google.com/+DavideCoppola> 
<http://www.linkedin.com/in/davidecoppola> 
<http://www.twitter.com/vivaladav>



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




--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden.

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

Re: [Qt-creator] What's the crash?

[André Hartmann]

Hi Jason,


There's nothing more the debugger or C++ can do for you here.

My comment refered to something like this in your code:

QList data;
data[0] = 123;

That will crash in qlist.cpp with index out of range, and not in your 
code. Therefore it is not immediately obvious what causes the crash. But 
with the stack trace you can find the guilty function.


It's up to you to inspect the stack though. If global variables are 
involved, things might get more complicated.


> MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png

> I thought earlier versions of QtC had something simular.

Are you working with a debug version of your program?

Regards,
André


But it does at the command line:
Process 79112 launched: '/Users/jhihn/Projects/test_crash/a.out' (x86_64)
Process 79112 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_ARITHMETIC 
(code=EXC_I386_DIV, subcode=0x0)
 frame #0: 0x00010fad a.out`main at main.c:7
4   {
5   int a = 2;
6   int b = 0;
-> 7 return a/b;


I'm pretty sure I remember some dialog appearing saying something about SIGSEGV 
(or in this case EXC_ARITHMETIC)?

MS gives this: 
https://user-images.githubusercontent.com/10531631/36583169-c65d48ea-1874-11e8-90db-1a651cfd09f5.png
I thought earlier versions of QtC had something simular.

The difference is:

int *a, *b; *b=0;
return *a / *b;

Here, the problem could be that 'a' is out of process space, or 'b' is 0. If 
'a' is a pointer, I don't necessarily know what my address range is. I have to 
deduce (and risk being wrong) what the actual crash was, meaning I could waste 
time going down the wrong path.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator



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

Re: [Qt-creator] Branches side-panel

[André Hartmann]

Hi all,

first apologize for breaking the thread, I only had a "digest mail 
account" till now.


Thanks Orgad for bringing this topic up. I hoped it would raise more 
interest though...


For my motivation: I dislike the Git branches dialog, as it always gets 
in the way. Usually, when working with branches you need to see diffs or 
resolve conflicts, so you need the editor windows too. As we now have 
the left and right side panel, I thought it would be a good idea to move 
this dialog to these panels.


The branches window itself is very useful as it allows *a lot* of Git 
operations to be done, so I think having it visible always is a good 
option. I'd move it to the right side panel, so it disappers while 
debugging (you don't need it during debugging).


I don't use the programs mentioned by Michael, but I think we get a lot 
closes to them with this panel.


The only questions that arises now is: Should it already get a wider 
scope, i.e. should it not only contain the branches window but also the 
changed files list, a "fast commit" window, etc.?


What do you think?

One more note: The side panels are a bit more mouse-centric, as many 
options are in context menus. That is no big problem for me (and I'm 
already using the keyboard very much!), but may hurt others. Any opinion 
on this?


A compromise would even be, if the side panels could be un-docked and 
docked again. But I think we don't have the needed infrastructure for now.


Thanks for reading this long mail. I'm awaiting your opinions :)

Regards,
André

Am 05.07.2018 um 07:58 schrieb qt-creator-requ...@qt-project.org:

Send Qt-creator mailing list submissions to
qt-creator@qt-project.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.qt-project.org/mailman/listinfo/qt-creator
or, via email, send a message with subject or body 'help' to
qt-creator-requ...@qt-project.org

You can reach the person managing the list at
qt-creator-ow...@qt-project.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Qt-creator digest..."


Today's Topics:

1. Re: Branches side-panel (Michael Jackson)
2. Re: QtCreator 4.7 RC Feedback (Michael Jackson)
3. Re: QtCreator 4.7 RC Feedback (Eike Ziller)


--

Message: 1
Date: Wed, 04 Jul 2018 22:17:39 -0400
From: Michael Jackson 
To: 
Subject: Re: [Qt-creator] Branches side-panel
Message-ID: 
Content-Type: text/plain;   charset="UTF-8"

I would love to see a "workspace" that basically incorporates the 
functionality of something like SourceTree or GitKraken into QtCreator. I don't 
actually know what QtCreator has to offer by way of Git functionality because those 2 applications 
are that good.

--
Mike Jackson

?On 7/4/18, 9:10 AM, "Qt-creator on behalf of Mathias Hasselmann" 
 wrote:

 Hi Orgad,
 
 I'd totally love to see (much) better git integration in QtCreator and

 replacing the branches dialog would with a panel be a great start for a
 more natural git experience in QtCreator. I'd really love to see such
 change!
 
 Thanks,

 Mathias
 
 Am 02.07.2018 um 19:49 schrieb Orgad Shaneh:

 > Hi,
 >
 > There is a pending change
 >  by Andr? Hartmann that
 > introduces a Branches side-panel for Git.
 >
 > The current dialog is not modal, which I find a bit confusing, and it
 > has many buttons with dynamic enable/disable state. It also hides the
 > main window when open.
 >
 > Before we proceed with it, I'd like to hear your opinions:
 >
 >   * Do you like it as a panel?
 >   * Do you prefer the panel or the current dialog?
 >   * How about removing the dialog and replacing it by the panel?
 >
 > Thanks,
 > - Orgad
 >
 >
 > ___
 > Qt-creator mailing list
 > Qt-creator@qt-project.org
 > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator
 





--

Message: 2
Date: Wed, 04 Jul 2018 22:32:40 -0400
From: Michael Jackson 
To: "qt-creator@qt-project.org" 
Subject: Re: [Qt-creator] QtCreator 4.7 RC Feedback
Message-ID: <49133341-7a34-45b1-8af3-ad9cea9e9...@bluequartz.net>
Content-Type: text/plain; charset="utf-8"

Ok, Good suggestion. I went back and for the QtC 4.6 test the Clang code model 
was turned off. So I went back and tried again. The Syntax highlighting took 
about 5 seconds for the particular file that I am using as my benchmark. More 
Importantly the drop down was populated with the methods of the class in about 
2 seconds which is reasonable. At least I can start navigating quickly. By the 

Re: [Qt-creator] [Development] Proposing Orgad Shaneh as Maintainer of Version Control modules in Qt Creator

[André Hartmann]

+1. Orgad is doing great work (everywhere in Creator, not only in the 
VCS intregration).


Disclaimer: I'm no maintainer.

Regards, André

Am 02.05.2018 um 13:03 schrieb Jaroslaw Kobus:

Of course +1


*From:* Development 
<development-bounces+jaroslaw.kobus=qt...@qt-project.org> on behalf of 
Tobias Hunger <tobias.hun...@qt.io>

*Sent:* Wednesday, May 2, 2018 12:14:14 PM
*To:* qt-creator@qt-project.org; developm...@qt-project.org
*Subject:* [Development] Proposing Orgad Shaneh as Maintainer of Version 
Control modules in Qt Creator

Hello,

I want to propose Orgad Shaneh as maintainer of the version control 
related modules in Qt Creator.


So far I have been handling that responsibility, but since I took over 
the project-related Qt Creator plugins, I had way too little time on my 
hands to take a lead in the version management related code.


Orgad has been working in those modules, he did a lion's share of the 
reviews involved and he added functionality during that time and he is 
willing to take on the responsibility involved. So I would like formally 
propose Orgad as maintainer of the version management code. I am sure he 
will take good care of the code, especially of the vcsbase and git plugins.


Best Regards,
Tobias

--
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B


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


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




--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden.

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

Re: [Qt-creator] Odd QtCreator hang

[André Hartmann]

Hi Sean,


I've got an odd hang with QtCreator when debugging my software.
Oh, as you are on Windows, that's the third platform that show 
clipboard-related strage effects.


We already have QTCREATORBUG-20262 and QTBUG-67729. Can you please check 
these?


Regards,
André

[1] https://bugreports.qt.io/browse/QTCREATORBUG-20262
[2] https://bugreports.qt.io/browse/QTBUG-67729



I've got the following function where I'm trying to copy the data out of a 
QTableView to the clipboard in a format that will allow the resulting data to 
be pasted directly into an Excel spreadsheet. Here's the function:
void plotContainerWidget::slotCopyTableToClipboard()
{
 // select everything in table copy it to text string with
 // '\t' separating columns and '\n' separating rows
 if(mModel == 0)
 {
 return;
 }

 int rows = mModel->rowCount();
 int cols = mModel->columnCount();

 QString tableString;
 for(int i=0; i < cols; ++i)
 {
 tableString += mModel->headerData(i, Qt::Horizontal).toString();
 tableString += "\t";
 }
 tableString.chop(1); // remove extraneous tab
 tableString += "\n";

 for(int i=0; i < rows; ++i)
 {
 for(int j=0; j < cols; ++j)
 {
 tableString += mModel->data(mModel->index(i, j), 
Qt::DisplayRole).toString();
 tableString += "\t";
 }
 tableString.chop(1); // remove extraneous tab
 tableString += "\n";
 }
 tableString.chop(1); // remove extraneous newline
 qDebug() << tableString;
 QClipboard* clippy = QApplication::clipboard();
 if (!clippy)
 {
 return;
 }
 clippy->setText(tableString); // *** QT CREATOR HANGS HERE ***
 qDebug() << "copied table to clipboard";
}

When I execute this chunk of code within the debugger, it hangs at that QClipboard::setText() line. 
I first encountered it executing my code within the debugger, but without any breakpoints set. 
During that session, Qt Creator hung, and I had to force quit. After re-launching QtCreator, I set 
a breakpoint in this function and stepped through my code. The parsing is fine up until that line, 
the string looks good, but then Qt Creator hangs when that line setText() is executed. So this 
issue seems to happen whether I have any breakpoints set or not and interestingly this code does 
NOT hang when I choose "Run" from within Qt Creator, only when I choose "Start 
Debugging", even though that should still be executing the debug build of my application, just 
not running inside the debugger.

Qt version 5.3.2 (yes, I know this is ancient...)
Qt Creator 4.5.2 (at least this isn't!)
Windows 7 64-bit

Any ideas?
Sean


This message has been scanned for malware by Forcepoint. www.forcepoint.com
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immedia

Re: [Qt-creator] Proposal increasing requirement for building Qt Creator 4.7

[André Hartmann]

Hi Andrzej,

Am 15.03.2018 um 23:06 schrieb Andrzej Telszewski:

On 15/03/18 15:08, Eike Ziller wrote:

https://codereview.qt-project.org/223368
Target branch “master” (will be 4.7)

"Increase requirement for building Qt Creator from Qt 5.6.2 to Qt 5.9

Qt 5.11 will be released and Qt 5.9 is the new LTS.
Increasing the requirement allows us to remove some baggage and
workarounds like Utils::asConst, special Q_OVERRIDE header, and
deployment target adaptions on macOS, and simplifies pulling in
proparser changes from Qt.”

This doesn’t affect the Qt that you use to develop your applications 
with.


Br, Eike



If this bump isn't yet strictly necessary, I'd love to stick with 5.7.
I'm on Slackware and 5.9 does not seem to be arriving soon.

But well, if need be, then I can't stop you ;-)


5.7 is no option, as it is no LTS and should have reached end-of-life 
already.


But it's very easy to install a recent Qt version with the online 
installer and use that for building Creator. I do it this way on Ubuntu 
16.04. Of course you can also build Qt from sources.


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

Re: [Qt-creator] GSoC 2018: New feature proposal for Qt Creator

[André Hartmann]

Hi Gowtham,

your proposal sounds indeed interesting. And we have the task 
QTCREATORBUG-16246, which almost looks like your suggestion.


So there *is* interest in this topic :)

I've just two comments to the implementation:

* Would it be enough to have the files on a network share instead of 
rsync'ing them?
* Is it really needed to have Clang running on the remote machine? Would 
it be enough to have access to the included headers on remote?


Best regards,
André

[1] https://bugreports.qt.io/browse/QTCREATORBUG-16246

Am 10.03.2018 um 21:15 schrieb Sree Gowtham Josyula:

Hello All,

This mail was initially posted in the Qt  Development mailing list
<http://lists.qt-project.org/pipermail/development/2018-March/032301.html>,
but I am reposting here, with minor edits, as the audience here are
more appropriate.

I am a Masters Student in Computer Engineering Program at Arizona
State University. I am interested in participating in Google Summer of
Code(GSoC) 2018 with Qt as my mentor organization. Link -
https://blog.qt.io/blog/2018/02/22/google-summer-of-code-2018/

In this mail, I would like to propose a new feature for Qt Creator as
my GSoC project, based on my experience at my previous company.

Issue faced in previous company -  In my previous company, we had our
development environment in Windows and target platform as arm-linux
machine. For that, we would develop code on Windows systems and then
sync the project/workspace to the remote linux server and then compile
with the cross-compilation tool-chain there and then deploy on the
target machine elsewhere.

In the above setup  we faced the following problems -
1. Unavailability of code completion frameworks on the development
machine as not all the platform headers were available locally
2. Frequently syncing the workspace was a wasteful of time

In order to solve the above problem, I would like to propose a "Remote
System Development Plug-in" for editing, compiling, executing &
debugging files on a remote system on the lines on Emacs Tramp package
(https://www.emacswiki.org/emacs/TrampMode).

High Level Features -

1. Public key registration of development machine on remote machine
(and vice-versa) for seamless syncing of files between the two
machines
2. Setting up a toolkit (Compiler, Debugger, Qt Tool-chain, cmake,
qmake, qbs, sysroot) of a remote machine on the Development machine's
Qt Creator IDE
3. Opening projects of remote machine in development machine (using
the same interface used for opening project on development machine)
4. Automatic syncing of workspace between development machine and
remote machine(on every save & periodically) - could be done using
rsync
5. Compilation of code on the remote machine with the tool-chain setup there
6. Execution & debugging code on Remote machine
7. Supporting Clang based code completion, got-definition &
refactoring - Might need to run a clang-daemon/Language Server on the
remote machine and send the responses to development machine.

Kindly let me know your thoughts about my above idea.

Best Regards,
Gowtham
(Sree Gowtham Josyula)
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartm...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 351 
26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbef

Re: [Qt-creator] Begging for some micro-features for 4.6/4.7

[André Hartmann]

Hi Jason,


I know the beta is out for 4.6, but I would like to request a few tiny "how hard 
could it be?" features.


There is a simple rule: features have to go in before the beta, the time 
between beta and release is for testing and bug fixing. So your wishes 
could go to 4.7 earliest.



1.  Add the really cool color ticks in the scrollbars (used for showing 
location of errors, found occurrences) of found occurrences to the Help, 
Compile, and Output panes. I figure this is a micro-feature because there is 
already a scrollbar that does it, and the finding ability also exists. It's 
just not yet applied for those panes.  I'm begging for this!!


I already found QTCREATORBUG-15703 and QTCREATORBUG-18333 as related 
requests. Does this cover all your needs? If not, feel free to add more 
suggestions.



2. Add new colors for class and function definitions to the scrollbars. The 
idea is that the Nth color tick corresponds to the nth class/function in header 
files and the Nth color corresponds to the Nth function for source. (Maybe have 
click to jump?)


I don't fully understand what you mean here... can you elaborate?

Best regards,
André

[1] https://bugreports.qt.io/browse/QTCREATORBUG-15703
[2] https://bugreports.qt.io/browse/QTCREATORBUG-18333









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





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartma...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 
351 26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
Weitergabe dieser Mail ist nicht

gestattet.

This e-mail may contain confidential and/or privileged information. If 
you are not the intended recipient
(or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden.

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

Re: [Qt-creator] [Win, CDB] No console window while debugging (missing since QtC 4.5.0)

[André Hartmann]

Hi Tilman

Am 26.01.2018 um 14:37 schrieb Tilman Skobowsky:

Hello everybody,


I run / debug on windows with VS2017 tools and CDB as debugger.
My project is configured to "Run in terminal".
Prior to QtC 4.5, when I hit either "Run" or "Debug", QtC showed the 
"qtcreator_process_stub.exe" console window where I can see certain 
logging info.
Starting with QtC 4.5 (also tried with the 4.5.1-1841 build from the 
snapshots directory) I get the console window when I hit "Run" but not 
when I hit "Debug".


Is this on purpose or am I missing some settings?


Seems like you hit QTCREATORBUG-19633 :(

Regards,
André

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

(I want to upgrade to the snapshot build due to the fix of 
QTCREATORBUG-18613)



Sincerely
Tilman Skobowsky



References:
     https://bugreports.qt.io/browse/QTCREATORBUG-18613
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator




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

Re: [Qt-creator] prepare-commit-msg and commit-msg hooks

[André Hartmann]

Am 09.01.2018 um 17:23 schrieb Seth Raymond:

yes. for example, a conscientious committer will want to revise the file
list when during writing the commit message they notice that the commit
is non-atomic. happens to me all the time.


Would a "back"/"cancel" button at the commit message window that
returns you to the file selection window be sufficient?


I'm quite sure that would break my workflow. And in all the yars I'm 
working with Creator, you're the first one that had such a requirement.



 I'm not particularly familiar with git gui, I've only ever used git > out of 
the terminal (and am now learning Qt Creator's git plugin).



Invoking git via the terminal is a series process, so obviously
the process in the GUI could be done in series.


I don't think so. Well, you can stage files also in Creator before 
commiting; but I think most people will just open the commit dialog
and work from there. But if you have a suggestion how this "new way of 
commiting in series" could look like, you're welcome to present.



You lose an aspect of convenience for the
sake of "proper" functionality. But I'm not the one who makes those
decisions; I just wanted to report a deficiency I saw and see if there
were any known workarounds.

Our team is just skipping the Creator git plugin altogether and will
be using git via the terminal/preferred GUI that works with the hooks
we've written.


Would you tell us which "preferred GUI" allows you to do that?




fwiw, qtc is imo still inferior to git gui regarding fine-grained
commits - the diff view and chunk-level staging are kinda hidden, and
line-wise staging apparently isn't there at all.
in fact, the selective staging context menu is outright broken in 4.5 -
there is no indication which actions make sense, and there are
duplicated actions.


Sounds to me like I'm not the only person having problems with the
plugin. Hopefully some extra functionality will be added in the future
to make the plugin line up better with git tools already in place
elsewhere. Creator is an *integrated* development environment, after
all...


Come on, Creators Git integration is the best I have seen so far. The 
only thing I miss, is an integrated Merge tool...


Regards,
André



On Tue, Jan 9, 2018 at 9:56 AM, Oswald Buddenhagen
<oswald.buddenha...@qt.io> wrote:

On Tue, Jan 09, 2018 at 09:03:14AM -0500, Seth Raymond wrote:

Is there a strong reason to keep the process in its current,
parallelized state?


yes. for example, a conscientious committer will want to revise the file
list when during writing the commit message they notice that the commit
is non-atomic. happens to me all the time.

fwiw, qtc is imo still inferior to git gui regarding fine-grained
commits - the diff view and chunk-level staging are kinda hidden, and
line-wise staging apparently isn't there at all.
in fact, the selective staging context menu is outright broken in 4.5 -
there is no indication which actions make sense, and there are
duplicated actions.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

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





--
Dipl.-Ing. (FH) André Hartmann
Softwareentwicklung / Software Development

E-Mail: andre.hartma...@iseg-hv.de | Tel: +49 351 26996-43 | Fax: +49 
351 26996-21


iseg Spezialelektronik GmbH - HIGH VOLTAGE. EXACTLY.
iseg-hv.de | iseg-hv.com | download.iseg-hv.com

Bautzner Landstr. 23, 01454 Radeberg / Rossendorf, Germany
Geschäftsführer / Managing directors: Dr. Frank Gleisberg, Dr. Joachim 
Pöthig

Amtsgericht / Lower district court: Dresden HRB 16250
Umsatzsteuer-Id: / VAT-ID: DE812508942

News / Information
https://iseg-hv.com/en/products/control#isegControl2 isegControl2 - 
Unified Control Software
https://iseg-hv.com/en/products/detail/EHS EHS FLEX - Customize and keep 
the price
https://iseg-hv.com/en/products/detail/EHS EHS STACK - Perfect for GEM 
Detectors
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf NEW! 
Product catalog 2017 / 2018 released
https://iseg-hv.com/en/products/detail/NHR NHR - NIM HV-Supply with 
reversible polarity


Links
https://www.linkedin.com/company/12726924 iseg on LINKEDIN | Let's stay 
connected!
https://www.youtube.com/channel/UC5AL-ZgOqSim_1gYNnndyzQ iseg on YOUTUBE 
| Tutorials and more ...

https://www.twitter.com/iseg_hv iseg on TWITTER | please follow!
https://iseg-hv.com/files/iseg-high-voltage-power-supplies.pdf iseg 
CATALOG | download product catalog as PDF
http://download.iseg-hv.com/ iseg DOWNLOADS | manuals, software, 
firmware and more...


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. Wenn Sie nicht der richtige
Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren 
Sie bitte sofort

Re: [Qt-creator] prepare-commit-msg and commit-msg hooks

[André Hartmann]

Am 09.01.2018 um 15:56 schrieb Oswald Buddenhagen:

On Tue, Jan 09, 2018 at 09:03:14AM -0500, Seth Raymond wrote:

Is there a strong reason to keep the process in its current,
parallelized state?


yes. for example, a conscientious committer will want to revise the file
list when during writing the commit message they notice that the commit
is non-atomic. happens to me all the time.


Me too.


fwiw, qtc is imo still inferior to git gui regarding fine-grained
commits - the diff view and chunk-level staging are kinda hidden,


But once you know it is there, it's no problem. There is also 
https://bugreports.qt.io/browse/QTCREATORBUG-18482 as suggestion to 
improve this.



and line-wise staging apparently isn't there at all.


Line-wise staging is in my pipeline: 
https://codereview.qt-project.org/#/c/213165


Regards,
André


in fact, the selective staging context menu is outright broken in 4.5 -
there is no indication which actions make sense, and there are
duplicated actions.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator



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

Re: [Qt-creator] Disabling auto-reload of qbs files

[André Hartmann]

Hi Christian (Gagneraud),

OK, I just realised that i'm using a custom build of Qtc, "Qt Creator 
4.5.0-rc1 (4.4.83)" - built on the 18th of October.
The reason being that Qt doesn't support Linux-x86_32 anymore, so I have 
to build it myself (I cannot switch to Linux-x86_64).
So this might not help at having a stable QtC. I will first install a 
release build (4.4.1 tag) and see how it goes.


Why? There won't be fixes to 4.4 anymore, as 4.5 is near the release. 
I'd continue with this version and provide as much info as possible to 
Christian (Kandeler). Perhaps its a regression? Then fixing it would be 
much appreciated by others also.


Best regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] Nominating Lorenz Haas for approver

[André Hartmann]

Hello all,

I'd like to nominate Lorenz Haas for approver status.

Lorenz has been contributing to Qt and Qt Creator since spring 2013. He 
has provided some high quality patches to Creators C++ Editor and is the 
author of Creators Beautifier plugin.


He is actively reviewing patches in these areas, and recently started 
contributing to and reviewing others patches for Qt OPC UA and MQTT also.


These are his own contributions:
https://codereview.qt-project.org/#/q/owner:%22Lorenz+Haas%22,n,z

and these are his reviews:
https://codereview.qt-project.org/#/q/reviewer:%22Lorenz+Haas%22,n,z

Best regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Qt Creator Windows snapshot looks XP-styled

[André Hartmann]

Hi David,

Am 25.10.2017 um 09:41 schrieb David Schulz:

looks like https://bugreports.qt.io/browse/QTCREATORBUG-19150.


Indeed. I'll track this.

Regards,
André



Greetings

David


On 25-Oct-17 09:38, André Hartmann wrote:

Hi all,

I just tried the latest Qt Creator 4.5 snapshot [1] on Windows 7. All 
is fine so far, however, some dialogs (e.g. the Git fixup dialog) 
looks very XP-style (e.g. the buttons have sharp edges). This was 
different with the Beta. I noticed that Creator is now build against 
Qt 5.10.


Is this a known feature/bug?

Best regards,
André

[1] 
https://download.qt.io/snapshots/qtcreator/4.5/4.5.0-rc1/1614/qt-creator-opensource-windows-x86_64-4.5.0-rc1_1614.exe 


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


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



--
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] Qt Creator Windows snapshot looks XP-styled

[André Hartmann]

Hi all,

I just tried the latest Qt Creator 4.5 snapshot [1] on Windows 7. All is 
fine so far, however, some dialogs (e.g. the Git fixup dialog) looks 
very XP-style (e.g. the buttons have sharp edges). This was different 
with the Beta. I noticed that Creator is now build against Qt 5.10.


Is this a known feature/bug?

Best regards,
André

[1] 
https://download.qt.io/snapshots/qtcreator/4.5/4.5.0-rc1/1614/qt-creator-opensource-windows-x86_64-4.5.0-rc1_1614.exe

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

Re: [Qt-creator] Is it possible to fix QTCREATORBUG-11259 in Qt Creator 4.5?

[André Hartmann]

Hi all,

Well, actually there are 24 votes.

Given that these 24 people are all C++ developers, has anybody of you 
thought about contributing this piece of code? By voting and waiting you 
don't get any step forward.


I see two possibilities: either the code model is already able to deduce 
the correct type for auto, then it should be quite easy to generate the 
tooltip. If the code model is not able to do this already, then some 
more knowledge and work will be needed to solve this task.


Best regards,
André

 10.10.2017 um 08:02 schrieb Christian Gagneraud:

On 10 October 2017 at 15:01, Vincent Hui <vincenthk...@gmail.com> wrote:

Hello,

QTCREATORBUG-11259 was reported for more than 3 and half years. It is about
auto type deduction. Is it possible to fix QTCREATORBUG-11259 in Qt Creator
4.5? Now there are 17 people voting for this issue.


+1 (20 now!)

Tested with QtC 4.4 with and without clang code model.

Chris



Thanks,
Vincent

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


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





--
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] Nominating Denis Shienkov for Approver status

[André Hartmann]

I'd like to propose the nomination of Denis Shienkov for Approver
status.

Denis has been the maintainer of QtSerialPort for a long time now.
He also formed the architecture of QtSerialBus and provided several CAN 
plugins there. He further contributes to other parts of Qt and QtCreator 
and is actively reviewing other changes (for example he has 
constructively improved a lot of my changes to QtSerialBus).


This is his own Gerrit dashboard:

https://codereview.qt-project.org/#/q/owner:%22Denis+Shienkov+%253Cdenis.shienkov%2540gmail.com%253E%22,n,z

And these are his reviews:

https://codereview.qt-project.org/#/q/reviewer:%22Denis+Shienkov+%253Cdenis.shienkov%2540gmail.com%253E%22,n,z

Best regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Code review process for Qt Creator patches

[André Hartmann]

Hi Alexander,

All contributions to the Qt Project have to go thought Gerrit [1] due to 
licensing.


There are several pages describing how to start, best read [2] first and 
follow the links there. After you pushed your patches to Gerrit, you 
have to add reviewers. This could be a bit problematic, as Autotools has 
no maintainer at the moment [3]. I guess you should add Tobias Hunger in 
this case, as he is the general Project Management maintainer. Doing a 
git blame in the files you changes might also help finding people 
familar with the code.


Best regards,
André

[1] codereview.qt-project.org
[2] https://wiki.qt.io/Setting_up_Gerrit
[3] https://wiki.qt.io/Maintainers

Am 18.04.2017 um 06:42 schrieb Roessler, Alexander:

Hello,


I have made some changes to the Autotoolsprojectmanager plugin for Qt
Creator which I would like to push upstream.


How can I submit my patch to the code review process for Qt Creator?


Best regards,

Alexander



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




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

[Qt-creator] Generic highlighter für Bitbake *.inc files

[André Hartmann]

I found the bitbake-syntax-highlighter generic highlighter on Github [1] 
and started to use it for my bitbake receipes with QtCreator.


Highlighting of .bb and .bbappend files works well, but .inc files are 
not highlighted at all. If I edit the XML file and change "*.inc" to 
"*.bbinc" in the extension list line and rename my file, the 
highlighting is fine. But that's not what I want to do :)


Any ideas on this?

Best regards,
André

I have tried QtCreator 3.4 and 4.2.

[1] https://github.com/ikoveshnikov/bitbake-syntax-highlighter
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Etiquette for getting code reviews, and who to ask

[André Hartmann]

Hi Marc,

either you already know who is responsible for a module or you just do 
the simple way:


Do a git blame on the files you changed and see who worked most or 
recently on it. That's the way I do if I submit a patch and I think most 
other do it the same way.


Best regards,
André

Am 23.06.2016 um 09:57 schrieb Marc Reilly:

Hi All,

How do I find/determine who is best/able to review code, and is it
considered impolite to just add people as reviewers?

I have a series which is similar to another which one which was
previously accepted, so I would start will those people, but it seems
kinda rude to just add everyone en-masse.

Anyway, if anyone is interested, I've implemented a hover handler which
will preview images from .qrc files when mouse hovers over a
"qrc:/file/image.png" bit of text. At the moment it is just for cpp files..

The series is 4 commits, and starts with:
https://codereview.qt-project.org/#/c/158305/

Cheers,
Marc

(FWIW, i'm happy for anyone to add me as a reviewer)


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



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

Re: [Qt-creator] Searching for names in locator with starting letters as it is in code-completion

[André Hartmann]

Hello,

there was already a patch on Gerrit that was never integrated:

https://codereview.qt-project.org/#/c/61581/

I think it's not much missing there, but someone just had to continue 
the work...


Andre

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

Re: [Qt-creator] Looking for Enums with Locator

[André Hartmann]

Hi Nikolai,

just speaking for me, code completion for enum parameters would help 
more. There's already a report for this:


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

Just in case you want to work in this direction...

Anyway, thanks for making QtCreator the best IDE ever (for me).

Best regards,
Andre

Am 13.04.2016 um 09:42 schrieb Nikolai Kosjar:

On 04/12/2016 11:30 AM, Prav wrote:

Hi, Nikolai.


it seems that there is support for enum declaration... but not for enum
values (not yet?) ...

Correct.

Ok. I see. Does  it  make sense for you to add enum values in Locator?
... From my experience enum-values seems to be used same or
even more frequently in programs


I'm fine with making enum values "locatable", though personally I
haven't missed them.

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



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

Re: [Qt-creator] Fwd: issue with issue pane

[André Hartmann]

Hi Dmitry,

first of all, please keep the mailing list included, your problem might 
be interesting for others too and you get more help the more people read 
from it.


That said, sorry, the custom parser for now only scans for errors,
not warnings. I already started to extend the parser but never finished 
it (time is short...):


https://codereview.qt-project.org/#/c/80533/

If you want to take over... feel free to do so. I'd be happy to review 
your changes.


Best regards,
Andre


Hi,

Yes, custom error parser works with _*"(.*)", line (\d+): (.*)$*_ , now
it showing errors in source code and I can make jumps to line in file,
but it treats all "errors" and "warnings" like an errors. Is it possible
to configure it somehow to treat them separately (errors are red,
warnings are yellow)? I couldn't find any documentation about error parser.

Regards,

Dmitry

On 16 December 2015 at 11:51, André Hartmann <andre.hartm...@iseg-hv.de
<mailto:andre.hartm...@iseg-hv.de>> wrote:

Hi

I have some makefile projects, too, and things work fine for me.
My compiler pattern for errors looks like this:

  ../src/main.c:708: error: xxx

while yours is

   "../src/main.c", line 708: error #20: xxx

It's quite possible, that your pattern is not recognized (correctly)
by Creators gcc error parser.

If you want to check yourself, its in gccparser.cpp, I could have a
look later today.

A possible solution is to set up a custom compiler in
Tools -> Options -> Build & Run -> Compilers -> Add -> Custom and
then set up a custom error parser (regular expression based). This
one is a bit slower but should support every possible compiler :)

Best regards,
Andre

Am 16.12.2015 um 12:17 schrieb cyb:


-- Forwarded message --
From: *cyb* <cg.ve...@gmail.com <mailto:cg.ve...@gmail.com>
<mailto:cg.ve...@gmail.com <mailto:cg.ve...@gmail.com>>>
Date: 16 December 2015 at 10:48
Subject: Re: [Qt-creator] issue with issue pane
To: Ziller Eike <eike.zil...@theqtcompany.com
<mailto:eike.zil...@theqtcompany.com>
<mailto:eike.zil...@theqtcompany.com
<mailto:eike.zil...@theqtcompany.com>>>


Hi,

 ** Creator version*

QtCreator version 3.5.1, Build on Oct 15 2015, From revision
b4c52505ca

 *Which compiler is this?*

This is a Ti GCC based compiler for TMS320C55xx DSP, from Code
Composer
Studio v6. GCC error parser is working fine.

 ** How is the project organized?*

This is a makefile project, I just imported project sources and
using
qtcreator for building and editing.
*
*

 *  - Are the sources files in subdirectories?
  (Best would be to send the project file)*

Attached if it will help.

 ** Please send the contents of compile output pane too.
 *


Example compile output pane:

10:38:07: Running steps for project Vmic-DSP...

10:38:07: Starting: "c:\Program Files
(x86)\ti\ccsv6\utils\bin\gmake.exe" -k all

'Building file: ../src/main.c'

'Invoking: C5500 Compiler'

"C:/Program Files
(x86)/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55"
-v5505 --memory_model=large -g --include_path="C:/Program Files
(x86)/ti/ccsv6/tools/compiler/c5500_4.4.1/include"

--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/CELT_Codec_0.7.1/libcelt"

--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/dsplib_3.0/inc"
--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/inc"

--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/usbstk5505/inc"
--define=c5505 --define=DECT_FP --define=HAVE_CONFIG_H
--display_error_number --diag_warning=225 --ptrdiff_size=16
--algebraic
--asm_source=algebraic --preproc_with_compile
--preproc_dependency="src/main.pp" --obj_directory="src"
"../src/main.c"

"../src/main.c", line 708: error #20: identifier
"overflowDetected" is
undefined

"../src/main.c", line 713: error #20: identifier
"overflowDetected" is
undefined

"../src/main.c", line 496: warning #552-D: variable
"CapturedPCML" was
set but never used

2 errors detected in the compilation of "../src/main.c".


gmake: *** [src/main.obj] Error 1

Compilation failure


gmake: Target `all' not remade because of errors.

10:38:08: The process "c:\Pro

Re: [Qt-creator] Fwd: issue with issue pane

[André Hartmann]

Hi

I have some makefile projects, too, and things work fine for me.
My compiler pattern for errors looks like this:

 ../src/main.c:708: error: xxx

while yours is

  "../src/main.c", line 708: error #20: xxx

It's quite possible, that your pattern is not recognized (correctly)
by Creators gcc error parser.

If you want to check yourself, its in gccparser.cpp, I could have a look 
later today.


A possible solution is to set up a custom compiler in
Tools -> Options -> Build & Run -> Compilers -> Add -> Custom and then 
set up a custom error parser (regular expression based). This one is a 
bit slower but should support every possible compiler :)


Best regards,
Andre

Am 16.12.2015 um 12:17 schrieb cyb:


-- Forwarded message --
From: *cyb* <cg.ve...@gmail.com <mailto:cg.ve...@gmail.com>>
Date: 16 December 2015 at 10:48
Subject: Re: [Qt-creator] issue with issue pane
To: Ziller Eike <eike.zil...@theqtcompany.com
<mailto:eike.zil...@theqtcompany.com>>


Hi,

** Creator version*

QtCreator version 3.5.1, Build on Oct 15 2015, From revision b4c52505ca

*Which compiler is this?*

This is a Ti GCC based compiler for TMS320C55xx DSP, from Code Composer
Studio v6. GCC error parser is working fine.

** How is the project organized?*

This is a makefile project, I just imported project sources and using
qtcreator for building and editing.
*
*

*  - Are the sources files in subdirectories?
 (Best would be to send the project file)*

Attached if it will help.

** Please send the contents of compile output pane too.
*

Example compile output pane:

10:38:07: Running steps for project Vmic-DSP...

10:38:07: Starting: "c:\Program Files
(x86)\ti\ccsv6\utils\bin\gmake.exe" -k all

'Building file: ../src/main.c'

'Invoking: C5500 Compiler'

"C:/Program Files (x86)/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55"
-v5505 --memory_model=large -g --include_path="C:/Program Files
(x86)/ti/ccsv6/tools/compiler/c5500_4.4.1/include"
--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/CELT_Codec_0.7.1/libcelt"
--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/dsplib_3.0/inc"
--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/inc"
--include_path="D:/_PROJECTS/Tulip_Av2/Software/dsp/Vmic-DSP/usbstk5505/inc"
--define=c5505 --define=DECT_FP --define=HAVE_CONFIG_H
--display_error_number --diag_warning=225 --ptrdiff_size=16 --algebraic
--asm_source=algebraic --preproc_with_compile
--preproc_dependency="src/main.pp" --obj_directory="src" "../src/main.c"

"../src/main.c", line 708: error #20: identifier "overflowDetected" is
undefined

"../src/main.c", line 713: error #20: identifier "overflowDetected" is
undefined

"../src/main.c", line 496: warning #552-D: variable "CapturedPCML" was
set but never used

2 errors detected in the compilation of "../src/main.c".


gmake: *** [src/main.obj] Error 1


Compilation failure


gmake: Target `all' not remade because of errors.

10:38:08: The process "c:\Program Files
(x86)\ti\ccsv6\utils\bin\gmake.exe" exited with code 2.

Error while building/deploying project Vmic-DSP (kit: Ti-C55-gcc-toolset)

When executing step "Make"

10:38:08: Elapsed time: 00:01.




There also was a discussion on the forum:
http://forum.qt.io/topic/61578/qt-creator-issue-with-issue-pane

Regards,

Dmitry

On 16 December 2015 at 10:25, Ziller Eike <eike.zil...@theqtcompany.com
<mailto:eike.zil...@theqtcompany.com>> wrote:


> On Dec 16, 2015, at 10:24 AM, cyb <cg.ve...@gmail.com 
<mailto:cg.ve...@gmail.com>> wrote:
>
> Hi, there's an issue with issue pane.
>
> Everything should be clear from next screenshot
>
> Gcc error parser is working, there's a line and file but it cannot take me to issue 
and not showing issue in source file. Maybe it because I used "Import project" but 
it should work in theory. Is this a my bug or feature was not implemented yet?

Qt Creator thinks that your file is called

main.c”

with a “ at the end.

What’s your compile output? (contents of “Compile Output” pane)
What compiler do you use on what platform?
Br, Eike

 >
 > Thanks,
 >
 > Dmitry
 >
 > ___
 > Qt-creator mailing list
 > Qt-creator@qt-project.org <mailto:Qt-creator@qt-project.org>
 > http://lists.qt-project.org/mailman/listinfo/qt-creator

--
    Eike Ziller, Senior Software Engineer - The Qt Company GmbH

The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht
   

Re: [Qt-creator] Is it possible to run some commands or scripts on saving the documents?

[André Hartmann]

Hi all,

there is already code under review to "beautify" on each save:

https://codereview.qt-project.org/#/c/124941/

So suggestions and comments can also be placed there to continue the 
review process and get the patch accepted.

Best regards,
Andre

Am 09.09.2015 um 16:11 schrieb Tobias Hunger:
> On Wed, Sep 9, 2015 at 4:00 PM, Hualet Wang  wrote:
>> Hi Lorenz,
>>
>> I occasionally found below lines in source code of todo plugin,
>>>
>>>  CppTools::CppModelManager *modelManager 
>>> =CppTools::CppModelManager::instance();
>>>
>>>  connect(modelManager, ::CppModelManager::documentUpdated,
>>>  this, ::documentUpdated, 
>>> Qt::DirectConnection);
>>
>> I’m pretty excited about that finding, maybe you can use the APIs in that 
>> snippet to run
>> Beautifier on the document every time the document get updated?
>
> Why would you want to do that?
>
> There are *lots* of document updates and slowing each and every one of
> those down with the beautifier.
>
> What keeps you from changing the indenter with the functionality you
> are missing? Then you would only insert "beautiful" lines and would
> not need the beautifier plugin at all:-)
>
> Best Regards,
> Tobias
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
>


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

Re: [Qt-creator] UTF-8 Strings in QtCreator source code

[André Hartmann]

Hi Jochen,

if I remember correctly, MSVC (at least older versions) needs a BOM 
(Byte Order Mark) at the file's beginning to detect UTF-8 encoded files.
Then it should work even without C++11 string constants.

Maybe that's the reason for your problems.

Best regards,
André

Am 07.09.2015 um 11:49 schrieb Hunger Tobias:
>> C++11 introduced new UTF-8 string constans, so it should be possible to
>> write the following:
>
>> QStringLiteral(u8"This is a Unicode Character: \u2018.")
>
>> and all C++11 compiler should compile it without warnings. Right?
>
>> Shall we change the coding style and allow the new UTF-8 string
>> literals?
>
> I rarely use windows, but considering that all Qt 5 code needs to be utf8 
> encoded anyway, I am a bit surprised that special markup of charcater 
> constants as utf8 are required.
>
> Best Regards,
> Tobias
>
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
> ___
> Qt-creator mailing list
> Qt-creator@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
>
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] use external terminal in Qt Creator

[André Hartmann]

Hi Freddy,

Are you on Linux?

Creator has a setting in the Tools - Options - Environment - General 
tab to set the terminal.

The default is /usr/bin/xterm -e, but it seems you can insert your 
option -hold there also.

Then you have to check Run in terminal in the Projects mode - Build  
Run - Run configuration.

Disclaimer: I have not tried this out.

Best regards,
André

Am 13.07.2015 um 23:29 schrieb Freddy Martinez Garcia:
 Hi guys... I'm new in my job and they work with KDevelop only because to
 debug the system, we need the option Use External Terminal with value
 *xterm -hold -e %exe

 *
 I have a lot of time working with Qt Creator, is my favorite C++ IDE and
 I'll like to use it, but I need this option for debugging the application...

 KDevelop has this option in the Launch Configuration dialog

 can I do de same with Qt Creator ??

 best regard

 *=
 El tamaño de tus logros depende del tamaño de tus metas.
 *
 *C++ and Qt Senior Developer
 *
 *Lic. Computer Science
 *
 *Buenos Aires, Argentina
 *
 *
 *


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


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

Re: [Qt-creator] Pretty old changes on gerrit

[André Hartmann]

Hi Jochen,

  there are quite a number of very old changes on gerrit's master which
  past the sanity bot review but never got a human review. Would it help
  reviewing those changes starting with the oldest one?

For sure! If the changes are old, it may be better to ask the author 
first if they are still relevant.

  May I add myself as reviewer to changes?

Yes. I do that too, if I have time, I am interested in the change and 
find something to comment on.

  Of course there is the coding style but should a reviewer also run
  tests with the reviewed code?

  Should changes be built with qmake and qbs always?

Please read the following, it's not Qt specific but in general useful:

http://gerrit-training.scmforge.com/target/gerrit-and-code-review-best-practices/

To summarize possible review steps:

1. Read the code and look for style and logic errors
2. Suggest improvements
3. Cherry-pick the change to your local repo,
does it apply without merge conflicts?
4. Compile the change, are there warnings or errors
5. Test the change

As Qt is cross-platform, 4 and 5 may work on one platform, but fail on 
an other. So every tester is welcome.

Best regards,
André

Am 04.06.2015 um 23:37 schrieb Jochen Becher:
 Hello,

 there are quite a number of very old changes on gerrit's master which
 past the sanity bot review but never got a human review. Would it help
 reviewing those changes starting with the oldest one?

 As I hope to publish my ModelEditor plugin in the next days and hope to
 for reviews soon I am willing to help with other reviews of course. May
 I add myself as reviewer to changes?

 I couldn't find documentation about expectations on reviews. Of course
 there is the coding style but should a reviewer also run tests with the
 reviewed code? What about documentation? Is this always reviewed by
 Leena? Should changes be built with qmake and qbs always?

 Regards, Jochen


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



-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Preparing to contribute Boost.Build Plugin to Qt Creator

[André Hartmann]

Hi Mateusz,

First thing: I'm absolutely no Git nor Gerrit expert, they might correct 
me when I'm wrong.

  For example, let's assume we start working on the contribution as 
follows:
  1. Import current sources of our plugin into wip/boostbuildprojectmanager

To submit this first commit, it would be best all current developers 
give a +1 review to show their acceptance that the code is merged to the 
Qt repositories.

Afterwards, you can pull this branch and start further work.

  2. git push gerrit HEAD:refs/wip/boostbuildprojectmanager  (?)

This would be done after you changed a bit, i.e. created a patch.

Imho the command would be something like:

git push gerrit HEAD:refs/for/wip/boostbuildprojectmanager

  3. Developers A and B pull the changes

Yes, they do to test the new things out.
Then they suggest improvements to the patch, and the original developer 
A or any other pushes a new change set (with step 2). It is important to 
keep the Change-Id line in the commit footer, so Gerrit knows the new 
push belongs to an existing change.

Once this change is ready for submission (approved), it is cherry-picked 
to the wip/boostbuildprojectmanager branch and can be pulled by anyone.

Further development / coding style corrections go on with new Change sets.

Maybe it's best to have a look around at the open changes on Gerrit and 
how other developers interact with each other.

And if you have other questions, feel free to ask :)

Best regards,
André

Am 15.04.2015 um 00:13 schrieb Mateusz Loskot:
 On 19 February 2015 at 09:35, Mateusz Loskot mate...@loskot.net wrote:
 I've opened GitHub issue [2] devoted to discussion it further
 and prepare the submission through Gerrit.

 Finally, we've decided to work in Gerrit from the start [0], in a new
 long-living branch (we've got wip/boostbuildprojectmanager there).

 I've configured my local clones for Gerrit set up according to [1]
 and I've familiarised myself with [2] and [3].

 Now, I've got some Gerrit workflow issues I'd like to clarify.
 I'm not the only contributor who is going to work on the contribution
 and there will be numerous iterations of update of our Change in Gerrit.
 The intro [2] says Each time a Change is updated, it gains a new Patch Set,
 where a new Patch Set contains commits (initial or updated) ready for review.
 There is no way to push updates without creating new Patch sets.

 How to arrange iterative intermediate updates, before requesting review?

 For example, let's assume we start working on the contribution as follows:
 1. Import current sources of our plugin into wip/boostbuildprojectmanager
 2. git push gerrit HEAD:refs/wip/boostbuildprojectmanager  (?)
 3. Developers A and B pull the changes
 4. Developer A commits some coding style corrections
 4.1 git push gerrit HEAD:refs/wip/boostbuildprojectmanager  (?)
 ...nothing ready for review yet...
 5. Developer B updates his clone, then commits some more style corrections
 5.1 git push gerrit HEAD:refs/wip/boostbuildprojectmanager  (?)
 ... step 4 and 5 repeat and interleave...
 6. wip/boostbuildprojectmanager  builds, runs and is ready for first review

 Wouldn't the steps in 4. and 5. create noise numerous half-ready Patch Sets?
 In order to avoid that, shall we move the early collaboration to
 'private' clone, e.g. on GitHub
 and once the contribution is ready for first review, push to Gerrit?
 Then, if more updates are requested, prepare them on GitHub, once
 ready, push to Gerrit
 (as new Patch Set)?

 The [3] says: Note that pushing to your private clone does not count
 as publishing and
 is a perfectly valid way to solicit an early review, so I guess that
 use of GitHub for
 intermediate changes is the way to go, isn't it?

 [0] http://lists.qt-project.org/pipermail/qt-creator/2015-April/004580.html
 [1] https://wiki.qt.io/Setting_up_Gerrit
 [2] https://wiki.qt.io/Gerrit_Introduction
 [3] https://wiki.qt.io/Commit_Policy

 Best regards,



-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution

Re: [Qt-creator] QtCreator plugin contribution

[André Hartmann]

Hi,

 BTW, there are more Wiki pages that you need to crunch:
 https://wiki.qt.io/Branch
 https://wiki.qt.io/Branch_Guidelines
 The latter explains recommendations and caveats of possible
 development workflows.

But that's only true for Qt itself.

Creator has a much simpler workflow:

* new features go to master
* Bug fixes go to the latest stable branch or to master,
   depending on the importancy and technical risk

So just push your new plugins to master.

Best regards,
André


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

Re: [Qt-creator] QtCreator plugin contribution

[André Hartmann]

Thanks Orgad for clarifying this :)

  André meant pushing to refs/for/master, not directly to master.

Yes, that was exactly what I meant. Maybe I shouldn't write to the list 
before my first coffee...

  And do this one needs the necessary karma :-)

Push rights would be enough :-P

But, jokes aside, I think the following two pages might also interesting 
(as I now noticed the weren't mentioned before):

https://wiki.qt.io/Gerrit_Introduction
https://wiki.qt.io/Setting_up_Gerrit

This seems a lot of work at first glance, but if you take it step by 
step it's not that complicated.

If you have any questions, feel free to ask here.

Best regards,
André

Am 13.04.2015 um 08:57 schrieb Orgad Shaneh:
 On Mon, Apr 13, 2015 at 9:30 AM, Jürgen Hunold jhun...@gmx.eu
 mailto:jhun...@gmx.eu wrote:

 Hi André,

 Am Montag, 13. April 2015, 08:18:29 schrieb André Hartmann:
   Hi,
  But that's only true for Qt itself.
 
  Creator has a much simpler workflow:

 So why does

 
 https://codereview.qt-project.org/#/q/status:open+project:qt-creator/qt-creator,n,z

 show a lot of activity?


 He referred to the branching scheme, not to the gerrit workflow itself.

  * new features go to master
  * Bug fixes go to the latest stable branch or to master,
 depending on the importancy and technical risk
 
  So just push your new plugins to master.

 And do this one needs the necessary karma :-)

 I think we better have the new code reviewed and approved first.


 You don't really have a choice ;-).

 André meant pushing to refs/for/master, not directly to master.

 - Orgad


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



-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtCreator plugin contribution

[André Hartmann]

Just two more cents from my side,

  I hope it's acceptable workflow, as two other developers that joined
 my efforts are based on GitHub, and GitHub simlifies our collaboration a
 lot.

 Every author needs to agree to the Contribution Licensee Agreement, so make
 sure that everyone that joins you understands and signs that CLA.

Maybe a wip (work in progress) branch on Qt Gerrit is the better choise?

Pros:
- All contributors sign the CLA, so there's no licence problems later
- You get the Qt Sanity Bot (and human reviewers) checking the coding
   style
- The code is under broader review, maybe more contributions come in
- You make it easy for others to check out that branch and test it
- When the work is finished, the branch could easily be merged
- Further work after the initial release has to be done on Gerrit anyway

Cons:
- You and your contributors need to setup and learn Gerrit,
   but you will need to anyway, and I think the other two already did :)

Personally I don't see much advantage for external developing on GitHub.

But that's just my personal opinion.

Best regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] QtCreator 3.3 RC looses MSVC compiler settings

[André Hartmann]

Hi Christian,

Thanks for the hint. Indeed, updating to tonight's version helped.

Best regards,
André

Am 27.11.2014 um 08:25 schrieb Stenger Christian:
 Hi,

 yes, that's a known issue and should have been fixed already ( 
 https://bugreports.qt-project.org/browse/QTCREATORBUG-13515 )

 Kind regards,
 Christian

 
 From: qt-creator-bounces+christian.stenger=theqtcompany@qt-project.org 
 qt-creator-bounces+christian.stenger=theqtcompany@qt-project.org on 
 behalf of André Hartmann andre.hartm...@iseg-hv.de
 Sent: Thursday, November 27, 2014 8:16 AM
 To: qt-creator@qt-project.org
 Subject: [Qt-creator] QtCreator 3.3 RC looses MSVC compiler settings

 Hi,

 When working with the Nightly 3.3 Build as of Nov 25 (9a5f81d96f) under
 Windows 7 x64, my two MSVC kits loose their Compiler setting.
 Interestingly, the one MinGW kit doesn't.

 The Qt versions are all Manual, the MSVC compilers are
 Auto-detetcted and the MinGW is Manual.

 Is this a known problem?

 Thanks.

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




-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] QtCreator 3.3 RC looses MSVC compiler settings

[André Hartmann]

Hi,

When working with the Nightly 3.3 Build as of Nov 25 (9a5f81d96f) under 
Windows 7 x64, my two MSVC kits loose their Compiler setting. 
Interestingly, the one MinGW kit doesn't.

The Qt versions are all Manual, the MSVC compilers are 
Auto-detetcted and the MinGW is Manual.

Is this a known problem?

Thanks.

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

[Qt-creator] Change path to external DLLs for program execution

[André Hartmann]

Hello,

I have (Windows) projects that depends on external
libraries.

Whenever a new version of this lib is released,
I have to compile and test the projects against
the new version and sometimes switch back to the
old version.

Qmake already makes my life very easy, as I can
switch between them by changing the CONFIG variable:

# project.pro

CONFIG += LIB_V1
#CONFIG += LIB_V2

LIB_V1 {
INCLUDEPATH += c:/lib_v1/include
QMAKE_LIBDIR += c:/lib_v1/lib
}

LIB_V2 {
INCLUDEPATH += c:/lib_v2/include
QMAKE_LIBDIR += c:/lib_v2/lib
}

Now my last problem is, that I need the corresponding
DLLs from either c:/lib_v1/bin or c:/lib_v2/bin when
executing my program from Qt Creator.

Is there a way to achive this?

The worst possible way would be to copy the DLLs to the
build directory in a build step, but maybe there is a
cleaner solution?

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

Re: [Qt-creator] Design 3#

[André Hartmann]

I really like the small mode bar at the left side.

But if text is written vertically, it should be readable from the right 
side!

But maybe it's enough to display the text as tooltip.
In this case, I'd prefer to have menu items for the mode switching too.

Juts my two cents,
André

 Hey Folks,

 Some new Designs J

 Light Theme:

 http://img4.imageshack.us/img4/4947/5h2.png

 Dark Theme:

 http://img96.imageshack.us/img96/2734/rspm.png

 I would appreciate useful feedback.

 Best,

 Eli



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



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

[Qt-creator] Keyboard layout switching hotkey?

[André Hartmann]

Hi all,

It happens once in a while that I press a key sequence that switches the 
keyboard layout from German to English within Qt Creator.

My system is Windows 7 64bit, QtCreator 2.8.1 (Qt 4.8.4) from 
qt-project.org. Other Windows program and I seems other Creator 
instances are not influenced.

When I restart the Creator instance, the keyboard is back to German.

I'm unsure which combination I press, but I think Ctrl is involved.

Is this known and desired behavior? If yes, how can I switch back?

Best regards,
André


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

[Qt-creator] How to run single new autotest

[André Hartmann]

Hello,

I've working on adding a new autotest for the AnsiEscapeCodeHandler:

https://codereview.qt-project.org/#change,65028

The test should in principle work like the one for fileutils.

I've managed to compile and link this after some investigation and with 
help from Orgad.

Now my question: How can I run just this single test? Running all tests 
lasts too long during development.

Best regards,
André
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] How to run single new autotest

[André Hartmann]

Hi Orgad,

Thanks, I didn't know that. Seem like I could have asked you directly 
yesterday :)

I will try this afternoon.

Is this documented somewhere?

Best regards,
André

Am 10.09.2013 08:41, schrieb Orgad Shaneh:
 On Tue, Sep 10, 2013 at 9:20 AM, André Hartmann
 andre.hartm...@iseg-hv.de mailto:andre.hartm...@iseg-hv.de wrote:

 Hello,

 I've working on adding a new autotest for the AnsiEscapeCodeHandler:

 https://codereview.qt-project.org/#change,65028

 The test should in principle work like the one for fileutils.

 I've managed to compile and link this after some investigation and with
 help from Orgad.

 Now my question: How can I run just this single test? Running all tests
 lasts too long during development.

 Best regards,
 André
 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org mailto:Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator


 Good morning,

 If you build it using Creator (by passing BUILD_TESTS=1 to qmake), you
 can just choose it in the Run configuration (or in the mini target
 selector).

 Otherwise, execute ./tst_ansiescapecodehandler from the build directory.

 Executing qtcreator -test *doesn't* run those tests anyway.

 - Orgad


-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Slow cdb

[André Hartmann]

Do you try to access global variables?

I sometimes have a dead slow cdb too, if I try to access member / global 
variables that are out of scope.

In this case, there are warnings in the debugger log that it can't 
access the variable.

Once you run into this problem, the only solution is to re-start Creator 
(it seems the watched variable can't be removed)

Andre

Am 04.06.2013 09:40, schrieb Peter Kümmel:
 Wasn't there a wiki entry about dead slow cdb or cdb in general?

 I think there was something related to the warning
   WARNING: Unable to verify checksum for ...
 but I couldn't find it any more.

 What was the reason for this warning, is this warning related to the slowdown?
 How could I fix the bad cdb speed on my installation side?

 (I use cdb to debug gdb support atm)

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



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

Re: [Qt-creator] MinGW GDB not stopping at breakpoints

[André Hartmann]

Hello Kai,

  we changed the way how breakpoints are set in 2.8 from just the
  filename to absolute paths

Yeah, I remember I saw it on Gerrit...

  You can change the breakpoint by right click in Breakpoints
  view-Edit Breakpoint...Path, switch to Use File Name.

Yes this works for me.
In my case, the source and build directory are on a network-drive.
I will try later on a local drive to see how it behaves there.

Best regards,
André

Am 24.05.2013 08:46, schrieb Koehne Kai:
 -Original Message-
 From: qt-creator-bounces+kai.koehne=digia@qt-project.org [mailto:qt-
 creator-bounces+kai.koehne=digia@qt-project.org] On Behalf Of André
 Hartmann
 Sent: Thursday, May 23, 2013 9:16 AM
 To: qt-creator@qt-project.org
 Subject: [Qt-creator] MinGW GDB not stopping at breakpoints

 Hello,

 I have build QtCreator from the 2.8 branch a week ago with MSVC 2010 /
 32bit.

 Operating system is Windows 7 64bit.

 Yesterday I realized that GDB 7.4 is not breaking. It works perfectly with an
 official Creator 2.7 Installation.

 Hi André,

 we changed the way how breakpoints are set in 2.8 from just the filename to 
 absolute paths . Could you check whether changing it back to relative path 
 fixes the issue for you?

 You can change the breakpoint by right click in Breakpoints view-Edit 
 Breakpoint...Path, switch to Use File Name.

 Regards

 Kai




-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

[Qt-creator] MinGW GDB not stopping at breakpoints

[André Hartmann]

Hello,

I have build QtCreator from the 2.8 branch a week ago with MSVC 2010 / 
32bit.


Operating system is Windows 7 64bit.

Yesterday I realized that GDB 7.4 is not breaking. It works perfectly 
with an official Creator 2.7 Installation.


Unfortunately there are no 2.8 builds on builds.qt-project.org at the 
moment, so I can't check these.


Debugger log is attached.

Best regards,
Andre
sStarting debugger GdbEngine for ABI x86-windows-msys-pe-32bit...
dStart parameters: 'tests' mode: 1
dABI: x86-windows-msys-pe-32bit
dLanguages: c++ 
dExecutable: 
X:\S12X\KernelLibrary\build-tests-Desktop_Qt_4_8_2_MinGW-Debug\debug\tests.exe 
dDirectory: X:\S12X\KernelLibrary\build-tests-Desktop_Qt_4_8_2_MinGW-Debug
dDebugger: C:\Qt\qtcreator-gdb-7.4-MINGW32_NT-6.1-i686\gdb-i686-pc-mingw32.exe
dProject: X:\S12X\KernelLibrary\tests (built: 
X:\S12X\KernelLibrary\build-tests-Desktop_Qt_4_8_2_MinGW-Debug)
dQML server: 127.0.0.1:3768
dRemote: :0
dSysroot: 
dDebug Source Location: 
/usr/src/debug/qt5base/src/corelib:/usr/src/debug/qt5base/src/gui:/usr/src/debug/qt5base/src/network
dSymbol file: 
dDumper libraries:  C:\Qt\4.8.2\qtc-debugging-helper\ 
D:\Daten\Tools.qt\build-qtcreator-Desktop_Qt_4_8_2_MSVC_2010-Release\qtc-debugging-helper\128627218\
 
C:\Users\ah.ISEG\AppData\Local\QtProject\QtCreator\qtc-debugging-helper\128627218\
dDebugger settings: 
dQmlInspector.FromQml: false  (default: false)
dUseAlternatingRowColours: false  (default: false)
dFontSizeFollowsEditor: false  (default: false)
dUseMessageBoxForSignals: true  (default: true)
dAutoQuit: false  (default: false)
dLogTimeStamps: false  (default: false)
dVerboseLog: false  (default: false)
dCloseBuffersOnExit: false  (default: false)
dSwitchModeOnExit: false  (default: false)
dBreakpointsFullPath: false  (default: false)
dRaiseOnInterrupt: true  (default: true)
dUseDebuggingHelper: true  (default: true)
dUseCodeModel: true  (default: true)
dShowThreadNames: false  (default: false)
dUseToolTips: true  (default: false)  ***
dUseToolTipsInLocalsView: false  (default: false)
dUseToolTipsInBreakpointsView: false  (default: false)
dUseAddressInBreakpointsView: false  (default: false)
dUseAddressInStackView: false  (default: false)
dRegisterForPostMortem: false  (default: false)
dLoadGdbInit: true  (default: true)
dLoadGdbDumpers: true  (default: true)
dAttemptQuickStart: false  (default: false)
dGdbStartupCommands:   (default: )
dGdbPostAttachCommands:   (default: )
dWatchdogTimeout: 20  (default: 20)
dAutoEnrichParameters: false  (default: true)  ***
dUseDynamicType: true  (default: true)
dTargetAsync: false  (default: false)
dWarnOnReleaseBuilds: true  (default: true)
dMultiInferior: false  (default: false)
dIntelFlavor: false  (default: false)
dIdentifyDebugInfoPackages: false  (default: false)
dMaximalStackDepth: 20  (default: 20)
dAlwaysAdjustStackColumnWidths: false  (default: false)
dShowStandardNamespace: true  (default: true)
dShowQtNamespace: true  (default: true)
dSortStructMembers: true  (default: true)
dAutoDerefPointers: true  (default: true)
dAlwaysAdjustLocalsColumnWidths: false  (default: false)
dMaximalStringLength: 1  (default: 1)
dListSourceFiles: false  (default: false)
dSkipKnownFrames: false  (default: false)
dEnableReverseDebugging: false  (default: false)
dAllPluginBreakpoints: true  (default: true)
dSelectedPluginBreakpoints: false  (default: false)
dAdjustBreakpointLocations: true  (default: true)
dAlwaysAdjustBreakpointsColumnWidths: false  (default: false)
dNoPluginBreakpoints: false  (default: false)
dSelectedPluginBreakpointsPattern: .*  (default: .*)
dBreakOnThrow: false  (default: false)
dBreakOnCatch: false  (default: false)
dBreakOnWarning: false  (default: false)
dBreakOnFatal: false  (default: false)
dBreakOnAbort: true  (default: false)  ***
dAlwaysAdjustRegistersColumnWidths: false  (default: false)
dAlwaysAdjustSnapshotsColumnWidths: false  (default: false)
dAlwaysAdjustThreadsColumnWidths: false  (default: false)
dAlwaysAdjustModulesColumnWidths: false  (default: false)
dShowQmlObjectTree: true  (default: true)
dQmlInspector.ShowAppOnTop: false  (default: false)
dState changed from DebuggerNotReady(0) to EngineSetupRequested(1) [master]
dQUEUE: SETUP ENGINE
dCALL: SETUP ENGINE
dTRYING TO START ADAPTER
dENABLING TEST CASE: 0
dSTARTING C:\Qt\qtcreator-gdb-7.4-MINGW32_NT-6.1-i686\gdb-i686-pc-mingw32.exe 
-i mi --tty=\\.\pipe\creator-1120-2149
dGDB STARTED, INITIALIZING IT
28show version
29show debug-file-directory
30set print object on
31set breakpoint pending on
32set print elements 1
33set overload-resolution off
34handle SIGSEGV nopass stop print
35set unwindonsignal on
36set width 0
37set height 0
38-interpreter-exec console set remotecache on
39-interpreter-exec console maintenance set internal-warning quit no
40-interpreter-exec console maintenance set internal-error quit no
dTHE FOLLOWING COMMAND CHECKS AVAILABLE FEATURES. AN ERROR IS EXPECTED.
41-interpreter-exec console disassemble 0 0
sSetting up 

[Qt-creator] msysGit fetch problem

[André Hartmann]

Hello List (especially Git experts),

I have a problem with Qt Creator 2.7.0 under Windows 7 64 Bit and Git 
1.8.1.msysgit.1.

When accessing our local Gerrit server with the Gerrit Dialog, Creator 
hangs on  Apply at the following command:

09:08 Executing in X:\S12X\KernelLibrary: C:\Program Files 
(x86)\Git\bin\git.exe fetch 
ssh://j...@gerrit.iseg.local:29418/KernelLibrary refs/changes/70/70/9

trace: built-in: git 'fetch' 
'ssh://j...@gerrit.iseg.local:29418/KernelLibrary' 'refs/changes/70/70/9'

trace: run_command: 'ssh' '-p' '29418' 'j...@gerrit.iseg.local' 
'git-upload-pack '\''/KernelLibrary'\'''

It seems ssh can't find the correct key, although the Options checkbox 
Set HOME is set.

On the Windows Command Line with HOME manualy set it works:

X:\S12X\KernelLibraryC:\Program Files (x86)\Git\bin\git.exe fetch 
http://gerrit.iseg.local/KernelLibrary refs/changes/68/68/1
trace: built-in: git 'fetch' 'http://gerrit.iseg.local/KernelLibrary' 
'refs/chan
ges/68/68/1'
trace: run_command: 'git-remote-http' 
'http://gerrit.iseg.local/KernelLibrary' '
http://gerrit.iseg.local/KernelLibrary'
trace: run_command: 'rev-list' '--objects' '--stdin' '--not' '--all' 
'--quiet'
trace: run_command: 'fetch-pack' '--stateless-rpc' '--stdin' 
'--lock-pack' '--th
in' 'http://gerrit.iseg.local/KernelLibrary/'
trace: built-in: git 'fetch-pack' '--stateless-rpc' '--stdin' 
'--lock-pack' '--t
hin' 'http://gerrit.iseg.local/KernelLibrary/'
remote: Counting objects: 21, done
remote: Finding sources: 100% (12/12)
trace: run_command: 'unpack-objects' '--pack_header=2,12'
remote: Total 12 (delta 9), reused 12 (delta 9)
trace: built-in: git 'unpack-objects' '--pack_header=2,12'
Unpacking objects: 100% (12/12), done.
trace: run_command: 'rev-list' '--objects' '--stdin' '--not' '--all'
trace: built-in: git 'rev-list' '--objects' '--stdin' '--not' '--all'
 From http://gerrit.iseg.local/KernelLibrary
  * branchrefs/changes/68/68/1 - FETCH_HEAD

More interesting, Creators Git Pull works fine:

14:31 Executing in X:\S12X\KernelLibrary: C:\Program Files 
(x86)\Git\bin\git.exe pull

 From ssh://gerrit.iseg.local:29418/KernelLibrary

5c3ed45..7c6974b master - origin/master

Updating 5c3ed45..7c6974b

Fast-forward
[]
24 files changed, 2522 insertions(+), 370 deletions(-)

We have at least two other systems that are working, but on this PC 
something is very strange.

Any ideas welcome.

Best regards,
Andre

PS: The Git timeout doesn't seem to work for Gerrit fetch, should I 
create a bugreport?
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] C/C++ parser and pre-included headers

[André Hartmann]

Hi,

regarding your Include-File: every Generic Project has a Project.config 
file, in which you can add defines for Qt Creator.

Maybe there is a chance to let this file beeing a link to your include 
file, or otherwise, move the global definitions to the Project.config 
and -include this one to your compiler.

Regarding the slow parsing: I'm pretty sure I heard this from other 
people before, maybe there is already a bugreport. I think the most 
helpful information would be the project source code, in case you can 
publish it ;)

Am 05.04.2013 03:54, schrieb hatred:
 Hi All!

 Some compilers can declare header file(s) that will be pre-included to
 all sources before compile. For example GCC has option -include file
 for this purposes. Our project uses this ability to declare some
 macroses, types, functions and so on (big embedded project).

 I use QTC to edit and refactoting code (Generic Project) and found, that
 some macrosses can't be recognized by QTC while our pre-compiled file
 does not included manually. So, my question: Does any way to point this
 pre-included files for QTC parser?

 And another question but regard parsing.
 Currently I use QTC 2.6.2 on WinXP (32bit) it require about 20 min to
 parse our project (some classes does not recognized but in most cases it
 works). I tried to migrate to 2.7.0 and found that parsing break
 totally: I tried to wait for a two hours, but parsing still reports a
 zero progress. So my question: Does any way to turn on parsing
 debugging? What file currently processing. How much files already
 processed and total files count. Parsing errors and warnings and so ons.
 I want fill a bug report, but I don't see what helpful information I can
 provide...


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


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

Re: [Qt-creator] Unable to write composed characters

[André Hartmann]

This works perfectly for me both in Windows XP (Creator 2.6) and Ubuntu 
Linux (Creator 2.4).

* Which Creator Version are you using?
* Which Operating System (and Desktop Environment)?

Regards,
André

  I am unable to write composed characters in Qt Creator.  For example,
 when I want to write:

 á

 In all other programs I press these two keys in succession:

 'a

 That gets me an á.  But in Qt Creator that doesn't work.  As soon as I
 press the ' key, it immediately appears on screen.  So instead of á, I
 get 'a.  Is there a setting I'm missing?  If there is, I'm unable to
 find it.

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


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

[Qt-creator] pp-macro-expander.h missing?

[André Hartmann]

Hello,

with latest master I get the following compile error:

make[3]: *** No rule to make target 
`../../../../qt-creator/src/libs/cplusplus/pp-macro-expander.h', needed 
by `.obj/debug-shared/cppcurrentdocumentfilter.o'.  Stop.

Any hints?

André

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

Re: [Qt-creator] Qt-Creator doesn't take into account my settings

[André Hartmann]

Hello,

I think there should be at least a hint in Tools - options - Text 
Editor, that these settings are NOT for C++ and QML.

In my opinion, the Documentation is quite good (much better than many 
other software), but users tend to not read them ... ;)

By the way: a Tip of the day or Did you know in the welcome screen 
might be a good idea with Creators increasing functionality (I think in 
former times there was already such a function)

André

 Hello,

 We attempt to explain the options you have in the documentation:

 http://doc.qt.nokia.com/qtcreator-2.4/creator-indenting-code.html

 Can you take a look and see if the documentation is helpful? If not,
 what kind of information would you like to have added? I'm updating the
 docs to 2.5 right now and could try to improve the instructions.

 Leena

 *From:*qt-creator-bounces+riitta-leena.miettinen=nokia@qt-project.org 
 [mailto:qt-creator-bounces+riitta-leena.miettinen=nokia@qt-project.org]
 *On Behalf Of *ext Gilles Habran
 *Sent:* Friday, March 23, 2012 7:30 AM
 *To:* qt-creator@qt-project.org
 *Subject:* [Qt-creator] Qt-Creator doesn't take into account my settings

 Good morning,

 It's been a while since I used Qt Creator and I gave it another try
 yesterday. My computer is running ArchLinux 64bits and qtcreator 2.4.1-1.

 I'm used to have 3 spaces instead of tab so I tried to configure that in
 Qt Creator :

 Tools - options - Text Editor -

 Tab policy : spaces only, tab size 3, indent size 3

 Even in FakeVim (even if use FakeVim is unchecked)... just to be sure.

 Unfortunately, when I press Tab, I have the default number of spaces : 2.

 I tried to change to a bigger number like 6 spaces but it doesn't work
 either... I even tried to reboot, nothing changed.

 Can someone tell me what I'm doing wrong ?

 Thank you.

 Kind regards,

 GH



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


-- 
Best regards / Mit freundlichen Grüßen
André Hartmann, Dipl.-Ing. (FH)
Software Project Manager

iseg Spezialelektronik GmbH |  phone: ++49 (0)351 26996-43
Bautzner Landstr. 23|  fax:   ++49 (0)351 26996-21
D-01454 Radeberg / Rossendorf   |  web:   www.iseg-hv.com

Geschäftsführer / Managing director: Dr. F. Gleisberg, Dr. J. Pöthig
Amtsgericht / Lower district court: Dresden HRB 16250
Ust.-Id.-Nr. / VAT-ID: DE812508942

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte
sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator