On 02/28/2012 02:36 PM, Caolán McNamara wrote:
There's something odd here, RestoreConfigDefaults_Impl is supposed to
basically do the right thing, reset the values to their defaults, but
the cast of m_xConfigurationUpdateAccess to an XPropertyState throws in
SvxProxyTabPage::ReadConfigDefaults_Impl and
SvxProxyTabPage::RestoreConfigDefaults_Impl so all of that reset is
skipped/non-functional.
Looking into configmgr I don't see any mention of XPropertyState in the
list of things an Access supports. Though I do see a mention in (the
unbuilt) configmgr/qa/unit/test.cxx of
//TODO: support setPropertyToDefault
caolanm->sb: What's the story with XPropertyState and
configmgr::Access ? Should Access support XPropertyState so the
XPropertyState stuff in optinet2.cxx works ?, or is it not supposed to
support XPropertyState and the stuff in optinet2.cxx should be changed ?
Sorry for the long delay. I marked the initial mail for later
consumption but then lost sight of it. Looking into this now, it
appears that was a deliberate act of my subconscious...
See <https://bugs.freedesktop.org/show_bug.cgi?id=33697#c7>.
Stephan
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.