Commit c7fa1a92 authored by Eike Ziller's avatar Eike Ziller
Browse files

Add changes file for 3.5

Start using (multi)markdown for it as well.

Change-Id: Ifa59eb29eaea859444e8eaf03954462744360032
Reviewed-by: default avatarLeena Miettinen <>
parent 5c4a025d
Qt Creator version 3.5 contains bug fixes and new features.
The most important changes are listed in this document. For a complete
list of changes, see the Git log for the Qt Creator sources that
you can check out from the public Git repository. For example:
git clone git://
git log --cherry-pick --pretty=oneline origin/3.4..origin/3.5
* Increased minimum requirements for compilation of Qt Creator to
MSVC 2013 and GCC 4.7, and Qt 5.4.0
* Added variants with native separators to Qt Creator variables that
represent file paths
* Changed the way inconsistent enabled states were handled by the
plugin manager. Disabling plugins is now only a hint; if another
(enabled) plugin needs it, it is implicitly enabled. Before, the
other plugin was implicitly disabled.
* Added `-load all` and `-noload all` command line options that
enable and disable all plugins respectively
* Made `-load` command line option implicitly enable all required
plugins, and `-noload` disable all plugins requiring the
disabled plugin. Multiple `-load` and `-noload` options are
interpreted in the order given on the command line.
* Added option to jump directly to specific column in addition to
line number when opening files through locator or command line
QMake Projects
CMake Projects
* Made it possible to register multiple CMake executables
* Fixed default shadow build directory name
Qbs Projects
QML-Only Projects (.qmlproject)
QML Profiler
* Made saving and loading trace data asynchronous to avoid
locking up UI (QTCREATORBUG-11822)
C++ Support
* Added separate icon for structs
QML Support
Version Control Systems
Platform Specific
* Added locator filter that uses Spotlight for locating files
Remote Linux
Credits for these changes go to:
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment