Hi, I believe we can address the polling and cursor problems in LyX under DRT by identifying a user action as follows:
* an X input determines the start of an action (e.g., key press) * a burst of X outputs (e.g., screen draw requests) determine the end of the action (e.g., show the corresponding letter on the screen) This way, frequent polling that doesn't update the screen will not extend an action indefinitely. Of course, if certain actions do not result in the screen being updated for long periods of times, then we will not identify their ends. Is this an issue in LyX? Do all actions result in some screen output relatively quickly? BTW, we have written a paper on DRT that uses LyX as a running example. See: http://www.cse.unsw.edu.au/~amichail/drt.pdf Feedback would be appreciated! We should be able to release a preliminary version of this tool + full instructions for getting LyX to work later this week. Amir
