I need a solution that enables Captivate 8 to use the [ALT] + [F8] shortcut in an EXE file.

Report · Jun 17, 2015

I have tried everything that I currently know to fix this, but when the file is published, the [ALT]+[F8] shortcut does not work.

We've made simulations for this software using Captivate 3 in the past and did not have this problem. I know I might be grasping at straws, but I refuse to believe it was possible in Cap 3 and not in Cap 8.

Report · Jun 17, 2015

Hi there

What is the key sequence assigned to? And what is your project and output type? Much has changed since version 3 and Captivate 8 offers more project and output types than version 3 did.

Cheers... Rick

Report · Jun 17, 2015

I've tried both Click Boxes and Transparent buttons.

The project is a software simulation where [ALT]+[F8] opens a very specific comment window. It must be published as an .EXE file.

Report · Jun 17, 2015

Hmmm, that's interesting. I'm guessing the complaint here is that after you have published as EXE, Alt+F8 doesn't work? (That may sound incredibly silly, but sometimes folks will simply preview in the browser while developing and not actually create the EXE)

Assuming that's the case, I definitely smell a bug. And if so, that should be reported to Adobe.

For what it's worth, I just tried it on my own setup and the key sequence worked for me in both Captivate preview as well as the Google Chrome browser. While I didn't test the EXE output, I'm pretty certain it would work there as well.

Cheers... Rick

Report · Jun 17, 2015

You are correct - after being published as an EXE, the [ALT] + [F8] command doesn't work. I also tested in as a SWF in IE, but it didn't work there either. It DID, however, work in Chrome.

Adobe Tech support said there is no workaround for it.

Report · Jun 17, 2015

Well now, that's a bummer!

I know at one point Adobe dropped the ability to publish as EXE. They later added it back in. Looks like they certainly missed allowing some options there.

I'd encourage you to file a bug using the link below:

Click here to view the bug reporting form

Cheers... Rick