https://bz.apache.org/ooo/show_bug.cgi?id=91768
--- Comment #12 from Chuck Spalding <[email protected]> --- (In reply to Peter from comment #10) > To store Window Application Data within the Document, does only make sense > if the documents definition does define the information how to handle the > Information in a standardized way. I agree with that general statement. I am not familiar with the details of the OpenDocument standard. However, I invite you to look at this webpage: https://wiki.oasis-open.org/office/Spreadsheet_View_Data . I don't know its "official" significance, but it appears to me to be under the umbrella of the standards organization. Fundamentally, I don't understand why OpenOffice *does* use some Window Application Data that is stored within the document (e.g., author; document properties [set in File > Properties...]; styles; spreadsheet selected cell, grid on/off, row/column headers on/off, zoom; ...), but does *not* use other data that is in the document (i.e., window position and size). (As an aside, it seems odd that spreadsheet grid on/off [and other things] is set in the *application* properties [i.e., on a Mac in OpenOffice > Preferences...], but is applied on a per-document basis. [Don't get me wrong--I agree with that attribute being applied on a per-document basis.]) > We have to think how to deal with optional information. ... >From the site referenced above, and from my observance of *current* file contents, I don't think it would be "optional information". > ... I guess you do not want to store it every time you change the Windows > setting. So there is a menu popping up. Which is annoying for users who do > not care. I don't understand why the user would be involved at all. I expect the application to save the window state as it exists when the window is closed, since that's how the user has configured the window. (That's how other applications behave.) > ... This issue has a vote of 2, which is not high rated. so a lot of people > can be assumed will not want this feature. I don't know the significance of votes in this Bugzilla system, but it was me who gave the 2 votes, thinking that it might help raise the priority of the issue. Regarding how many people will want this feature, look at the multiple related bug reports--that is, the same issue reported in various ways. > Therefor we have to answer the question: How do we set the windows size > within a document or configuration? The answer seems clear to me: Use the existing attributes. > Or is it okay for the community of AOO if the Document size changes at > every save command? The document size would not change if the user hadn't changed the window. Currently, the size of (closed) document A is changed (the next time it's opened) if document B has been saved in the meantime. How can *that* be considered okay? > Also depending on the solution, we need mockups, icon or other GUI features > that get build in. I still don't understand why you think this would be something that the user would explicitly configure. I don't see any need for a change to the GUI. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue.
