RE: Re: Toad v11 Schema browser LH tab order wrong - bug
John Dorlon <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <4120B436C765EC43A31CC3E2A13D36A62255D197@ALVMBXW02.prod.quest.corp> |
Sorry, I missed your first post. It's a bug. This issue has made it to me through Quest Support, and it's fixed for the next beta. You might be able to work around it by going into the config screen, and moving all the non-visible SB tabs to the end of the order. From: [email protected] [mailto:[email protected]] On Behalf Of Boneist Sent: Tuesday, October 11, 2011 8:23 AM To: [email protected] Subject: [toad] Re: Toad v11 Schema browser LH tab order wrong - bug Message from: Boneist Am I the only one that's seeing this problem in v11? It's really irritating having to "configure" the tabs everytime *{:-( _______________________________________ Historical Messages Author: Boneist Date: Tue Oct 11 06:23:28 PDT 2011 Am I the only one that's seeing this problem in v11? It's really irritating having to "configure" the tabs everytime *{:-( __ Author: Boneist Date: Tue Oct 04 07:01:41 PDT 2011 Hi, This is a minor, but fairly irritating bug in v11. I've configured my schema browser to show the tabs (multi-lined) in the following order: Tables Views Packages Procedures Functions Triggers .... However, when I first launch the schema browser (which is my default window to launch when I open a new session) the order is as follows: Tables Views Procedures Packages Functions Indexes .... I right mouse click on the tab icon area and click configure, but the tabs are already listed in the right order. Clicking on ok then puts the tabs in the right order. I've tried closing the schema browser with the tabs in the right order and relaunching it, but that comes back with the wrong order again. I've even closed Toad down entirely (making sure that the last schema browser closed had the tabs in the right order) and relaunching, only for the tabs to still show up in the wrong order. Why are the settings not being applied when the schema browser is launched? Is it a bug, or is it something that I haven't got set right in the options?! This worked fine in v10.6. ETA: I've tried restoring the default order and then re-ordering and that didn't work - I still have the same issues with the ordering not taking effect until after I've opened up the config and clicked OK without amending anything. Message was edited by: Boneist __ _______________________________________