|
Home > Archive > WebSphere HATS > November 2005 > AutoTAB on Input
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Mitch Davidson 2005-06-05, 5:45 pm |
| New to HATS, just got going and are at V5.0.4 and have noted that for a data entry screen, when a field gets filled, the user must TAB to get to the next input field.
Is there a way to make that happen automatically?
| |
| Juanma Martinez 2005-06-05, 5:45 pm |
| In article <d0afqi$4682$1@news.boulder.ibm.com>, DavidsMi@collier.k12.fl.us says...
> Is there a way to make that happen automatically?
>
Auto Advance
The ability to have the cursor advance automatically to the next input field on the Web page
once the current input field has been filled) has been added to HATS V4.0.4. With this feature
enabled, cursor movement will behave more similarly to how it behaves in a typical terminal
emulator - once a user has completely filled in a field, the cursor will automatically move to
the beginning of the next field.
To enable this feature, edit the file webApplication\common\lxgwfunctions.js (located in your
HATS Project) and change the line:
var autoAdvance = false;
to
var autoAdvance = true;
This will enable auto advance on every page of your HATS application. You can selectively turn
this feature on or off per transformation by adding the following lines just before the
<HATS:Form /> tag in your transformation:
<script>
autoAdvance = false;
</script>
--
Juanma Martínez
| |
| Mitch Davidson 2005-06-05, 5:45 pm |
| Most excellent!!! Once I found the right spot (newbie, had to learn to go to the Navigator perspective!) making the change was a snap. I'd almost vote for this to be default as true instead of false, but it surely is a good motivator to make the change and demonstrates the relative ease of doing so.
Thank you very much!
| |
| COPS Project Team 2005-11-03, 8:45 pm |
| "Juanma Martinez" <juanma_martinez@es.ibm.com> wrote in message
news:MPG.1c93ae592dc5ce86989712@news.software.ibm.com...
> In article <d0afqi$4682$1@news.boulder.ibm.com>,
> DavidsMi@collier.k12.fl.us says...
> Auto Advance
>
> The ability to have the cursor advance automatically to the next input
> field on the Web page
> once the current input field has been filled) has been added to HATS
> V4.0.4. With this feature
> ... [and so on, copied form the doco]
> Juanma Martínez
Hi.
Has anyone heard of problems with the auto-advance functionality? I find
that while it is very useful, the way in which it works is subtly wrong. The
cursor should automatically advance to the next field only when you actually
type the last character into the field. But in fact, once a field is
completely filled, the end of it becomes "greased" so that the cursor "slips
off" whenever it touches it. This is can be worked around, of course, but is
quite a nuisance if trying to edit the value in a field.
Imagine you want to edit a long text field - say, 60 characters - which is
fully populated. Perhaps you want to remove the last character. So, you tab
to the field, hit [End] to jump to the end, and the cursor immediately jumps
to the start of the following field. Argh!
Ok, no problem, you can deal with this. You grab your mouse and click at the
end of the field. The cursor immediately jumps to the start of the following
field. What the BLEEP is going on here...
Anyway, I think you get my point by now. How can one modify the behaviour so
that auto-advance only affects what it should, and not the arrow keys, [End]
key, mouse and whatever? Or to state the question in another way, how can I
cause auto-advance to trigger only when the field value is modified?
Lewis Pritchard
------------------
| |
| George Baker 2005-11-06, 8:45 pm |
| In article <dkehfs$898u$2@news.boulder.ibm.com>, cops@police.nsw.gov.au=20
says...
> "Juanma Martinez" <juanma_martinez@es.ibm.com> wrote in message=20
> news:MPG.1c93ae592dc5ce86989712@news.software.ibm.com...
>=20
> Hi.
>=20
> Has anyone heard of problems with the auto-advance functionality? I find
> that while it is very useful, the way in which it works is subtly wrong. =
The
> cursor should automatically advance to the next field only when you actua=
lly
> type the last character into the field. But in fact, once a field is
> completely filled, the end of it becomes "greased" so that the cursor "sl=
ips
> off" whenever it touches it. This is can be worked around, of course, but=
is
> quite a nuisance if trying to edit the value in a field.
>=20
> Imagine you want to edit a long text field - say, 60 characters - which i=
s
> fully populated. Perhaps you want to remove the last character. So, you t=
ab
> to the field, hit [End] to jump to the end, and the cursor immediately ju=
mps
> to the start of the following field. Argh!
>=20
> Ok, no problem, you can deal with this. You grab your mouse and click at =
the
> end of the field. The cursor immediately jumps to the start of the follow=
ing
> field. What the BLEEP is going on here...
>=20
> Anyway, I think you get my point by now. How can one modify the behaviour=
so
> that auto-advance only affects what it should, and not the arrow keys, [E=
nd]
> key, mouse and whatever? Or to state the question in another way, how can=
I
> cause auto-advance to trigger only when the field value is modified?
>=20
> Lewis Pritchard
> ------------------
>=20
I believe you may have a point. I took an emulator and typed data into=20
all positions of an input field and watched the cursor jump to the next=20
input field. I then repositioned my cursor in the completely full field=20
and pressed the End key and the cursor moved to the protected position=20
immediately after the last character in the field. =20
Therefore, I recommend you call the IBM support center and open a=20
product defect (PMR) stating that the implement ion did not match the=20
operation of a real 3270 emulator. I cannot guarantee that it will be=20
fixed, but this is the procedure for getting such issues resolved.
|
|
|
|
|