Thu, 17 Jan 2019 09:28:12 +0000 Fix display of "no source code available" message in source view
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 17 Jan 2019 09:28:12 +0000] rev 133
Fix display of "no source code available" message in source view
Tue, 01 Jan 2019 23:46:41 +0000 UX: add initial support for command completion in simple console
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 01 Jan 2019 23:46:41 +0000] rev 132
UX: add initial support for command completion in simple console ...that does not use PTY (which is not always available). This support uses (new) MI command `-complete`.
Fri, 14 Dec 2018 11:41:47 +0000 Improve `--gdb` command line option handling
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 14 Dec 2018 11:41:47 +0000] rev 131
Improve `--gdb` command line option handling ...to allow user to specify (shell) command to launch GDB. In some cases (like when gdb is launched on remote machine through SSH), we cannot use UNIX PTYs to have native GDB CLI console. For cases like this, introduce new `--no-pty` option to force VDB to use emulated console even if current platform supports PTY (using PTY when available is preferred).
Fri, 14 Dec 2018 10:31:13 +0000 Fix: bug in simple console causing output being lost
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 14 Dec 2018 10:31:13 +0000] rev 130
Fix: bug in simple console causing output being lost For some reason, output that did not fit to visible area was removed. The problem was in `#doCursorDown:` being called multiple times for multi-line output. For some reason it removes lines from the begining. The problem seems to be that rangeEndLine (number of pending lines) was not updated after a line was printed. Though it seems right to fix this in `TerminalView`, for real usage where output is taken from TTY it somehow works. To be on a safe side (for now) fix it only in `VDBSimpleDebuggerConsoleView`. We will see...
Thu, 13 Dec 2018 14:58:49 +0000 Fix: catch-up with `jv:libgdbs` after a rename of `#gdbExecutable`
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 13 Dec 2018 14:58:49 +0000] rev 129
Fix: catch-up with `jv:libgdbs` after a rename of `#gdbExecutable` ...to `#gdbCommand``
Thu, 13 Dec 2018 14:56:29 +0000 Fix: use `VDBUnixDebuggerConsoleApplication` only when GDB's process is a UNIX process
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 13 Dec 2018 14:56:29 +0000] rev 128
Fix: use `VDBUnixDebuggerConsoleApplication` only when GDB's process is a UNIX process ...having separate streams for CLI console (usually a PTY). This is to handle cases when `GDBStXSimpleProcess` is used even if VDB runs on UNIX systems.
Wed, 12 Dec 2018 16:35:20 +0000 Renamed `VDBWindowsDebuggerConole*` to `VDBSimpleDebuggerConsole*`
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 12 Dec 2018 16:35:20 +0000] rev 127
Renamed `VDBWindowsDebuggerConole*` to `VDBSimpleDebuggerConsole*` as ot may be used on other scenarios than running on Windows, for example when GDB is run on remote machine through SSH or when using generic `GDBRemoteProcess`.
Wed, 28 Nov 2018 14:08:58 +0000 UX: reflect font size in in `VDBMemoryApplication`
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 28 Nov 2018 14:08:58 +0000] rev 126
UX: reflect font size in in `VDBMemoryApplication`
Sun, 28 Oct 2018 14:34:08 +0000 Catch up with removal of `GDBOutputFormats` pool in `jv:libgdbs`
Jan Vrany <jan.vrany@fit.cvut.cz> [Sun, 28 Oct 2018 14:34:08 +0000] rev 125
Catch up with removal of `GDBOutputFormats` pool in `jv:libgdbs`
Mon, 08 Oct 2018 08:24:14 +0100 Send `#updateAfterVisitiblityChanged` to an application when visibility of its window changes
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 08 Oct 2018 08:24:14 +0100] rev 124
Send `#updateAfterVisitiblityChanged` to an application when visibility of its window changes Such as when the application is in a tab which is not visible and become visible or the other way round. This can be used by applications to suppress (expensive) updates when contents is not visible.
(0) -100 -10 +10 +100 tip