PuTTY wish do-text-splitting

summary: Frontends need control over where do_paint() splits runs
class: wish: This is a request for an enhancement.
difficulty: tricky: Needs many tuits.
priority: medium: This should be fixed one day.

Currently, the way that do_paint() decides where to split the text runs it passes to do_text() is rather ad hoc and messy. It splits whenever there is a change to the "attributes" of the characters (subject to term->attr_mask), which includes any changes to the high-order byte of the character codes. It also splits around characters in the U+23BA–U+23BD range because the Windows front-end needs this.

It seems to me (BJH) that we could do with some way for the front end to inform the run-splitting code, so that do_paint() could put in splits where the front end needs them, and not put in spurious splits where it doesn't. I don't yet have any clear idea how this should work, though.

Audit trail for this wish.

If you want to comment on this web site, see the Feedback page.
(last revision of this bug record was at 2004-11-16 15:27:00 +0000)