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
_______________________________________________
LibreOffice mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice

Reply via email to