× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I'm with Dave - this function acts differently between CODE and WDSc, and I
would like to have the original CODE functionality. It just makes more
sense to leave the cursor on the original line.

Jim

On Thu, Feb 21, 2008 at 9:37 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

Dave Shaw wrote:
In CODE, when filtering the current selection, the cursor stays on the
line where you made the selection. If you don't move it, you can expand and
be right back where you were. In LPEX, the cursor goes to the first line
selected by the filter. When there are a lot of similar lines, I find this
annoying, since I usually forget to set a quick mark first and have to take
time to go back, since (for example) it isn't easy to tell one 'when
selected_field = x' from another. Is there any simple way (other than
hitting myself over the head every time I forget to set a quick mark until I
start doing it right) to make LPEX emulate CODE on this or work around it
somehow?



It took me a while to figure out what you were saying. What you're
saying is that if you have, say, 10 WHEN statement in your program and
you select the fourth one, this of course positions the cursor to that
line. When you then right-click and choose Selected / Filter on
Selection, it shows you all ten lines, but positions the cursor on the
first one, and you don't know which one you were originally one. And
thus, if you hit Ctrl-W to remove the filtering, your source member is
now positioned to the first one, not the fourth.

Nope, I can't see a good way around it. You can, of course, take a
quick glance and remember which line number you were on before you do
the filter. Or, as you suggest, you can set a quick mark. But my guess
is that it's pretty hardcoded into the filter-by logic to position the
cursor on the first one (since it's quite possible to filter out the
line cursor is currently on).

This looks like an opportunity to write your own command! I'm not sure
of all the ins and outs, but you'd want to write a little command that
first executes a quick-mark, and then a filter on selection. You'd mark
the text, and then run that command (probably by tying it to a shortcut
key). This would be a cool project, actually. Wanna work on it?

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.