Tab v. CR in a Table

[Kevin_work]

I have a table that I am using to get user input.
The table has a certain maximum size that is displayed to the user.
(Ie 3 rows by 10 columns + row column headers).
I turned off all scroll bars since more than 30 entries is not allowed.

The problem is this :
If the user enters text and then presses the CR, the focus goes to the
cell below the current cell. This is fine unless the current cell is in
the bottom row. In this case the whole row moves up exposing a row
that I do not wish to be seen / modified. And no way to get back
since there are no scroll bars.

Conversely, if the TAB is used it will go through all the visible cells
and then return to the top left cell.

Any ideas ? BTW, I am using Solaris so the solution must be
G or
CIN.

Thanks, Kevin Kent
____________________________
My job is so secret, *I* don't even know what I am doing.


[See first answer for additional information]

[Kevin_work]

[Attachment(s) for question]

[lupo]

Kevin B. Kent schrieb in im Newsbeitrag:
388F85AE.88BC8A43@usa.alcatel.com...
> I have a table that I am using to get user input.
> The table has a certain maximum size that is displayed to the user.
> (Ie 3 rows by 10 columns + row column headers).
> I turned off all scroll bars since more than 30 entries is not allowed.
>
> The problem is this :
> If the user enters text and then presses the CR, the focus goes to the
> cell below the current cell. This is fine unless the current cell is in
> the bottom row. In this case the whole row moves up exposing a row
> that I do not wish to be seen / modified. And no way to get back
> since there are no scroll bars.
>
> Conversely, if the TAB is used it will go through all the visible ce
lls
> and then return to the top left cell.
>
> Any ideas ? BTW, I am using Solaris so the solution must be
> G or CIN.
>
> Thanks, Kevin Kent
> ____________________________
> My job is so secret, *I* don't even know what I am doing.
>

Hi Kevin

complicated - but it works:
Check out the 'Edit Position' of the Table (Attribute Node).
If the 'Edit Position' is out of defined range (i.e. 0..2/0..9)
set 'Edit Position' to 0/0 and
then to to the index of the last allowed row or column (i.e. 2/9).

Robert

[Kevin_work]

Robert Luftensteiner wrote:

>
> > The problem is this :
> > If the user enters text and then presses the CR, the focus goes to the
> > cell below the current cell. This is fine unless the current cell is in
> > the bottom row. In this case the whole row moves up exposing a row
> > that I do not wish to be seen / modified. And no way to get back
> > since there are no scroll bars.
> Hi Kevin
>
> complicated - but it works:
> Check out the 'Edit Position' of the Table (Attribute Node).
> If the 'Edit Position' is out of defined range (i.e. 0..2/0..9)
> set 'Edit Position' to 0/0 and
> then to to the index of the last allowed row or column (i.e. 2/9).
>
> Robert

Thanks Robert.
This is exaclty what I wanted. It jumps a bit when it goes
down a row and back up bu
t I can live with that.

Kevin Kent