Setting the default shortcut may only set the current shortcut if that
has not already been set.

Frédéric Mercille (1):
      Setting the default key sequence should only set the current sequence
         if none is set. Otherwise, it overrides the user configuration in
         QtCreator.ini.

Request-url: http://gitorious.org/qt-creator/qt-creator/merge_requests/832


Reviewed-by: con <qtc-committer@nokia.com>

Done with Thorbjørn Lindeijer

A project's existing .pro file could be added to the project, making
the .pro file appear twice in the project tree. This is sub-optimal
because

1. It does not make sense for the .pro file to appear twice.
2. Qt Creator crashes when trying to remove either of the duplicate
.pro files.

Task: 254011

Task-number: 254695

and '?' ) in the french translation.

Setting the default key sequence should only set the current sequence if none is set. Otherwise, it overrides the user configuration in QtCreator.ini.

Merge-request: 827
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Reviewed-By: TrustMe

We don't really have any useful quickfix implemented so there's no reason
to waste time visiting the AST.

- std::set/map: Introduce templates to iterate the MSVC STL
  implementation depending on type (since it inherits some
  basic set_traits that depend on the key/value size.
- Retrieve types correctly in CDB (buffer too short for STL-types)
- Fix std::map in GDB broken by previous commit.
- Introduce a dumper version check in GDB/CDB.
- Make GDB parse sizes in initial dumper call as well
- Fix special sizes to work with namespaced Qt (watchutils)

Also cache a lastModified time, so that we don't emit a signal if it
didn't change.

If you call setVisible(true) on the item before it is placed in a
hierarchy, it will show as a normal top-level window. On some platforms
this isn't really an issue, but with Carbon, the show happens
immediately, so you get this flash of a window which is really
disturbing. I'm surprised it's not noticed on other platforms.
Personally, I'm not sure why we call this at all, but I'm leaving it for
the moment.

Reviewed-By: TrustMe

Rev-by: Oswald Buddenhagen <oswald.buddenhagen@trolltech.com>