Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | cannot save or open a network path with spaces | ||
---|---|---|---|
Product: | General | Reporter: | Unknown <non-migrated> |
Component: | code | Assignee: | thorsten.martens |
Status: | CLOSED FIXED | QA Contact: | issues@framework <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | 638 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows ME | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2001-10-17 09:41:23 UTC
I will take care of this one ! In an actual internal version (641xx), which will be the base for the next upcoming OO, saving and loading in network-folders with a space in their name, works fine when using the file-open / save-as dialog. When trying to open such a file via doubleclick in Windows-ME-Explorer an errormessage occurs. This bug has been reported to the development section to be fixed. For further investigation it would be helpfull to know a little bit more about how this bug has occured. A step by step walkthrough and mentioning which filetypes and dialogues (own or system) were used, could help ! To replicate the defect, you can do the following: 1. Start a new Text Document, type something and then choose File- >Save. 2. On the Save As dialog box, choose any path in Network Neighborhood, e.g. "Wand Computer" -> "c" -> "My Documents" - > "Untitled1.sxw". 3. OOo would pop up this message (with a OK button): Error saving the document Untitled1: Wrong parameter. The operation was started under an invalid parameter. OR you can do the following: 1. On the menu bar, choose File->Open. 2. On the Open dialog box, choose any path in Network Neighborhood, e.g. "Wand Computer" -> "c" -> "My Documents" -> "Untitled1.sxw". 3. OOo would pop up this message (with a OK button): Error loading document file://Wand%20Computer/C/My%20Documents/Untitled1.sxw Nonexistent object. Nonexistent file. OK, problem is now completely fixed and doesn`t occur in an internal 641f1 anymore. Due to the fact that upcoming OO versions will be based on a 641, this problem won`t occur any longer. Fixed, verified and closed ! |