Re: Questions about CL parser.

Hey Kelly,

1) This is working as designed. When prompting, the preferences for CL
formatting are respected.  If you have formatting off, then you would see
the behaviour you describe.  I can see how that may not be desirable, I
would expect the command to be placed starting in the same column that it
was previously, so I've added your feedback to our requirements list.

2)   This is also working as designed.  The default tab key behaviour
(insertToTab) was overridden by the iSeries parsers in order to behave the
same way as CODE.  Unfortunately the way this was done makes it very
difficult to reverse the behaviour (you would have to subclass the iSeries
parsers).  I will also add this to our list.


thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/22/2005 09:52:48 AM:

> There's two behaviors of the CL parser I'd really like to change if
possible.
>
> (1) When I prompt a command, the parser moves the code to the far
> left starting position of the line on returning from the prompt.
>
> (2) When I place the cursor within a line and press the Tab key, the
> cursor tabs without moving the text. For example, if my code looks like
this:
>    ADDLIBLE LIB(MYLIB)
> and I want it to look like this:
>    ADDLIBLE   LIB(MYLIB)
> I can't place my cursor at the end of ADDLIBLE and press the Tab
> key. I have to use the spacebar and add individual spaces.
>
> Is there any way to change the behavior of the parser so it doesn't
> shift the code to the beginning of a line and so it does move the
> text when the Tab key is pressed?
>
> I'm running WDSCi 5.1.2 with the CL automatic formatting and
> automatic indenting turned off.
>
> Thanks,
> Kelly