Loading Profile...
Saving file on a read-only partition (or CD) without any error message
Hi,
Recently I opened a mockup from a partition mounted as read-only. After a few changes I planned to save it (as) on a RW partition, but accidently I pressed CTRL-S. I was astonished, but BM worked like normal (asterisk before a file name disappeared). Of course it was unable to write that file on RO partition and there is an error in logfile:
21:39:32 GMT+0100 save, saving currentPath in model:/mnt/temp/foo/test-file.bmml
21:39:32 GMT+0100 saveFileToDisk:/mnt/temp/foo/test-file.bmml
21:39:32 GMT+0100 #FM# saveFileToDisk error:Error: Error #3001
21:39:32 GMT+0100 #LSOMGR# getProperty cachedMockups, null, returning [object Object],[object Object],[object Object]
21:39:32 GMT+0100 #LSOMGR# setProperty: cachedMockups, [object Object],[object Object],[object Object]
(last two messages can be not related with save operation, but without seconds in log I can't be sure).
It's probably quite rare, but if there is no big problem with an implementation I think there could be some error message displayed on a screen to prevent saving changes in /dev/null :).
Balsamiq Mockups For Desktop version 1.5.24 and 1.5.26 on Linux (Fedora 8) and Windows.
Regards
Marcin
Recently I opened a mockup from a partition mounted as read-only. After a few changes I planned to save it (as) on a RW partition, but accidently I pressed CTRL-S. I was astonished, but BM worked like normal (asterisk before a file name disappeared). Of course it was unable to write that file on RO partition and there is an error in logfile:
21:39:32 GMT+0100 save, saving currentPath in model:/mnt/temp/foo/test-file.bmml
21:39:32 GMT+0100 saveFileToDisk:/mnt/temp/foo/test-file.bmml
21:39:32 GMT+0100 #FM# saveFileToDisk error:Error: Error #3001
21:39:32 GMT+0100 #LSOMGR# getProperty cachedMockups, null, returning [object Object],[object Object],[object Object]
21:39:32 GMT+0100 #LSOMGR# setProperty: cachedMockups, [object Object],[object Object],[object Object]
(last two messages can be not related with save operation, but without seconds in log I can't be sure).
It's probably quite rare, but if there is no big problem with an implementation I think there could be some error message displayed on a screen to prevent saving changes in /dev/null :).
Balsamiq Mockups For Desktop version 1.5.24 and 1.5.26 on Linux (Fedora 8) and Windows.
Regards
Marcin
I’m a little bit worried
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Marcin, thanks so much for reporting this. It hadn't occurred to me to test this case, and like you said it should be easy to fix. I think the right behaviour would be to pop open the "Save As..." dialog, perhaps with a message on it that says "could not save to xyz location, please choose another location".
I hope to fix it this week and post it live next week. Perhaps you could help me test it? I'll post back here once I have a fix to test.
I’m thankful
-
Inappropriate?It's nothing urgent, just a small issue.
I would be happy to help you and test your fix. -
Inappropriate?I've also seen this when using a source control tool to manage both .bmml files and .png snapshots - the tool (in my case perforce) sets the OS (in my case Windows) attribute to Read-only unless I have the file checked out. Balsamiq thinks I'm still able to save the bmml file, but the snapshot dialog just hangs there.
This is a little more important for me for the .bmml files so I don't have the false impression of saved work.
I’m anxious
-
Inappropriate?Hi there, I was thinking of fixing it by showing this dialog when this happens:
The same dialog would be shown both on save and export to snapshot if the bmml or png are read-only.
Thoughts?
1 Comment
Add a comment
This solves the problem
-
Does your solution let me save the file with a different name or path? Assuming the full path box was editable, this would solve the scenario for me as well as others I'm not currently facing, such as mount partitions &c. -
-
Inappropriate?Has this been fixed yet? I have the same problem but I am using a data management software to track different versions of the file. I found that since I don't have the file checked-out it is marked Read-Only and I shouldn't be able to save it. I made a few changes only to find out that they were not saved.
I’m frustrated
1 Comment Add a comment
This solves the problem
-
Hi there, it's not fixed yet, we're working on it!
-
Inappropriate?Same problem. Just lost an hour's work that I thought Mockups had saved but it hadn't because the files were read only (thanks to Perforce version control). Using version 1.6.8 on Ubuntu. I would suggest this is more urgent than adding any new features - silently losing work is a Very Bad Thing.
I’m very annoyed
1 Comment Add a comment
This solves the problem
-
Hi Day, you are totally right and I am sorry. We'll have at least a warning in the next build, hopefully by Tuesday.
-
Inappropriate?Hi all, I just added an error message when saving fails for any reason. Can you please help me test the new build from here http://www.balsamiq.com/products/mock... before I push the changes live in the 1.6 branch?
Please test save, save as, save all...it was a bit of a tricky fix so I'd like to make sure I didn't mess anything up...the tests pass on my end but you never know. Thanks and sorry it took so long to get to this.
I’m hopeful
-
Inappropriate?Wow quick response thanks! Have tried the fix and it works. When attempting to Save a single read only Mockup, I get a modal error dialog that says:
Unable to save file. Perhaps it's read-only? Please check your file system and try again.
Error: Error #3001
Small usability problem occurs when you have multiple read only Mockups open (4 or more) and try Mockup->Save All. Multiple error dialogs are stacked up on top of each other, and the translucent background gets applied multiple times so that instead of fading out the rest of the UI, they combine to black it out entirely:
Doesn't look good, but also you have to click ok on several identical dialogs, until you reduce the number of them to about 4 at which point the background UI starts to show through. Looks like nothing is happening for a while.
Stacked:
I’m thankful
-
Inappropriate?Have been doing some more testing and there is a bit of an issue with the fix.
To reproduce:
- Open a read-only .bmml file.
- Make a change
- Save
- Observe error dialog. :)
- Dismiss error dialog.
- Note that asterisk before file name (indicating unsaved file) has gone. Implies that Mockups thinks the file has been saved.
- Make file writeable (chmod +w, p4 edit, ...)
- Close Balsamiq Mockups for Desktop
- Not prompted to save unsaved changes. Changes are lost :(
I’m unsure
-
Inappropriate?Hi Day, I just fixed the two problems you reported. The new build is at the same address http://www.balsamiq.com/products/mock...
I tested it, but again it is a tricky fix so any help in testing will be greatly appreciated.
I’m thankful
2 people say
this solves the problem
1 Comment Add a comment
This solves the problem
-
Great thank you so much. After some quick testing things do look much better.
Only minor gripe would be that on the "multiple save of read-only files" issue, you now only get a single error dialog (good) but it just says "unable to save file" (singular) with no indication of which file(s) gave the error. The user can of course glance at the tabs at the bottom to see which files are unsaved (have asterisks in front of name) but this is not super-obvious. Certainly good enough to get me by though thank you. -
Inappropriate?I've just check a new version and it works correctly. Sorry that I could test it earlier.
Thanks for your effort!
I’m thankful
EMPLOYEE
EMPLOYEE
