Apr 2, 2025
Qt 6.9 Released
Qt 6.9 is now available, with new features and improvements for..
Apr 1, 2025
New Online Exploring Experience Launched!
We have been busy working on a totally new way to explore the world of Qt,..
Mar 31, 2025
Qt for MCUs 2.10 Out Now!
Qt Group is pleased to announce Qt for MCUs 2.10, a release packed with..
Commenting for this post has ended.
Remarks/issues:
1) Clicking on any menus or at the different panes at the left or bottom , it takes quite some time to show.
Big issue.
2) After 3.3.2, using gdb 7.9.1 with qtcreator is broken. Same with this version:
Debugging starts
Debugging has failed
Debugging has finished
....
....
Warning: State changed from EngineSetupFailed(2) to DebuggerFinished(22) master
Warning: (gdb) (no active run control)
Warning: QUIT DEBUGGER REQUESTED IN STATE 22 (no active run control)
Warning: 16^done (no active run control)
Warning: (gdb) (no active run control)
Linux red hat 6 x86_64
Probably creating a bug report on https://bugreports.qt.io is a better option.
Very nice. I love and I've been using Qt Creator for several years now. Thanks for the fabolous work!
Some months ago a mock-up for a new UI flat design has been shown. Is that project still going? Which are the plans for the release of the new UI? I felt in love with the new design, the icon consistency and the general look and I'm impatient to use it.
Will somebody please fix this bug properly? https://bugreports.qt.io/br...
The project explorer after this "fix" has become all but unusable, at least as far as i'm concerned i can, and will, no longer update Creator until this is fixed, it's just unusable anymore.
awesome - thx, for all the hard work!
Are you aware that Qt Creator has multiple issues? At least on Windows it is possible that it crashes within minutes (OpenSource and Enterprise version) (FTH disabled). I counted about 50 crashdumps until I gave up on your software and went to CLion. I'm under the impression (but not sure, because I could not track down a specific reason for this behaviour) that using the VIM emulation, following virtual methods, or just using the class hierarchy let QtCreator die. I think It crashes in most cases with an MSVCR120.dll error, while parsing the source code. A package of QtCreator with debug symbols would be appreciated very much. It is also strange that 3 of my colleagues have the same issues with QtCreator while another does not encounter this behaviour.
Any thoughts of leveraging a tool like Crashpad (https://code.google.com/p/c...) to monitor for crashes? I semi-recently switched from Breakpad to Crashpad which now silently reports all caught crashes. While we do our best to address issues by looking at the call stacks, I'm increasingly under the impresssion that the vast majority of crashes we're not getting are due to bugs in Qt. I have yet to include Qt symbols on your crash server so I can't completely back up that claim other than the lack of symbol data for a large number of reported crashes. Qt Creator could serve as a great way for Digia to monitory for quality issues in Qt itself without depending on developers to actually report crashes.