You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using colorama (or pyreadline) for colored ANSI text on Windows somehow interferes with (or hijacks/disables/supercedes) the wx input-hook that allows wx Widgets (like plotting) to be responsive and interactive from the command line.
This needs investigation, and may be non-trivial. For example, I think that IPython somehow manages to solve this (and uses pyreadline to get a replacement StdOutput.... hmmm).
For the time being, color output should be suppressed from the Windows command terminal, as interactive widgets are more important. It also emphasizes that the new support for color should be translated and supported in the wxLarch GUI (which is a reasonable alternate to the command line on Windows).
The text was updated successfully, but these errors were encountered:
Weird but True:
Using colorama (or pyreadline) for colored ANSI text on Windows somehow interferes with (or hijacks/disables/supercedes) the wx input-hook that allows wx Widgets (like plotting) to be responsive and interactive from the command line.
This needs investigation, and may be non-trivial. For example, I think that IPython somehow manages to solve this (and uses pyreadline to get a replacement StdOutput.... hmmm).
For the time being, color output should be suppressed from the Windows command terminal, as interactive widgets are more important. It also emphasizes that the new support for color should be translated and supported in the wxLarch GUI (which is a reasonable alternate to the command line on Windows).
The text was updated successfully, but these errors were encountered: