Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On 02/09/2012 02:34 PM, Russell D Mileham wrote:
I am building a Base form where I would like to group several controls and enable/disable them 
based on the actions of the user. When I group the controls, the Enabled property can be set in the 
Properties: Multiselection dialog through the GUI, but I can't seem to figure out how to access the 
group properties in a macro. I have tried accessing a Model of the Group using 
getByName(GroupName), followed by accessing the view using getControl(Model). However, it appears 
that what I get is a Model and View of the first control element contained in the group. Can 
someone point me in the right direction?

Thanks,
Can you post a copy of the form and code on Nabble or somewhere else so others can look at. Just send a message with the appropriate links. There are couple on the list who are very good a macros.

Email attachments are stripped from the list if you send directly to the list

--
Jay Lozier
jslozier@gmail.com


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.