Hi Carsten,
After some investigation for the unimplemented UNO interfaces in our XCU
based accelerator configuraiton, I get some ideas as following:
1)For com.sun.star.ui.XUIConfigurationStorage,
we have to connect a storage when reloading/storing ui configuration, so
setStorage(...)/hasStorage of XUIConfigurationStorage are used on this
purpose. Right?
According to this, we have to specify the storage, where the
accelerators are loaded/stored from/to, for the document accelerator
configuration. The setStorage(...)/hasStorage have also been implemented
for this situation.
But for global or module depending accelerator configuration, where the
accelerators are now loaded/stored from/to XCU, it seems that it isn't
necessary to set the storage for global/module accelerator
configuration. If we want to store their accelerators to a storage, we
can use the XUIConfigurationPersistence.storeToStorage().
Similarly, the ImageManager and UIConfigurationManager have implemented
the interface XUIConfigurationStorage, while ModuleImageManager and
ModuleUIConfigurationManager doesn't inherit it.
2)For com.sun.star.ui.XUIConfigurationPersistence,
All the 3 types of Global/module/document accelerator configuration have
to implement the XUIConfigurationPersistence. We can use the original
AcceleratorCache and AcceleratorXMLWriter to store the accelerators to a
specified storage, and I have done it in my local code.
And what's your opinions?
Regards,
Yan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@framework.openoffice.org
For additional commands, e-mail: dev-h...@framework.openoffice.org
