I see the problem myself, and I also haven't reported it mainly because it is quicker to work around the problem than to create an RFE. If you raise an RFE then I will vote.
On the other hand, it might warrant a PMR as functionality is missing that should be there.
-Paul.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: 08 September 2015 16:01
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] The problem with Finding what is selected
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.
---------------------------------------------------------------------------------------
Important This email transmission and any files with it are strictly confidential to the intended recipient and may be legally privileged. Any views or opinions presented are solely those of the author and do not necessarily represent those of BHSF. If you are not the intended recipient, you must not copy, disclose or distribute its contents in any way.
If you have received this email in error, please notify the sender and delete the email from your system. We have taken steps to ensure this email and attachments are free from any virus but do not accept any responsibility once this e-mail has been transmitted. You should scan any attachments for viruses. No contract may be concluded on behalf of BHSF Group Limited or its subsidiary companies by email.
Registered Office: BHSF Group Limited, Gamgee House, 2 Darnley Road, Birmingham B16 8TE. Registered in England number 04767689. BHSF is authorised and regulated by the Financial Conduct Authority and Prudential Regulation Authority.
This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit
https://www.mimecast.com
---------------------------------------------------------------------------------------
midrange.com
