Feature #118
Threading and locking in the TUI
| Status: | Assigned | Start: | 08/26/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | 09/10/2010 | |
| Assigned to: |  Matthew Iselin |
% Done: | 0% |
|
| Category: | TUI | Spent time: | - | |
| Target version: | - | Estimated time: | 12.00 hours |
Description
The TUI should be updated to use the new pthread locking routines in order to handle input callbacks properly. Input callbacks should just push the key onto a queue and wake a Semaphore - which wakes a specific "input thread" that distributes the input to terminals as necessary.
The TUI also needs locking in a few areas which could be quite racy.
History
Updated by Matthew Iselin about 1 year ago
- Priority changed from Normal to Low
- Target version deleted (
Foster Post-Release Milestone #1)
Investigated this a bit more and it seems to be less of a problem now. The architecture of the TUI is also fairly complex to modify - likely with a variety of regressions.
Will look into this further, and weigh up the performance against the safety later.