Toad World® Forums

FILE OPEN problem with Toad 10.1


#1

When you open a file in the editor it will open it in a tab and remember the
extension. If I try to open another file it will only show files with that same
extension. I would like it to always show all .SQL, .PKB, .PKS, .FNC and .PRC. I
have not found an option for that.

You do have categories for that. There is the PL/SQL category. But once you
chose a file it uses that extension rather than the category extensions.


#2

Glad you brought that up Erwin … this bugs me too.

ian


#3

I am not sure that I follow. I launch the Open File dialog and select a .SQL
file. The file opens in a new tab. I click the Open File button again and in the
dialog the filter dropdown is set to PLSQL, the filename edit is blank, and the
file browser listview shows all files matching the filter. I see .SQL and .PKB
files in my test. What exactly are you seeing?

Michael


#4

Here is my scenario


#5

Here is my scenario
image001.jpeg


#6

Here is my scenario


#7

So instead of it remembering the type of file you opened previously you want it
to always stay at the PLSQL* level?


#8

So instead of it remembering the type of file you opened previously you want it
to always stay at the PLSQL* level?


#9

YES. Because I will be opening SQL, PKB, PKS, files. I don’t want to start
a separate window for each type of object. If nothing else, PKB and PKS should
be always be shown together.


#10

YES. Because I will be opening SQL, PKB, PKS, files. I don’t want to start
a separate window for each type of object. If nothing else, PKB and PKS should
be always be shown together.
image001.jpeg


#11

YES. Because I will be opening SQL, PKB, PKS, files. I don’t want to start
a separate window for each type of object. If nothing else, PKB and PKS should
be always be shown together.


#12

PKB and PKS make sense to have together, but you can always just change the file
type drop down as needed, right?


#13

PKB and PKS make sense to have together, but you can always just change the file
type drop down as needed, right?


#14

Yes. But that requires extra effort.

Now that we have much wider monitors I would have no problem with two OPEN FILE
icons.

One could be the current OPEN FILE (meaning open same as previous)

The other could be OPEN PLSQL

This way no OPTION to change. Just two choices. I can even live with having to
do a CUSTOMIZE MENU to get and drag that second OPEN PLSQL icon to the icon bar.


#15

Yes. But that requires extra effort.

Now that we have much wider monitors I would have no problem with two OPEN FILE
icons.

One could be the current OPEN FILE (meaning open same as previous)

The other could be OPEN PLSQL

This way no OPTION to change. Just two choices. I can even live with having to
do a CUSTOMIZE MENU to get and drag that second OPEN PLSQL icon to the icon bar.
image001.jpeg


#16

Yes. But that requires extra effort.

Now that we have much wider monitors I would have no problem with two OPEN FILE
icons.

One could be the current OPEN FILE (meaning open same as previous)

The other could be OPEN PLSQL

This way no OPTION to change. Just two choices. I can even live with having to
do a CUSTOMIZE MENU to get and drag that second OPEN PLSQL icon to the icon bar.


#17

Ok, this has come up before. It has been quite some time since investigating it,
but I seem to remember a couple of key points and roadblocks that prevent fixing
it at this time. I’ll list them out even though you know most of this
already from observation.

We set the last used file extension, FNC in your case
We unfortunately (and probably incorrectly) have multiple filters that
include the FNC extension
Windows Common Dialogs search through the filters, in order, until one is
found that contains the extension and uses that filter
Toad has a predefined set of filters for the common dialogs and PLSQL is one
of many and happens to appear below some of the other PLSQL object filters
The list of filters (Options à Files à General) can’t be reordered
and the predefined filters can’t be deleted
We have no way of obtaining the last used filter index from the common
dialog, just extension of the last opened file

One proposition from back in the day was to retain the last used filter and not
last used extension, but we can’t do this because of 6 above. This would
be ideal, but as far as I know still not possible.

Another way to “fix” it would be to ship with a predefined filter
list, but give you complete control over reordering or even removing those
filters with a restore defaults option so that you can nuke all of the
individual PLSQL object type filters or at least push PLSQL to the top.

For now you can do the following which should work. Edit the filters for the
PLSQL object types that are listed above PLSQL (function, java, java source,
package, and package body) so that those filters look for a bogus extension,
.aaa for instance. This should cause your case below to always go to the PLSQL
filter, but means that the modified filters are now useless.

Michael
image003.jpeg


#18

Ok, this has come up before. It has been quite some time since investigating it,
but I seem to remember a couple of key points and roadblocks that prevent fixing
it at this time. I’ll list them out even though you know most of this
already from observation.

We set the last used file extension, FNC in your case
We unfortunately (and probably incorrectly) have multiple filters that
include the FNC extension
Windows Common Dialogs search through the filters, in order, until one is
found that contains the extension and uses that filter
Toad has a predefined set of filters for the common dialogs and PLSQL is one
of many and happens to appear below some of the other PLSQL object filters
The list of filters (Options à Files à General) can’t be reordered
and the predefined filters can’t be deleted
We have no way of obtaining the last used filter index from the common
dialog, just extension of the last opened file

One proposition from back in the day was to retain the last used filter and not
last used extension, but we can’t do this because of 6 above. This would
be ideal, but as far as I know still not possible.

Another way to “fix” it would be to ship with a predefined filter
list, but give you complete control over reordering or even removing those
filters with a restore defaults option so that you can nuke all of the
individual PLSQL object type filters or at least push PLSQL to the top.

For now you can do the following which should work. Edit the filters for the
PLSQL object types that are listed above PLSQL (function, java, java source,
package, and package body) so that those filters look for a bogus extension,
.aaa for instance. This should cause your case below to always go to the PLSQL
filter, but means that the modified filters are now useless.

Michael
image004.jpeg


#19

Can you perhaps improve the process at step #1? Have an option “Remember
last-opened file type”, checked by default, such that when NOT checked you
simply don’t set the last-used-file-extension (and clear it if it was set
earlier in the session). What would Windows Common Dialogs then use for a
filter?

Nate Schroeder

IT Commercial Technical Services - Data Management Team

Monsanto Company

800 N. Lindbergh Blvd. G3WI - Saint Louis, MO - 63167

314-694-2592
image003.jpeg


#20

Can you perhaps improve the process at step #1? Have an option “Remember
last-opened file type”, checked by default, such that when NOT checked you
simply don’t set the last-used-file-extension (and clear it if it was set
earlier in the session). What would Windows Common Dialogs then use for a
filter?

Nate Schroeder

IT Commercial Technical Services - Data Management Team

Monsanto Company

800 N. Lindbergh Blvd. G3WI - Saint Louis, MO - 63167

314-694-2592
image004.jpeg