- Apr 19, 2011
-
-
Friedemann Kleint authored
-
Christian Kandeler authored
This will also make it easier for us to initiate a re-exchange if we ever want to implement that.
-
Christian Kandeler authored
-
Christian Kandeler authored
-
Christian Kandeler authored
-
Christian Kandeler authored
Correct protocol-wise, but possibly buggy (fails with dropbear).
-
Friedemann Kleint authored
On Windows or if file is executable.
-
Friedemann Kleint authored
-
Tobias Hunger authored
Try to start debug listener if it is not yet running. This can happen when e.g. a external debug listener was closed in the meantime.
-
Tobias Hunger authored
-
Tobias Hunger authored
-
hjk authored
-
hjk authored
-
Friedemann Kleint authored
Remove MemoryViewWidget/RegisterMemoryViewWidget in favour of MemoryView/RegisterMemoryView based on the bin editor widget.
-
Friedemann Kleint authored
Add markup for displaying class layouts in the debugger. Add a factory registered with the plugin manager for creation of widgets by soft-dependent plugins.
-
Tobias Hunger authored
-
Tobias Hunger authored
Task-number: QTCREATORBUG-4589
-
Tobias Hunger authored
Get debug output for all GUI applications at once. This should stop the "Cannot retrieve debugging output". Task-number: QTCREATORBUG-4569
-
- Apr 18, 2011
-
-
Christiaan Janssen authored
Task-number: QTCREATORBUG-4451 Reviewed-by: Kai Koehne
-
Tobias Hunger authored
-
hjk authored
-
hjk authored
-
hjk authored
-
Oswald Buddenhagen authored
it was apparent only with qt 4.8
-
Oswald Buddenhagen authored
for one, entirely stop monitoring the own IFile. second, expect changes on the filename - in case other IFiles use it as well. these two ensure that nothing weird happens, especially if we show a dialog and thus enter an event loop.
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
there only two classes of files anyway: regularly editable ones which may ask for interaction, and "background" files which always operate silently. the regular case is the more complex one, so put that into the base class.
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
it's bogus. and the ProWriter will take care not to add stray empty lines now.
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
- use Utils::FileSaver - as a side effect, don't rewrite the desktop file with the same content if it already exists - pop up message boxes on errors - this is likely to be more visible than qWarning()s/nothing - this is implemented in a somewhat strange way with the model itself doing the gui interaction, but that seems to be the simplest solution given the qt class design
-
Oswald Buddenhagen authored
easier to handle errors that way
-
Oswald Buddenhagen authored
lots of use of Utils::FileSaver and Utils::FileReader Task-number: QTCREATORBUG-1619
-
Oswald Buddenhagen authored
add/unify read error handling in all affected classes
-
Oswald Buddenhagen authored
this centralizes error reporting (in fact, in most cases it adds any in the first place). Task-number: QTCREATORBUG-1619
-
Oswald Buddenhagen authored
-
Oswald Buddenhagen authored
no need to pass in the current file name
-
Oswald Buddenhagen authored
this replaces the ever-repeating idiom block/save/unblock with a single call.
-