I read Eric's stack about how to use tables, which was very helpful.
His suggested approach for making a table not scroll (i.e., act as if it were a fixed group of fields on the screen) shows just how awkward the table facility is. Imagine having five tables on a stack and trying to implement the RawKeyDown handler: you would have to clone the code repeatedly for every table on the stack, or loop over all fields looking for tables.
I'm afraid I can't understand why this obviously helpful feature was not built into tables from the start
Grump Jon _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
