> > Me: "[I'd also like to see] Columns, or at least synchronized scrolling >> between two or more distinct fields." >> Raney: "Combining the grid lines properties with tabstops pretty much >> handles >> [columns]." >> Are you *sure* about that? Let's say you're using gridlines and tabstops, >> and you've got a field that *looks* like it's got 2 columns in it. What >> happens if you insert a paragraph into column 1? > >That's one of the issues: all the cells have to be the same size, and >there is no support for wrapping the text in one cell. Jacque (of >HC-list fame) worked up an example that supports these things using >multiple fields in a scrolling group. It works pretty well, even >without any special optimizations in MetaCard. Hopefully a public >example of this will be made available at some point. Nevertheless, a >property that controls "cell" formatting would be useful to have. It >could either be "none" (the current behavior), "clip", or >"expandToFit". I would assume that the "expandToFit" option would >also automatically wrap the text as needed. We have more than those requirements: 1. Selections must be constrained to one cell 2. Leaving one cell must send some message (closeCell), so you can check for correct entries (some cells can only contain numbers for example) 3. Some rows, collumns, or even single cells can be locked (lockText) We are doing a lot of magic with MetaCard to simulate this and would be glad to reduce the complexity of our product. But without these three, we can not. -------------------------------------------------------------------- | Ruediger zu Dohna GINIT GmbH 0721-96681-63 [EMAIL PROTECTED] | | PGP-Fingerprint: F1 BF 9D 95 57 26 48 42 FE F8 E8 02 41 1A EE 3E | --------------------------------------------------------------------
