maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Confusing behaviour when saving to a file that matches an existing directory|
|Product:||[Maemo Official Applications] Images and Camera||Reporter:||timeless|
|Component:||Image viewer||Assignee:||unassigned <nobody>|
|Status:||RESOLVED FIXED||QA Contact:||image-viewer-bugs|
Steps: 1. open file manager 2. select the images folder 3. tap new folder 4. enter "Z.png" 5. tap ok 6. open images 7. app menu>image>save a copy... 8. enter "Z" 9. tap ok Actual Results: 8. (?) Replace existing file of same name? 9. Not Allowed Expected Results: a. don't show me a dialog that talks about a file that doesn't exist b. don't give me an error that says 'not allowed', it doesn't mean anything to a user (or a translator)
Updated status for Fremantle welcome.
WONTFIX for Diablo (not critical). Fremantle status welcome... -> moreinfo
In 1.2009.42-11 (using a Z.jpg directory due to bug 7015) Actual Results: 8. "Overwrite original file?" (say yes) 9. "Saving Image Z" 10. No error message, Z.jpg directory left intact and still empty, temporary JPEG file named .imgvwr8N4R4U left behind.
Internal moreinfo: "After creating folder name with j.peg under Images folder: 1.If trying to rename any image with "z" name it will display"Image name is already in Use" (or) 2.Trying to copy any image with "z" name to the Images folder Pop up will display with "Replace existing folder of same name?z.jpg" .If press yes ,it will remove the folder "z.jpg" and file "z" will be copied to the folder. It is the expected Behaviour. Is these the same issue your talking?"
> Is these the same issue your talking?" No. Please follow the steps to reproduce. This bug (filed in the Image viewer component) is about ... the Image viewer, not the file manager.
This has been fixed in package imageviewer-ui 3.4.05.1+0m5 which is part of the internal build version 10.2010.05-8 (Note: 2009/2010 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).