Sorry they didn’t go with your proposal. When I click on a tab, or button I
want something to happen NOW, not 3 seconds from now. I know that as a developer
it’s always a compromise between features and performance. I would gladly
sacrifice many of the window style options for performance.
Eye candy, of course, helps sell a product, but when resizing the window takes
literally 5 seconds then ( add your explicative here).
I’m on 10.6. Looking forward to Toad 11 !
On Thu, May 5, 2011 at 10:25 AM, Michael Staszewski <
firstname.lastname@example.org > wrote:
Performance problems when changing tabs will persist forever as long as we
remain in a multi-tab style, multi-desktop Editor mindset. I proposed (and
implemented) an alternative early in the Toad 11 cycle, but the consensus
was to keep the current design even if it is less efficient and more
resource intensive. Performance under the proposed change was incomparable
to earlier versions. I could load > 400 tabs without error and I forget the
exact stats, but something like 60 or 80 files in less than 20 seconds.
Depending on what version you are on you can expect to see better
performance by upgrading to the latest. Toad 11 should be better than Toad
10.6 in this area too so if you are able to check out the beta then go for
it. I think that performance gains would be most visible with a fair
amount of higher quality, faster RAM and multi-core CPU. Toad isn't a
graphics intensive application so the graphics issues are likely a
combination of less than stellar code in this area of the product and the
intensity of the code required to manage the various tab styles.