|
From: Gerd W. <bir...@t-...> - 2006-01-15 12:08:48
|
Hi Mark,
sorry that my tests didn't show any effect. All I can say at the moment
is that your problem is not a common problem. At work more than 20
colleagues of mine are using SQuirreL on different Windows and Linux
versions and no one ever complained about 3-4 seconds for switching
between sessions.
I have seen that with some look and feels switching session windows is
faster than with others but by far not in the range of seconds. You
might though try a Metal look and feel.
The last thing I can offer is that you try out the little test class
below. It opens a Desktop window with four child windows
(JInternalFrames) with editor panes on each. If you can reproduce the
lag on this example I'm pretty sure it is a problem with your system.
Gerd
/////////////////////////////////////////////////////////
//
package pack;
import javax.swing.*;
public class InternalFrameTest
{
public static void main(String[] args)
{
JFrame f = new JFrame();
JDesktopPane desk = new JDesktopPane();
f.getContentPane().add(desk);
JInternalFrame jif;
jif = new JInternalFrame();
jif.getContentPane().add(new JEditorPane());
jif.setBounds(0,0,200,200);
jif.setVisible(true);
desk.add(jif);
jif = new JInternalFrame();
jif.getContentPane().add(new JEditorPane());
jif.setBounds(0,210,200,200);
jif.setVisible(true);
desk.add(jif);
jif = new JInternalFrame();
jif.getContentPane().add(new JEditorPane());
jif.setBounds(210,0,200,200);
jif.setVisible(true);
desk.add(jif);
jif = new JInternalFrame();
jif.getContentPane().add(new JEditorPane());
jif.setBounds(210,210,200,200);
jif.setVisible(true);
desk.add(jif);
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
f.setSize(500,500);
f.setVisible(true);
}
}
//
/////////////////////////////////////
Mark Neher wrote:
>
> Thanks for the quick response !! Regarding your suggestions:
>
> 1. I was and am using the NetBeans editor
>
> 2. I removed codecompletion.jar, restarted, and saw no change
>
> 3. I removed syntax.jar, restarted, and saw no change
>
> Thanks,
>
> Mark
>
>
>> From: Gerd Wagner <bir...@t-...>
>> To: Mark Neher <mar...@ho...>
>> CC: squ...@li...
>> Subject: Re: [Squirrel-sql-users] performance issues when switching
>> panels
>> Date: Fri, 13 Jan 2006 19:50:59 +0100
>>
>> Hi Mark,
>>
>> could you try out the following an tell me if one or more changes the
>> lag?
>>
>> 1. Check the New Session Properties if your are using the Netbeans
>> editor. If not please switch to it and try again.
>>
>> 2. Remove the codecompletion.jar from your plugin dir, restart
>> SQuirreL, and try again.
>>
>> 3. Remove the syntax.jar from your plugin dir, restart SQuirreL, and
>> try again.
>>
>> Thanks
>>
>> Gerd
>>
>> Mark Neher wrote:
>>
>>> 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
>>>
|
