Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Inconsistent labeling of unsaved documents | ||
---|---|---|---|
Product: | General | Reporter: | Stefan Weigel <weigel> |
Component: | ui | Assignee: | AOO issues mailing list <issues> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | czeslaw.wolanski, digro, issues, mseidel, rainerbielefeld_ooo_qa |
Version: | OOo 3.0 | Keywords: | needmoreinfo, oooqa |
Target Milestone: | 4.1.13 | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bz.apache.org/ooo/show_bug.cgi?id=128400 | ||
Issue Type: | DEFECT | Latest Confirmation in: | 4.1.12 |
Developer Difficulty: | --- | ||
Attachments: |
Description
Stefan Weigel
2008-10-22 15:57:57 UTC
Created attachment 57388 [details]
screenshot showing inconsistency between labelling of unsaved documents
@AS, please have a look. It's not only the old label type, it's just another name! Properties of (German) new document "Unbenannt 3" will show "Unbenannt1" as file name. Pls. see additional screenshots. @sweigel: Pls. specify your OS and Platform, this bug might be OS-specific. Forgot to mention: I checked with "Ooo 3.0.0 RC3 Multilingual version German UI WIN XP: [OOO300m8 (Build9357)]" and can confirm the reported effect. Created attachment 57390 [details]
one other effect shown in screenshot
Resetting OS from "Winsows XP" to "All". Found this Bug with OO0 3.0 stable (OOO300m9) on - Windows 2000 SP4 - Windows XP SP2 - Ubuntu Linux 7.10 @rainerbielefeld: I cannot reproduce "Unbennant 3" --> "Unbenannt1". How did you do that? Indeed, currently I can only reproduce the bug from your report. I will do several further tests and try to find out how the "Unbenannt 3" --> "Unbenannt1" problem can be reproduced. Title shown inside title bar was never real thought to be used for printing ... anyway ... somewhere reused it this way and now it's broken because framework uses a complete new title bar (!) implementation. It seems that the insonsistency is caused by still using the old sfx based methods. We must find the code using them and rework it to use the framework based implementation (API at the model). Please try this: (1) Open a new document (text or spreadsheet) (2) In the toolbar click "Page Preview" several times and watch the title of the window. You will see the the title of the window go like this: Untitled 1 Untitled 1 : 2 Untitled 1 Untitled 1 : 3 Untitled 1 : 3 Untitled 1 : 4 Untitled 1 : 4 Untitled 1 : 5 and so on. Note: There is only one window for this document any time. But the caption displays as if there were multiple windows of the same document. Pleas also have a look at the following screenshot. Created attachment 66271 [details]
Screenshot mentioned above
I don't think that this issue deserves the keyword "regression". The naming of unsaved documents always was broken to some degree. So it now just is buggy in a different way. :-) Reset assigne to the default "issues@openoffice.apache.org". The current state of affairs (August 2020): issue still present. The attached image file provides few examples (Win 7, 64-bit, Home Premium; AOO 4.1.7 and AOO 4.2.0-dev). Another instance (Navigator in Writer and Calc) is described in Issue 128400. Created attachment 86973 [details]
Examples of inconsistent labelling
String seems to be originating from the variable STR_NONAME Source in KID_localize.sdf: sfx2 source\appl\app.src 0 string STR_NONAME 0 kid plblxp‖Untitled Found references to SetTitle and GetTitle in file: /trunk/main/sfx2/source/doc/objmisc.cxx Line 809 : void SfxObjectShell::SetTitle Line 879 : String SfxObjectShell::GetTitle Seems to originate from these lines: 833 // wird 'unbenannt#' als Titel gesetzt 834 String aNoName(SfxResId(STR_NONAME)); 835 if ( rTitle.Match(aNoName) <= aNoName.Len() ) _______________ Since I'm not at all a developer and don't know anything about C++ I will not touch the code, but if someone is interested: this is possibly where you might want to start looking This should be fixed now in trunk (#75e50e85) and AOO42X (#4453b43) Can someone confirm, please? BTW: Comment 11 and 12 show a different bug. Feel free to open another ticket for it. I have tested now with the latest builds on all branches and did not find any occurrence anymore. |