Bug: Export Snapshot to PNG Replace/Overwrite acts weird
Hey,
I think I just found a bug:
System: OSX 10.5
Mockups Version: 1.5.12
Problem: Overwriting an existing PNG file recursively re-creates the files path within the path. e.g. overwriting /foo/foo.png will create a new file in /foo/foo/foo.png instead of overwriting the file.
Steps to reproduce:
1) Open Mockups, new empty mockup layer shows
2) Add any element (lets say an Arrow)
3) Hit Mockup -> Save, save to /Users/felix/foo/foo.bmml
4) Hit Mockup -> Export Snapshot to PNG File (creates /Users/felix/foo/foo.png)
5) Repeat: Hit Mockup -> Export Snapshot to PNG File
6) Choose "Replace existing file"
7) File ends up being saved in: /Users/felix/foo/Users/felix/foo/foo.png
Hint: This may be related to: http://getsatisfaction.com/balsamiq/t...
Also: When I just tried reproducing this for reporting the bug I sometimes hit the case where I could not click either the "overwrite" nor the "create new file" buttons in the modal dialog which I worked around by restarting the app.
Quick help would be highly appreciated : ).
-- Felix
I think I just found a bug:
System: OSX 10.5
Mockups Version: 1.5.12
Problem: Overwriting an existing PNG file recursively re-creates the files path within the path. e.g. overwriting /foo/foo.png will create a new file in /foo/foo/foo.png instead of overwriting the file.
Steps to reproduce:
1) Open Mockups, new empty mockup layer shows
2) Add any element (lets say an Arrow)
3) Hit Mockup -> Save, save to /Users/felix/foo/foo.bmml
4) Hit Mockup -> Export Snapshot to PNG File (creates /Users/felix/foo/foo.png)
5) Repeat: Hit Mockup -> Export Snapshot to PNG File
6) Choose "Replace existing file"
7) File ends up being saved in: /Users/felix/foo/Users/felix/foo/foo.png
Hint: This may be related to: http://getsatisfaction.com/balsamiq/t...
Also: When I just tried reproducing this for reporting the bug I sometimes hit the case where I could not click either the "overwrite" nor the "create new file" buttons in the modal dialog which I worked around by restarting the app.
Quick help would be highly appreciated : ).
-- Felix
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 the_undefined, sorry this made you sad but I have good news: I was able to reproduce the bug, so a fix is not far. That part of the code is a bit tricky so I'll fix it in the morning with a clear mind (it's been a long day). Thanks so much for the detailed repro steps and stay tuned, I am confident we'll squash this tomorrow.
I’m thankful
1 person says
this solves the problem
-
Inappropriate?No problem : ), thank you so much for looking into this so quickly!
I actually am using the awesome shell integration now for converting all my mockup source files to png's.
It's probably not critical for most people, but while experimenting with that I also noticed that if you try to run the export while Mockups is already opened it doesn't generate the PNG and throws this error:
2009-01-06 19:38:28.144 Balsamiq Mockups[77287:10b] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be 'Editor', 'Viewer', 'None', or 'Shell'.
(However, I'm not sure if this error is related as I also get it during successful exports when Mockups is closed).
I’m happy
-
Yes I don't know about that NSDocumentController thing...it just started with Air 1.5 I think...seems like a harmless warning... -
Inappropriate?Hi Felix, I got it! Can you please install the pre-release build here: http://www.balsamiq.com/products/mock... and help me confirm the fix? If you do, I'll merge it into 1.5 right away as it's not a very nice bug to keep in there... :)
I’m hopeful I squashed it!
1 person says
this solves the problem
-
Inappropriate?Works perfectly! Thank you so much. I kind of dig this entire AIR installing / updating process.
Btw. I haven't expressed this anywhere else so let me just do it right here. I really love the application and I actually read pretty much all of your blog postings since day 1 (the archives from before you launched). Your success is really inspiring!
-- Felix
I’m excited
Loading Profile...



