From: "Jan D." <jan.h.d@swipnet.se>
Date: Sun, 25 Jan 2015 10:17:20 +0100
Fixed, but it would be nice to know why this function needs input blocked.
This was there since day one, according to the history. Unless Kim,
who wrote it (CC'ed), can recollect why he put the assertion there,
I'm afraid the reason is lost in time. My wild guess would be that
the reason is this function calls X APIs to actually draw stuff, and
many of those block input. Perhaps Kim wasn't sure whether input
should be blocked here.
If no other information emerges, my suggestion would be to remove the
assertion on master, and see if we get any bug reports.