out of source page.

complain.

Added a Q_ASSERT to the case that shouldn't happen.

StartOfLine/StartOfBlock. Eventually we want to switch all that to
actions, so we can have unix-style input also on the mac and vice versa
by setting different keybinding schemes.

Default to the baseName() of the .pro file.

sessionUnloaded was sometimes emitted when the session manager was in
an unsafe state (between delete m_file and  m_file = new ...) leading
to crashes when slots connected to the signal accessed the sessionmanager
again. This patch moves the signal emission before  delete m_file.

Reviewed-by: dt

The code was already there, but disabled as it led to a crash during
Creator startup due to a spurious "sessionUnload" emission.

Reviewed-by: dt

Show the current number base in the view.

Just mentioning it in the status bar is often not enough to take notice.

anchors.centeredIn has become anchors.centerIn

When trying to debug qmake or another bootstrapped application loading the
dumpers failed as they are binarily incompatible. So failing is expected and
fine. However, gdb 6.8-debian produces in this case _two_ responses for
'-exec-continue produces' ('^running' and '^error,msg="Cannot find new threads:
generic error"') which is impossible according to the MI docs. In theory...

jom can be found at http://qt.gitorious.org/qt-labs/jom



Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>

INT_MAX needs limits.h

Consistent with the way the summary is written.

Task-Nr: 259513

... by storing the children information in an additional watchdata
source bit, thus being able to prove the model wrong in case it
claims children are needed.

Fix "displayedtype" in CDB, display it elsewhere.
Log debugger settings in DebuggerManager startup.
Acked-by: hjk <qtc-committer@nokia.com>

Reviewed-by: hjk

add/remove.

This isn't a nice fix but the least evil version of a hack i could come
up. The source of the flickering is: We have a deeply nested structure
of widgets on the project pane. If we call hide() on such a deeply
nested widget, it will activate() it's parent layout synchronously.
That will then post an event (via updateGeometries() ) to its parent
layout that it needs relayouting. Which then will post to its parent
layout the same. And for each LayoutRequested, there's a painting in
between. The fix instead calls activate() up the chain until we are at
the viewport. This immediately relayouts everything. This adds a non
obvoius potentially for breakeage if the widgets are embedded in a
different widget hierarchy. But well, that's life.