small color coding issue in TOAD 10.6.1.3

Hello,

This is a pretty small issue but bothered me enough to report it.

Recently the number of schemas I have to managed has about tripled with most
having the same names across several instances.

Seemed like a good idea to start creating a color scheme in the session
connection screen.

However, when I open a recovered document from a TOAD crash for which the parent
schema is not currently open, TOAD helpfully opens the schema but in the process
removes the color coding.

Thanks!

Paul

Evening Paul,

I'm only on 10.5 at the moment, so be gentle with me! :wink:

However, when I open a recovered document from a TOAD crash for which
the parent schema is not currently open, TOAD helpfully opens the schema
but in the process removes the color coding.

10.6 does this? I never knew. As far as I'm currently aware, when I've
had a crash, I do get the recovered files with no colour scheme but the
connection is not reconnected for me. I have to manually connect and
then attach the window to the connection with the "connection change"
button.

Now, I haven't had a Toad crash on me for a while so I may be wrong, but
I'm pretty sure that when I attach a windows to a connection, the colour
scheme changes to suit that of the connection that I've just attached it to.

Are you sure that Toad is actually re-connecting?

--
Cheers,
Norm. [TeamT]

Hi Norm - this was a feature inspired from the Pond

Evening Mark,

On 11/04/11 20:04, Mark Lerch wrote:

Hi Norm - this was a feature inspired from the Pond
I'm going to have to pay a lot more attention to the release details for
each new [beta]version I think!

Sounds like a good idea to m e, reconnecting - nice. Must get 10.6
installed at work ...... if I'm allowed!

--
Cheers,
Norm. [TeamT]

hi Paul - this had already been found and is fixed for Toad 11. thanks!