Yes that is true for your first issue that both block and stream will
populate the find field, and as you said you can work around that. But you
may still want a setting to disable it or do something else?
However for what I wrote below, I am wondering if your second issue is
resolved when using block selection?
Thanks,
____________________________________________________________________________
Maha Masri
From: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 09/14/2015 03:28 PM
Subject: Re: [WDSCI-L] The problem with Finding what is selected
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Both block selection and stream selection are used to populate the find
field for ctrl-f.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----"Maha Masri" <masri@xxxxxxxxxx> wrote: -----
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
From: "Maha Masri" <masri@xxxxxxxxxx>
Date: 09/11/2015 11:15AM
Subject: Re: [WDSCI-L] The problem with Finding what is selected
One question, when running through the steps below, have you tried using
Block selection instead of Stream selection? That is, have you tried to
use Select line (Alt+L), character (Alt+B) or rectangle (Alt+R) instead of
using your mouse or the shift and arrow keys to select the source? Once
Block selected, I think that the steps below will work in that typing the
search term and pressing alt-a should NOT clear the selection and the
ctrl-f search term should be saved in the history.
1. select a block of source
2. do ctrl-f (make sure "Restrict search to selection is selected")
3. Type search term
4. alt-a
5. inspect selected lines
6. type replace string
7. alt-e to replace all within the selection
You may still want it to work with stream selection as well, in which case
an RFE or PMR would be needed if this worked before (although I went back
several versions and did not see it working).
Thanks,
____________________________________________________________________________
Maha Masri Project Manager
Rational Developer for i - Rational Developer for AIX and Linux - Rational
Developer for Power
From: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 09/08/2015 11:02 AM
Subject: Re: [WDSCI-L] The problem with Finding what is selected
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Yes, I know about search history, and it is the main reason I haven't said
anything. It is the "Restrict search to selection" piece that is the main
problem.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote: -----
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: 09/08/2015 10:57AM
Subject: Re: [WDSCI-L] The problem with Finding what is selected
Mark
In this context, have you tried arrow-up or arrow-down in the search
field? It keeps a history of things you've already searched for, maybe
that'd be useful.
Vern
On 9/8/2015 9:32 AM, Mark Murphy/STAR BASE Consulting Inc. wrote:
Several months ago there was an uproar concerning RDi's behavior when
ctrl-f was pressed. The problem was that folks wanted the selected text to
be inserted as the search term. So now the selected text is used as the
search term when ctrl-f is pressed. Unfortunately, we now have two less
than optimal consequences of this. First, if a large block is selected, the
ctrl-f search term is large, and I have to replace it with what I really
want to search for. Not always a big deal, but if I want to search for
something within a selected block of text "Restrict search to selection",
the thing I want to search for is never the selection, but some smaller
portion of the selection. I can still work around that though. The second
issue is a bigger deal. If I want to do a search and replace within a
selection, and I want to see the lines my search term will select, I have
to:
1. select a block of source
2. do ctrl-f
3. clear the search term as it contains the selected block
4. type the real search term (this can be combined with #3)
5. alt-a to filter on my search terms.
6. Inspect selected lines to ensure there is no unexpected changes that
will occur with my replace
If everything is OK, I have to do steps 1-4 again as alt-a has cleared my
selection, and ctrl-f will loose my last search term because I am searching
within a selection.
Then I can type my replace string, and select "Replace all".
This all used to be much simpler.
1. select a block of source
2. do ctrl-f (make sure "Restrict search to selection is selected")
3. Type search term
4. alt-a
5. inspect selected lines
6. type replace string
7. alt-e to replace all within the selection
I don't remember having to reselect after alt-a, and I certainly did not
have to retype my search terms (I would not appreciate this much at all if
I was using regular expressions).
I am not advocating removing the behavior where the current selection is
used as the search term except when "Restrict search to selection" is
active, and possibly when the selection is too large, maybe more than a
single line. I also would prefer that alt-a did not clear the initial
selection when "Restrict search to selection" is active. May need to save
that initial selection in the background in some way, but having to
backtrack through my use case and force retyping search terms negates any
search term validation I do using alt-a.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
