-
1. Re: Captivate 5 for Mac - keyboard commands not working
M_Anand Jul 18, 2010 9:56 PM (in response to jaimelee22)Hi there,
By any chance, does your keyboard has a single key for 'return' key and 'enter' key. In that case try pressing fncommandenter key combination.
Do let us know whether this resolved your issue....
-Manish
Blogs.adobe.com/captivate
-
2. Re: Captivate 5 for Mac - keyboard commands not working
jaimelee22 Jul 19, 2010 9:50 AM (in response to M_Anand)I ended up just changing the default key to something else (Option - S). I just can't understand why the default didn't work for me, but it doesn't really matter as long as something else does.
-
3. Re: Captivate 5 for Mac - keyboard commands not working
M_Anand Jul 19, 2010 11:16 AM (in response to jaimelee22)Hi Jaimelee22,
Does your keyboard has 'return' and 'enter' on the same key?
-Manish
blogs.adobe.com/captivate
-
4. Re: Captivate 5 for Mac - keyboard commands not working
jaimelee22 Jul 19, 2010 11:22 AM (in response to M_Anand)No. But I don't think it is an issue with the return or enter key because
none of the command keystrokes worked like they were supposed to either
(pause, pan, etc.).
-
5. Re: Captivate 5 for Mac - keyboard commands not working
M_Anand Jul 19, 2010 11:28 AM (in response to jaimelee22)Did you try using 'fn+command +F4' to start automatic panning.
-Manish
blogs.adobe.com/captivate
-
6. Re: Captivate 5 for Mac - keyboard commands not working
dowbright Jul 22, 2014 5:51 PM (in response to M_Anand)I'm in Captivate 8 now, after failing with 7. None of the shortcuts work on my Mac OS 10.9. Not with the function keys, and especially not with stopping a video with command-return, which is the equivalent of command-enter, since return also has the word enter written above it.
None of them worked in 7, either. I guess I need to learn how to make my own shortcut, since Adobe doesn't seem to be addressing this?
-
7. Re: Captivate 5 for Mac - keyboard commands not working
RodWard Jul 22, 2014 5:59 PM (in response to dowbright)If you're talking about keystroke shortcuts in published browser output, the issue is not Adobe's fault but the fact that browsers get first pick of the keystrokes and assign them to their own browser functions.
There is no way to control what the browser will or will not let through from within the Captivate content. Each end user's browser can have different settings.
My advice is to stop stressing about using keystrokes. There are some things that you can achieve when building an application that cannot be replicated exactly when building a browser-based simulation of that same application.



