Unable to click on the *next* mockup to change slides

In the left-hand “Mockups” panel (as seen in screenshot, in v3.5.15 on a Mac), I can’t click on the mockup below the one that I’m currently viewing. Clicking on it does nothing, or, more specifically, it’s clicking the one above it (which makes it look like nothing is happening). Because, if I double click on the one below the one selected, it asks me to rename the one above it. So, in my screenshot, I’m looking at v1, but I can’t click on v2 to select it or rename it. In order to rename it, I have to click on another mockup (e.g. Today’s UI) and then click on v2. This issue seems to always only affect the slide after the one selected.

Any idea how to fix this? I can always use the keyboard shortcut to go to the next one, but it trips me up and slows me down more frequently than I’d like to admit (usually when trying to rename newly copied mockups.

Hi @grebe,

Thanks for the post. Sorry for the annoyance here - I know it must be frustrating. We’ve seen incidences of this behavior before and it’s normally a temporary issue with the underlying framework on which the desktop app is based - Adobe Air.

It’s a little inconvenient but you can usually resolve the issue by just saving your project, quitting the application completely and restarting it. Can you give that a go and let me know if the problem is resolved or the issue persists?

1 Like

Interesting - that would answer why I don’t see it all the time, but when I see it, it’s always there. I couldn’t figure out when I wasn’t seeing it, but it sounds like upon freshly opening it.

Def. inconvenient, but I’m so thankful there’s a workaround!

1 Like

Hi grebe,
I have the same issue on my Windows PC. Try to click on some other mockup in the left panel, and then click on the target mockup again. It should switch then, it works for me.

1 Like

Came here with the same problem with an addition: dragging assets from the top bar into the slide is also disabled/broken. Luckily I can then still add items from the top bar by double clicking on the item.

Thanks for the workaround. I’m curious to know if there is some way I can prevent this bug from popping up?


That sounds like an old bug we had, @Maarten. Are you using 3.5.16?

Hi Brendan,

Not sure which version but I do know I downloaded it no more than 2 months ago.

I won’t be near my computer for 2 weeks so can’t check.


I understand Maarten. When you’re able and ready, can you download the latest version (3.5.16) from https://balsamiq.com/wireframes/desktop/, install it and let us know if the issue persists. Thank you.

Just FYI: I am using 3.15.16 and unfortunately this issue did happen to be again yesterday. As before, closing Balsamiq and re-opening it fixed it.

FOLLOW UP EDIT: I just downloaded 3.15.17 so I’ll report back if I see it again.

1 Like

You probably will. @grebe, unfortunately. 3.15.17 was a quick update to fix some menu issues.

This bug is a memory leak that we haven’t been able to track down. That’s why closing and reopening fixes it.

1 Like