Hi,
I'm facing a problem I don't know how to solve.
I've a complex get with several fields that may be populated directly with a code or found by activating an F.. key with a lookup in a linked table.
For each get object I may have different f.. keys with diferent functionality, i.e.
@ 2,2 get cvatcode pict "@!" (pressing F2 opens a tbrowse to lookup, pressing F4 opens a frame with the amounts divided by code)
@ 3, 2 get cUM pict "@!" (pressing F2 opens a tbrowse to lookup, but I need to disable F4 key, and, maybe, to enable another F.. key for other purpose.
...
...
READ
In addition each get has it's own message that it isn't at line 24 and centered, but it must be shown at the bottom of the window, whose dimensions and coordinates arent those of the entire screen.
In the past I had solved giving a READ after each get but it's inelegant and with very complex forms it's unmanageable.
There is another way to do it?
You can use the WHEN clause to pre-validate a get (code is executed when
the get receive the focus) and the VALID clause to post-validate a get
(code is executed when the get lost the focus).
You can use obj:varGet() to obtain the current get object, look at SRC\SYS\GETSYS.PRG.
PS: c'e' anche it.comp.lang.vo-clipper
Hi,
I'm facing a problem I don't know how to solve.
I've a complex get with several fields that may be populated directly with a code or found by activating an F.. key with a lookup in a linked table.
For each get object I may have different f.. keys with diferent functionality, i.e.
@ 2,2 get cvatcode pict "@!" (pressing F2 opens a tbrowse to lookup, pressing F4 opens a frame with the amounts divided by code)
@ 3, 2 get cUM pict "@!" (pressing F2 opens a tbrowse to lookup, but I need to disable F4 key, and, maybe, to enable another F.. key for other purpose.
...
...
READ
In addition each get has it's own message that it isn't at line 24 and centered, but it must be shown at the bottom of the window, whose dimensions and coordinates arent those of the entire screen.
In the past I had solved giving a READ after each get but it's inelegant and with very complex forms it's unmanageable.
There is another way to do it?
Regards
Marco
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 185 |
Nodes: | 16 (2 / 14) |
Uptime: | 08:50:29 |
Calls: | 3,651 |
Calls today: | 7 |
Files: | 11,145 |
Messages: | 3,445,099 |