Le 10/05/2018 à 19:29, Scott Kostyshak a écrit :
On Thu, May 10, 2018 at 05:25:22PM +0000, Jean-Marc Lasgouttes wrote:
I see it now. Not sure what to do about it, though.
No problem, thanks for taking a look. I doubt it bothers anyone else. I
was thinking we might already have a mechanism for delaying the screen
refresh in such cases.
We have setBusy (true/false), but I do not know what would be the
consequence of setting it around a command-sequence call. You could try
that, but I fear that the sequence will not be able to call interactive
calls like file-open anymore.
JMarc
