Hi,
I normally have 3-5 concurrent SQuirreL sessions open to various schemas.
When I upgraded from 1.2beta5 to version 2.0 a couple months back, I started
to have a lag when switching from one session to another. In 1.2beta5,
clicking in a different panel would switch to that session instantly, like
clicking into a different window to switch applications at the system level.
After upgrading, there was a 3-4 second lag before the new panel became
active -- not a crippling problem, but annoying. This occurs when directly
clicking a panel or using the "Active Session" drop-down. I've switched to
version 2.1 today; my perception is that it is a little faster in this
regard (although I didn't put a stopwatch on either version), but still a
couple seconds to activate a panel.
Does anyone else see this, or have an explanation ?? I've wondered if there
is some behind the scenes monitoring going on, to keep code completion and
other options up to date. BTW, I had switched to 1.2beta6 quite a while
back, but saw similar (or the same) issues; I eventually was interested
enough in code completion that I was willing to take the delay.
Thanks for the advice,
Mark
|