Hi Ariel, > In the following I report some tests.
finally found some time to come back to this ... Okay, as I see it, there's a number of root causes for all your observations: 1. When you select a category where no items are currently selected, then listeners are properly called, but subsequent getSelection calls return an empty DatabaseObject sequence. 2. When you select more than one item (in any category), then only the selection of the first is reported to the listeners, all subsequent selections are not reported. 3. an action which changes the selection state of multiple items triggers multiple notifications (instead of only one), one for each "intermediate selection state" in the transition from the old to the new selection. All of those 3 appear once or more in the scenarios you describe (and, in their entity, are now known as issue 93424). The good news: I fixed all of those (where especially the third fix comes at the cost of making the notification asynchronously). The bad news: It's in CWS dba31c, which means it is for 3.1 only :-\ In case you want to try out the changes: I attached the patch to the issue (it requires the previous patch, which is attached to some of my other mails here in this thread). > I'm not sure about the NamedDatabaseObject[0].Name, but reading the > specification, will it be the name of the "data source"? I updated the documentation to refer to DataSource.Name here, where it's described as either being the registration name (in case of a registered DB doc) or the file URL of the document. Again, thanks for the detailed feedback, and apologies for taking so long to answer it. 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]
