Custom Query (361 matches)
Results (25 - 27 of 361)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #24 | fixed | Replace current undo management with document-based undo mechanism | ||
| Description |
The current undo management code uses a long history of commands sent to the prover, then weeds through them to figure out which commands need undoing and how. This is tedious and will not support context switching. Currently there is no queue of undo commands but instead a thread is made for each undo command as one-by-one they are processed by the prover; this has very poor performance. The document itself has exactly the information needed to calculate undo commands, based on the processed position. Because the document locks the processed text, this is expected to be accurate. We can calculate a queue of commands for undoing just as we do when processing commands. This work has begun but amounts to a major reorganisation/extension of the document model. This ticket will be used to track progress. |
|||
| #28 | worksforme | Newlines in PGIP console are lost | ||
| Description |
Newlines in PGIP console (e.g. in parseresult) are lost. Hopefully these can be recovered from the document parse and are lost somewhere else. |
|||
| #36 | fixed | Split stream for console into input/output and give input a different colour. | ||
| Description |
A minor improvement for the PGIP console is to display input/output in different colours or fonts. This should be easy: message streams can have colour/fonts attached, so we just need to split PGIP stream into two. |
|||
