Loading Profile...
opening bmml file doesn't retain uploaded image
Hi Peldi - I uploaded an image added some markup comments and saved as a bmml. When I open the bmml it say that image could not be found
4
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?Hmm, that's bad. Could you please email me the bmml file? What version # are you using?
-
Inappropriate?Ok, it should be fixed in the latest release. Thanks for the help debugging this!
http://www.balsamiq.com/products/mock...
I’m thankful
-
-
Inappropriate?Hmm... sorry to report, it isn't fixed for me. I've downloaded NEXT.139 and have the same problem I encountered yesterday. Haven't quite figured out the underlying logic that breaks the images, but it seems related to importing items from two different directories. When I first tried the new import feature, I was pulling in icons from a single source directory. Trouble cropped up when, needing a different sort of image, I added a separate folder dedicated to the non-icon items. If I create a new mockup, then import an image from the second directory, then open an older mockup that was using items from the first directory, the older mockup suddenly can't find its imported images.
If you select one of the images, it is correctly identified by name in the properties panel, but you have to re-select it from the upload dialog to get it to "take" again. So it seems to be some sort of path retention problem.
I’m having to redo some of yesterday's stuff.
2 Comments
Add a comment
This solves the problem
-
Sorry about that Michael...it's certainly related to relative paths etc. I store the paths as relative in the bmml file, but have to reconstruct the full path in order to load the image or AIR won't load it (what a pain). What OS are you on? -
This happens on a Wintel box -- I also have Mockups installed on a Mac at home, but haven't had a chance to test the problem there. Also, another observation, as I'm fixing the broken items from yesterday: I'd mentioned that the image names are still listed in the property panel. The full set of images for that mockup are also on the recent imports pulldown. When I re-import an image, it's then listed twice in the recent items list. Which means, if an image occurs twice in the mockup, I can correct the second one by selecting from the recent items list if I guess right about which one has the path that works.
-
Inappropriate?Here's an update on image retention, now that I've had a chance to load NEXT.139 on my home Mac. Should mention that what follows is not a made-up test scenario: I frequently VPN to my employer's servers to continue work on files that were created under Windows. That platform agnosticism is one of the great features of Mockups.
Pulled up one of the files from two days ago, that were giving me the trouble I'd described. No surprise, every imported image was broken. Pulled up one of yesterday's files -- the last one I'd saved before leaving work. This time, all the images loaded. Cool -- wasn't sure that the full paths as defined by the Wintel machine would be correctly parsed/reinterpreted by the Mac (especially because of the VPN routing).
Finally, with yesterday's fully-functional mockup in view, I performed a "New Clone of Current Mockup." Every single image winds up broken in the clone.
Puzzling. -
Inappropriate?Michael, thanks for the detailed reports. It might take me another few tries, but I am confident that with your help I'll be able to squish this bug once and for all. I hope to be able to spend some quality time on it on Monday morning.
I’m thankful
-
Inappropriate?Ok, I think I got it. The bug had to do with adding images to a mockup that had never been saved before (i.e. didn't have a "base path" to use when relativ-izing image paths yadda yadda...).
Let me know if it works for you!
1.NEXT.141 is here: http://www.balsamiq.com/products/mock...
I’m hopeful this is it for this one
3 Comments Add a comment
This solves the problem
-
OK, just tested again from the home Mac under NEXT.144. "New Clone of Current Mockup" still results in "Image not found" errors. Also, noticing some sub-optimal behavior when switching between mockups that include imported images: the images seem to be unloaded from memory whenever you switch between tabs, resulting in a delay, visible placeholders, and "loading" labels when you re-select a tab that was foreground just a second before. The effect is probably magnified by the VPN link from a slow home connection, but this still doesn't seem like the best behavior. Will create a file or two from home and pull them up on the Windows box at work tomorrow.
-
Oops, I had forgotten to check the "new as clone" option, I'll fix that ASAP. As for images having to reload when you switch tabs, that's a pretty hard one to fix, I'll think about it
-
Also, just found a quick, reliable way to generate broken images: 1) import a few to a new mockup (I pulled from two different sub-directories, in case that makes a difference). 2) Click "New Clone of Current Mockup" -- in the new one, none of the imported images will show. 3) Now click the tab for the mockup you started from -- you'll see "Image not found" errors where they'd properly displayed just a moment before.
-
Inappropriate?Ok, I think I got both of the bugs (clone and going back to a new mockup should work now). You can tell when a feature is a BIG one...it takes a while to hash out all the code-paths. I am pretty satisfied with where the code is right now, thanks for helping me clean it up!
1 Comment Add a comment
This solves the problem
-
NEXT.147 is behaving nicely at work this morning, so you may have swatted the last import bug. Will report back if any more images break. Also, it looks like the reloads-on-tab-switch are a lot less annoying when you're on a local hard drive or intranet pipe. Sort of a "blink" whey you switch tabs, so it's no longer a concern. Appreciate your persistence through the weekend in chasing this stuff down.
-
Inappropriate?It turns out there was still one case that was failing, which I just fixed. Let us hope this is the last one! :)
I’m happy
-
Inappropriate?I used 1.5.23 under Windows Vista for this.
I created some mocks in C:\MyMocks that used images. The images were stored in the same folder that I saved my mocks to.
Then I copied the C:\MyMocks folder to a network path called J:\MyName\MyMocks. When I opened the mock files from J:\MyName\MyMocks it could not find the images used by the various controls.
How can I tell Balsamiq that if any referenced images are in the same folder as the .BMML file that references them, then just use a relative path to the image file of ".\filename"?
1 Comment Add a comment
This solves the problem
-
Hi PqBob, I'll try to reproduce the bug following your instructions. If the images were sitting next to the BMML files, the links should have been for the ".\filename" form you mention, and thus have worked when you moved the whole folder around. In other words, you don't need to tell Mockups to use relative paths, it should do that automatically. I will look into why it doesn't in your case.
-
Inappropriate?The folder paths, C:\MyMocks and J:\MyName\MyMocks, were not the actual ones I'm using. This reply uses the actual folder paths.
The paths to the PNG files in the original folder all looked like this, i.e. “../../../Mesh%2520Files/Mockups/CHARTrunner%25204.0/filename.png”. This seems to be a relative path that finds its origin at the root of the drive. The original full path was “E:\Mesh Files\Mockups\CHARTrunner 4.0\filename.png”
<control>
<controlproperties>
<src>../../../Mesh%2520Files/Mockups/CHARTrunner%25204.0/Attributes%2520chart%252004%2520%28health%29.png</src>
<filter>true</filter>
</controlproperties>
</control>
I think this may be related to the “use an image prior to saving the BMML file bug” that I saw reference to earlier in this forum topic.
After I “reattached” the image to the control, using the BMML in the folder “J:\Bob\Misc\Mockups\CHARTrunner 4.0\” the file path now looked like,
<src>../CHARTrunner%25204.0/Attributes%2520chart%252004%2520%28health%29.png</src>
Unfortunately, that path is not portable either. If I put the BMML and PNG file into J:\Bob that relative path doesn't work.1 Comment Add a comment
This solves the problem
-
Hi PqBob, I found and fixed a bug that had to do with folders with spaces in their names. I'd love your help testing the new build before I put it into production. You can download the new build here: http://www.balsamiq.com/products/mock... - let me know how it works out!
-
Inappropriate?That seems to have fixed the problem. Thanks!
EMPLOYEE
