I’m using Balsamiq 3 for desktops. I tried to open a BMPR file that I believe may have been corrupt in some way - (I suspect it was a victim of a CR/CRLF swap.) It caused Balsamiq to become essentially unresponsive. I terminated the process (and even tried rebooting) but now when I double-click the Balsamiq application icon, it looks like Balsamiq is trying to find and open that mockup at startup, which is causing it to go unresponsive again.
I don’t know where that offending BMPR file resides or I would just delete it (the corrupt file was originally opened by my git client software and I don’t know where it has that file stashed.)
Can I force Balsamiq to start with an empty mockup rather than trying to reload the last file?