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
We have a scaling delay parameter that depends on how long IPython has been idle. Currently it is a bit too long. We need to tweak these times and make them configurable.
The text was updated successfully, but these errors were encountered:
We have a scaling delay parameter that depends on how long IPython has
been idle. Currently it is a bit too long. We need to tweak these
times and make them configurable.
+1, they were actually bugging me during lecture recently.
Quick q: do we have similar scaling delays for qt? I couldn't find
any, but I'm not sure right now why...
[ LP comment 2 by: Brian Granger, on 2010-02-23 06:58:48+00:00 ]
1, they were actually bugging me during lecture recently.
Quick q: do we have similar scaling delays for qt? I couldn't find
any, but I'm not sure right now why...
Nope, the only reason we have to do this for wx is that wx does not
have the ability to trigger events when a file descriptor
gets a read/write event. Qt can do that and thus the eventhook runs
until the user types (that triggers stdin event).
On wx, on the other hand, we have to poll :( and hence the polling times.
Original Launchpad bug 526243: https://bugs.launchpad.net/ipython/+bug/526243
Reported by: ellisonbg (Brian Granger).
We have a scaling delay parameter that depends on how long IPython has been idle. Currently it is a bit too long. We need to tweak these times and make them configurable.
The text was updated successfully, but these errors were encountered: