Hi Carsten On Mon, 2009-10-12 at 14:56 +0200, Carsten Driesner wrote: > The visibility state cannot be stored in the document. This was a > design > decision by the UX team several years ago. > The visibility state should > always follow the user settings. That means if the user sets a > toolbar > to invisible it's a violation of user experience to make it visible > again. 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. Bear in mind it's not just the visibility state that is stored but also the positioning, so, with the current system if you have a document that you want to store some custom functionality exposed via a toolbar ( you cannot specify the desired position or initial visibility state of that toolbar ) Furthermore if someone opens that document they could hide the toolbar ( or move it into a position where not all toolbar items are easily visible etc. ) The next time that user opens the document those ( in this case erroneous ) changes would be applied, surely those changes should/could be stored with the document? at least then if the document was not modified the positional and visibility attributes would be in a consistent state?
Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
