Hi Jonathan, > Now that the form controls are largely there, what's required to > implement GroupName support for the Basic dialog controls?
Oh, didn't know this is on the plan, too ... As far as I know, grouping there is controlled implicitly by a) the tab index property and b) by the type of the controls. That is, the controls (control models, more precise) are sorted by tab index, and in this sequence, certain control types (such as the first of a sequence of radio buttons) defines the start of a group. The implementation for this is in toolkit/source/controls/unocontroldialogmodel.cxx, method implUpdateGroupStructure. (Hmm. Looking into this method ... it looks as if I wrote this code ... though I really can't remember :-\ ) As a rough plan, you would need to - introduce a new property GroupName / BASEPROPERTY_GROUPNAME in the toolkit module. For the details, just refer to the existing properties, all this is pretty straight forward - add this property to the UnoControlRadioButtonModel - remove the GroupName property from the form's radio button implementation. That is because form control( model)s inherit the properties from the toolkit control( model)s, unless explicitly masked out. - change the implUpdateGroupStructure method to respect the new property - change the persistence code for UNO dialogs to load/save the new property. Now that code really is beyond my competence, it's in xmlscript, AFAIK. - re-add the DIALOG_VISIBLE flag to extensions/source/propctrlr/formmetadata.cxx's GroupName entry Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
