Re: filterSelection cursor positioning

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