Noel Power wrote:
On Tue, 2009-10-13 at 10:11 +0100, Noel Power wrote:
Is there any plans to change that? I mean I can understand this
rationale for global/user settings for toolbars that are document
specific ( e.g. stored in the document ) But... having the visibility
state of document specific toolbars stored locally on the file system
( to my mind ) makes no sense
rewording...
Are there any plans to change that? I mean I can understand the
rationale for global/user settings for toolbars for application
settings. But for toolbars that are document specific ( e.g. stored in
the document ) having the visibility state of document specific
toolbars stored locally on the file system ( to my mind ) makes no
sense.
Hi Noel,
According to my knowledge there are no such plans. I can understand your
arguments but the user experience team decided that the state of EVERY
toolbar should be user specific. You could store the visibility of every
toolbar in a document and hide/show it although the user decided
otherwise. That's the reason why user experience decided against this
solution.
The current design uses the configuration to store the position,
visibility and other attributes. A natural enhancement would use a
configuration provider which can read/write configuration files from a
document. There is no such configuration provider and writing one is not
an easy task. Therefore, from my point of view, changing this behavior
in a good way needs some work to do. Currently I see no chance to
implement it in the near future.
Regards,
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
