inconsistant find dialog scope when text selected

[ScottMattes]

PLSD v 10.0.5.1710

I am noticing that when there is text selected and the Find Dialog comes up, sometimes the radio button for Scope = Selection is checked and sometimes it is not.

Using the following text in a new SQL Window:

SELECT something
INTO some_var
FROM a_table
WHERE c1 = c2
AND c3 > SYSDATE - 3;
-- a comment
SELECT OTHERS
FROM table_b
WHERE SYSDATE <> SYSDATE;

selecting from 'a_table' through '=' and doing ctl-f shows scope = global

so, selecting from 'into' through the end of the line 'others' and ctl-f still shows scope = global. extend the search to include 'from ' and now ctl-f switches to scope = selection. contract the text selected by just one character and ctl-f goes back to scope = global.

I personally feel that if any text is selected then the scope should equal selection.

thank you.

 

[Marco Kalter]

If a limited amount of text is selected, it does not make sense to use it as the scope. It is used as the default search text instead.

If a lot of text is selected, it does not make sense to use it as the default search text. It is used as the scope instead.

 

[ScottMattes]

I understand the reasoning.

I think that the cutoff between limited and a lot is a matter of opinion.

to me, any selected text that contains a CR and/or LF should cause Scope = Selection.

Just an opinion.

I do not think that the cutoff between how much text is Scope = Global or Selection is spelled out in the documentation.

Thank you.