I updated the ScreenInformation class to stop caching the screen boundings. The caching caused issues when a saved dialog position is on an (now) invisible screen area (say when an second monitor/beamer is disconnected).

There was a note in the commit log from 2008 that there is a performance issue when obtaining the bounds on Windows. This perf issue only occurs on Java 5, and as we ship with Jitsi with a private JRE6 on Windows there is no longer an issue.
If you however notice a performance penalty under another OS, please drop me a message.

I updated the ScreenInformation class to stop caching the screen
boundings. The caching caused issues when a saved dialog position is
on an (now) invisible screen area (say when an second monitor/beamer
is disconnected).

Great, I was getting tired of the issue myself. Thanks for looking into
it. Twinscreen users: let us know if this adds (or resolves) any issues
for you.

There was a note in the commit log from 2008 that there is a
performance issue when obtaining the bounds on Windows. This perf
issue only occurs on Java 5, and as we ship with Jitsi with a private
JRE6 on Windows there is no longer an issue.

For the record

"We ship with J6 on Windows" != "We don't care about J5 any more"

That said, I am not so sure there was indeed a significant performance
penalty to begin with. Will try to test one of these days.

There was a note in the commit log from 2008 that there is a
performance issue when obtaining the bounds on Windows. This perf
issue only occurs on Java 5, and as we ship with Jitsi with a private
JRE6 on Windows there is no longer an issue.

For the record
"We ship with J6 on Windows" != "We don't care about J5 anymore"

Well, my understanding from our last discussion was that expecting J6 on Windows (and Windows only) is ok?

That said, I am not so sure there was indeed a significant performance
penalty to begin with. Will try to test one of these days.

There is indeed a huge penalty with J5 on Windows. Querying all screen resolutions lasts for about 10 seconds (J5, Win7_64). But I doubt that other platforms ever had such a problem.

There was a note in the commit log from 2008 that there is a
performance issue when obtaining the bounds on Windows. This perf
issue only occurs on Java 5, and as we ship with Jitsi with a private
JRE6 on Windows there is no longer an issue.

For the record
"We ship with J6 on Windows" != "We don't care about J5 anymore"

Well, my understanding from our last discussion was that expecting J6 on Windows (and Windows only) is ok?

Is the new code running on Windows only?

That said, I am not so sure there was indeed a significant performance
penalty to begin with. Will try to test one of these days.

There is indeed a huge penalty with J5 on Windows. Querying all screen resolutions lasts for about 10 seconds (J5, Win7_64). But I doubt that other platforms ever had such a problem.

OK, I'll try to check it out one of these days (unless anyone else beats
me to it).