Hi Kelvin, thanks for your fast feedback :), and lemme comment inline.
> - [Off topic] Interestingly when I download the document using Windows > XP Pro SP2 the odt file becomes a zip file. I suppose that's something with the setup of the OOo server serving the files ... > - Column heads > > It is not explicitly stated in the spec what happens when the List > Content is Table, Query, SQL, or SQL (native), what is the effect of > Column heads value. I expect if Column heads is True the field names > will appear in the heading row. Is this correct? Interesting. My fast answer, from the model I had in my head, but obviously not in the spec, would have been: The first data row is made the header. However, your idea sounds interesting, and the mere fact that MSA also uses the column names suggests that we should do this for compatibility, at least. Thanks for pointing out, I will incorporate this into the spec. > - 3.4 Notes > > From my point of view as an MS Access developer I too find the width > property one of those things that does not appear logical. If you define > columns the width you want, why then give a total width. Having said > this I have used the width property on a number of occasions. Thus it is > used. It might depend on the implementation effort here. If it's a rarely used thing which takes a lot of time to implement it, then it's not worth it. Not sure ATM (that's one reason the spec has revision 0.1 :). > - Something I can't do in MS Access that may be useful. > > The ability to wrap the contents of a column so that rows are not just a > single line height in list and combo boxes. Hmm, so basically rows would have different heights, wouldn't they? You probably do not want to wrap *across* lines, since this would mean that you could select "part three of record 4", which by chance is in line 6. Difficult, would again depend on the implementation effort vs. benefit. Nice to have, sure, but at the moment I'd say: not more than this. > - Will Basic Dialogs also have the same capability Yes, minus data bindings. As of today, Basic dialog controls and form controls share the same implementation, extended by the latter with some data-access facilities. So, the multi-column feature would most probably also be available for dialog controls, but only for explicit value lists thens. Thanks again for pointing out this missing part. Thanks & Ciao Frank -- - Frank Sch�nheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
