Re: Outline view to source always one row too high (bug?)

Gregg,
I was wrong about positioning the cursor and you don't have to
double-click, just click the field in the outline view as you mentioned.
You are correct that the cursor does not position to the text.  The cursor
remains in the outline view.  I think this is to allow you to use the arrow
keys to flip through the outline view until you click in the source area.
If you have highlighting turned on, you will see the line containing your
selection.  I was thinking that the highlighted line always follows the
cursor but not in this case.  By default, highlighting is off.  I don't see
any reason why highlighting shouldn't be on all the time.  Turn on
highlighting with Windows > Preferences > Remote Systems > iSeries > LPEX
Editor Parsers.  Click "Highlight current line".  Can anyone at IBM think
of a reason why "Highlight current line" shouldn't be the default?

Thanks,
Craig Strong

<snip from Craig>
I have noticed that whenever I double-click a field, subroutines, or
other element in the outline view, it positions me to the file, field, or
subroutine in the RPGLE source but the cursor is always one row too high.
With highlighting on, actually highlights the row above the field, file, or
subroutine found.
<end-snip>

** Gregg wrote:
Craig,

When I click on a field in the outline it is positioned in the middle of
the
line editor. However, my source does not contain any lines of /TITLE or
/EJECT. My cursor also does not position to the text either. That is why I
was wondering if it is a value that needs to be set to allow positioning.

Gregg Willow

----- Original Message -----
From: <craigs@xxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, September 22, 2003 2:17 PM
Subject: [WDSCI-L] Re: Outline view to source always one row too high
(bug?)


>
>
>
>
> Ahh yes!  There is a /TITLE.  No /EJECT's though so that probably
explains
> being one off.  I tried doing the refresh on the source again making sure
> there weren't changes made to the source and it was still one off.  So, I
> am almost sure that is what it is.  Thanks for looking at it!  Someone
else
> mentioned theirs positioning in the center of the source.  I suspect if
you
> count the /TITLE and /EJECT's, this is how many rows off you would be.
> Mark, the Ctrl+Space worked for auto-complete after refreshing the
Outline
> view.  I just kept searching the archives and found the Ctrl+Space in a
> post a little later aftrer I posted that one.  Thanks again for your
help!
> It looks like Ctrl+Space always auto-completes on opcodes.  The Outline
> view doesn't even have to be up for auto-completing fields and files.
Just
> make sure an Outline view has been refreshed some time before.
>
> Thanks,
> Craig Strong
>
> ** Nazmin wrote:
> Craig,
>    Do you have directives like /eject, /title in your source? That would
> put your positioning up by one for each of these directives. Yes, this is
a
> bug and I am currently looking at it. If this is not what is causing the
> problem, please do send me the snippet of the source that causes the
> problem and I would be glad to look at it.
>
>
> Regards,
> Nazmin Haji
> Eclipse iSeries Tooling Development