I have created a software simulation which has a really annoying intermitent issue.
There are a number of validated TEBs throughout the project with the enter key set as the shortcut to go to the next slide..
My issue is that Captivate randomly chooses to ignore that enter has been pressed.. I have looked everwhere online and cannot find a solution to this issue.
I have also spoken to Adobe who claim they are not aware of any issue and it is fine at their end when trying to replicate.. I have sent them an example project so that they can see this bug in action.
Has anyone else come across this, and if so has any one come up with any work arounds?
I have also tried setting a button to transparent (it's shortcut as enter) but to no avail.
I'll probably move this discussion over into the Captivate forums area after I reply. So heads up on that.
It's been the source of frustration for many Captivate users. Some claim that it requires pressing the Enter key "harder" to make it work. Personally, I think the "harder" keypress is just voodoo and preposterous, as keyboards on computers are simply mechanical switches. My own view is that it's more related to timing than anything else.
I might suggest that you complete a Wish Form/Bug Report to alert Adobe about it. The more of these folks create about the same issue, the higher the priority is assigned to that issue.
Helpful and Handy Links
As I said, I'd advise to report to Adobe as a bug just to be safe.
Aside from looking at timing and configuration of the successful action (Go to next slide as opposed to Continue as well as looking at where the Pause point is) I have nothing to advise.
We have seen a few reports of the odd behavior but to my knowledge no definite "this fixes it" sort of solution.
Helpful and Handy Links
Hi there Folks.
I have spent a few hours with Adobe tech support and believe i have got to the bottom of the issue.. It seems that the outputted flash file does not always recognise the enter key when the play head is moving (Not paused). A work around i have found is to set the slide duration to 0.5 secs and "enter" seems to work fine. This allows the play head to stop quicker and minimises the risk of enter not being recognised. I need to test this further but it seems to work.
Ideally the playhead moving should not cause an issue however hopefully this may solve alot of user's issues
Hope this helps
I have experienced the same problem. After playing around with the TEB timing, I found that if the TEB has a short inactive time (active versus inactive is adjustable on the TEB in the timeline), when a learner enters the information and hits enter, the training progressed more smoothly.
Europe, Middle East and Africa