I have occasion to create a scripted dialog containing a ListView control which, depending on runtime circumstances, will either have no column headers or will have an unknown number of columns with dynamic names. By "dynamic," I mean they will change from one dialog creation to another; they will not change while one dialog is showing.
This scenario obviously outrules xml specification of column headers. My basic question, though, is how dynamic is WE's code for positioning and sizing things, and when does it run? Specifics: If I don't say in xml that there will be column headers, then I create them at runtime, will things look out of whack on screen? Related: Would it be better to say in XML that there will be column headers, then turn them off in code when necessary? If spacing and sizing is worked out at dialog creation time, I'm wondering if I should pull the crazy stunt of writing out a dynamic xml file and then using that to open the dialog. I doubt this is necessary, but since I won't know the column count or widths in advance, who knows... And one final question, though I bet I know the answer: Text items and subitems look writeable, but I don't suppose this means I can shortcut the normal red tape of inserting rows and columns a cell at a time with Insert calls, and just fill listview.text(i,j) as a two-dimensional array to populate the control? I'll be surprised if that one works... -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
