Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | stylist and navigator window states not restored | ||||||
---|---|---|---|---|---|---|---|
Product: | General | Reporter: | avagula | ||||
Component: | ui | Assignee: | andreas.schluens | ||||
Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P1 (highest) | CC: | andre.schnabel, andreas.schluens, bluedwarf, chne, issues, josef.latt, lars_o_hansen, pavel, stx123, www.openoffice.org | ||||
Version: | OOo 2.0.1 | Keywords: | oooqa, regression | ||||
Target Milestone: | OOo 2.0.1 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
avagula
2005-12-01 21:26:56 UTC
cannot reproduce in OOo 2.0.1 RC2: Navigator and Stylist get restored if opened in a previous session. closing Does not work in m143. You have properly closed session? (including quickstarters etc. And have you deleted user settings before switching to new milestone? Ok, sorry, I didn't close Quickstarter (but anyway: who does?) confirmed on Windows XP Pro SP2 with OOo 2.0.1 RC2 lars: you cannot prevent quickstarter from closing, when you shut down computer ;) btw, all opsystems have not quickstarter, or they are not working as expected with 2.0 (depending its own issues). I would like to restore style filter setting too (Automatic, Hierarchcal, All Styles, etc.). In latest build (m144) it always fallback to "Automatic", even if OOo wasn't closed. Just open/close Stylist. I received a report from curvirgo which says the same thing. I could reproduce this problem on Linux with m141 but I couldn't with 2.0. Then I find that i51628 may affect this issue. Not sure, however I hope my advice helps. Added as and cn: I tested some cases with m141 and found that m_nRefCount_* has never been decreased to 0 and the destructer of m_pDataContainer_* have never been called for some reason. So OOo cannot write out Views.xcu, which saves the states of any windows of OOo. There's almost no doubt that the change of fwk21 cause this problem. Please have a look. -> as, cn Curvirgo's report in Japanese help me pursue this issue. Thanks. worked in 2.0.0 -> regression *** Issue 59189 has been marked as a duplicate of this issue. *** Created attachment 32296 [details]
the patch for this issue, which is not complete
I attached a patch for i58758. However, it is not complete to solve this issue. The visibility state is now stored and read correctly but the position and size state is not. We have to continue to investigate this problem. OOo 2.0.1RC4 on W2K has obvously read my configuration data on update from 2.0.0 and by now I have the Stylist and Navigator window "always on and docked" @Andre: Can we raise priority for this? I see it as "basic functionality" AS->bluedwarf : The problem occures since issue #56589# (cws[perform06]) was fixed. And sorry . .. but your patch isnt the right one. It would turn back the changes made for #56589#. The right fixe would be: call "flush()" inside every SetXXX() call. see checked in version on cws[fwk29]. . . The target milestone for this bug seems to be a joke. You should consider to delay the realease of OOo 2.01 to solve this bug. This (the realease) concerns also Issue 59188. IMO this is a basic functionality. If this is really fixed, it should be integrated in OOo 2.01. I agree with jolatt. As volkerme reported, this bug may inconvenience those who are using 2.0. The problem, the position and size states are not kept correctly, was specific to IceWM window manager which I mainly use. I confirmed the fix of fwk29 works correctly on Knoppix 4.0 (KDE) with my own build. You can download my build from ftp://ooopackages.good-day.net/pub/OpenOffice.org/Linux/OOo680_m141_i58758_test.tar.gz curvirgo also confirmed the fix of fwk29 with Gnome 2.10 and on Windows XP with his own build. md: This will be addressed in 2.0.1 *** Issue 59353 has been marked as a duplicate of this issue. *** *** Issue 59188 has been marked as a duplicate of this issue. *** *** Issue 59188 has been marked as a duplicate of this issue. *** verified in 2.0.1RC5 german ->closing |