I don't use quicklisp but do use github desktop to check on things. I found a bunch of changes yesterday and found that my hack of calling the display function for redisplay now works where before changes made to the display were computed but not shown on the screen. I had observed a lot of stuff in the output record cache that I could not account for which is now gone.Mind that recently I rewrote parts of the incremental redisplay to fix some issues - I'm not sure whether these changes are already propagated to quicklisp.
I had not even noticed that problem! Thanks for the info.btw when you draw the border it makes the window bigger with each iteration, because the line thickness is 1 and it is not filled, so drawing (x1 y1 x2 y2) actually covers the area (x1 y1 x2+1 y2+1).
That would be redisplay-frame-pane causing infinite recursion. I shall work something up.As of the second issue, could you supply a code that triggers the issue? Thanks!