Skip navigation
ScottGemini
Currently Being Moderated

Text Entry Box Shortcut

Apr 10, 2012 5:25 AM

Tags: #text #shortcut #box #entry #teb

I have a problem with Captivate 5.5

 

When entering Text into a Text Entry Box with a shortcut assigned

 

     e.g. I have a Password Box where I instruct the user to type 'password'. I have a shortcut on the Text Entry Box of 'd'.

 

I expect it to take the user to the next slide/part of the slide as it has recognised not only the word entered but also that the shortcut key has been pressed.

It works fine in Captivate 4 but seems to be a problem in Captivate 5.5. Sometimes it will take the shortcut, sometimes you have to delete the shortcut and press the key harder and it will recognise it.

It works without failure everytime in Captivate 4.

 

I need it to work 100% everytime in Captivate 5.5

 

I have seen a few posts with the same problem but no answer.

 

Is anyone else having a similar issue, or can think of a way round this problem.

 

Thanks,

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Apr 10, 2012 6:46 AM   in reply to ScottGemini

    I believe this is a known issue.  I've seen the other posts as well and the only fix was to get the users to hit the key harder.  Not elegant I agree.  Feel free to add your voice to those that wanted to see this fixed by reporting it as a bug.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 10, 2012 7:05 AM   in reply to RodWard

    HI all

     

    LOL, y'all are cracking me up with the "hit the key harder" bit.

     

    Keys on the keyboard are simply switches that control an electrical connection to send signals to the applications. Because of this, they typically aren't pressure sensitive from the standpoint of a harder keypress being interpreted one whit differently than a softer keypress. It's like slamming the old style telephone down in the thought "that'll show 'em!". Sure, it does you good by allowing you to vent frustration, but the phone and the recipient won't care because all that really happened was that the electrical switch was triggered to disconnect the call.

     

    My thought here is that it's all about the timing involved. Perhaps check the pausing points?

     

    Cheers... Rick

     

    Helpful and Handy Links

    Captivate Wish Form/Bug Reporting Form

    Adobe Certified Captivate Training

    SorcerStone Blog

    Captivate eBooks

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 10, 2012 7:12 AM   in reply to Captiv8r

    I know it SOUNDS bizarre, but I distinctly remember this issue cropping up before on the forum, maybe a year or two back.

     

    Scott, you say you found other posts mentioning the same issue where the solution was to push harder on the key.  Can you remember how you found those threads?  Rick's disbelief has got me intrigued now.  I want to make sure my memory isn't playing tricks on me.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 10, 2012 7:56 AM   in reply to ScottGemini

    Hi all

     

    Here is an analogy. To type bold letters, you don't strike the keys harder to make them bold, do you?

     

    My point about the timing isn't about how rapidly the key is pressed. Moreover, it's about the timing of when the keypress is sensed. Consider this. If you take something like a Click Box object (which also pauses the slide) and you give it a shortcut key and time it so it appears at perhaps four seconds and pauses after perhaps 4.5 seconds, then ensure its action is configured to Go to the next slide. When the slide plays and the user presses the shortcut key that clicks the Click Box before the appearance point has been reached, it will appear as if the keystroke is being ignored. And in frustration, perhaps the key is banged on really hard. But at the time the key has been banged on really hard, enough time has elapsed so as to allow the Click Box to appear. In this case it will certainly appear that a harder keypress MUST have been what is needed in order to make things work, when in fact, the object simply hasn't appeared yet to become available for clicking.

     

    I'm not saying this is the case here. In fact, there could very well be a bug we are seeing with the Text Entry Box. Perhaps the coding of it causes the keypress to be ignored for some obscure reason and only after repeated attempts does it finally work.

     

    What I'd suggest as an experiment would be to put this through its paces where you see the shortcut appearing to be ignored. But instead of pressing the key again but this time with much vigor, wait a second or two. Press lightlly. If it fails to respond, press again but hold the key briefly before releasing. My thought here is that it's all in the timing of whatever is going on behind the scenes of when the object is "listening" for the trigger.

     

    Of course, only one of the development team can honestly tell us what is going on here. And even then, likely only after they have analyzed things from their coding perspective.

     

    Cheers... Rick

     

    Helpful and Handy Links

    Captivate Wish Form/Bug Reporting Form

    Adobe Certified Captivate Training

    SorcerStone Blog

    Captivate eBooks

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 13, 2012 3:09 AM   in reply to ScottGemini

    Hi Scott

     

    Yes, this is currently driving me bananas. I have text entry boxes with the shortcut set to Enter. I also have the TEB button set to invisible and stretched across the entire slide so that the user has the option of pressing Enter or clicking anywhere on screen.

     

    I've had this working in Cp5 - no problem. Now I'm using Cp5.5, the Enter key works only sometimes, I have many of these configured (one on each slide) and have compared the set up of each, but some work and others don't.

     

    ... and it does appear to be that pressing the Enter key a second time works sometimes, but then sometimes it doesn't as well. I've moved the timing around, but I have not had any success.

     

    I really need to understand this, any assistance or advice would be greatly appreciated.

     

    Regards

    Amanda

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 13, 2012 5:52 AM   in reply to ScottGemini

    Hi folks

     

    For the future, please consider bypassing support and submitting a Wish Form/Bug Report. (link is in my sig)

     

    Each of these submitted actually end up in front of the development team. (and you save yourself the frustration of dealing with support and teaching them how to use the software)

     

    Not only that, but Adobe prioritizes enhancements and bug fixes based on the number of these they receive.

     

    Cheers... Rick

     

    Helpful and Handy Links

    Captivate Wish Form/Bug Reporting Form

    Adobe Certified Captivate Training

    SorcerStone Blog

    Captivate eBooks

     
    |
    Mark as:
  • Currently Being Moderated
    May 8, 2012 7:29 AM   in reply to ScottGemini

    Hello

     

    I encountered this problem in Feb this year and originally as I was new to Captivate presumed it was something I had done wrong! I had started using Cap 5 originally and thought it was something to do with the re-format of templates in Cap 5.5. I remade all my slides and still the same problem. It really does seem hitting <enter> harder moves the slide on!

    The intermittence of this problem is very frustrating it changes all the time, sometimes its flawless then you just can’t move the slide forward at all!

     

    Regards Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2012 1:40 PM   in reply to ScottGemini

    I too am having that issue with a click box that has an Enter Key shortcut.  Sometimes you need to hit the Enter Key twice for it to work.  I have it on an assessment module and I'm not sure how it impacts the scoring on that item.

     

    Donna

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 1:29 AM   in reply to DEversole

    I just can't believe they still haven't fixed this bug or they even dared release the software with such a fundamental flaw. How are you supposed to create software simulations with an application which isn't cheap and doesn't work as it should! If this was a Microsoft app then people would be shouting from the roof tops! Wake up Adobe

    
     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 5:45 AM   in reply to ScottGemini

    Can i get below infomation regarding this issue.

     

    Is this issues reproducible in Cp 6.0 version??

     

     

    Can you attach the projects or sample project where the issues is present, so that we can debug and understand more about the issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 5:57 AM   in reply to NarutoCaptivate

    I haven't used Cap 6, and in fact it was only recently that I found out version 6 was out! I'm not sure if my employers will be happy especially as we upgraded our e-learning suite towards the end of last year so we could use 5.5.

    I can show this problem via webex, I would have to check to see if I can release files out?

     

    
     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:18 AM   in reply to R Thyme

    I am using version 5.5 of Captivate.

     

     

     

    Donna Eversole

     

    <mailto:deversol@comcast.net> deversol@comcast.net 

     

    ......__o

    ....'\  <;

    ...()_()__

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:21 AM   in reply to NarutoCaptivate

    I can attach a file with a slide copy but my project has 52 slides.  I’m currently working with the support staff on an issue of scoring inaccuracy of the project.  Can I get back to you on this?

     

     

     

    Donna Eversole

     

    <mailto:deversol@comcast.net> deversol@comcast.net 

     

    ......__o

    ....'\  <;

    ...()_()__

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 5:35 PM   in reply to ScottGemini

    For the record...I've been working with Captivate since version 1 and on this forum almost ever day since 2006.  I've NEVER seen Adobe give any kind of undertaking to anyone logging an issue as to whether they will or will not fix it and by what date.  If you logged a bug with Microsoft or Apple, I doubt you'd get any different response.  It's just business.

     

    So by all means log the issues, and you are correct that if MORE people log the issue the likelihood it will be fixed increases.  But expecting Adobe to give you some kind of personal commitment or a deadline for fixes will only increase your frustration levels.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 4:40 AM   in reply to ScottGemini

    The link to the bug report or enhancement request form is always found on the forums. Captiv8tr told you in his post above that the link was in his signature,

     

    To save you looking for it again, here it is:
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=5

     

    I don't know if the issue has been resolved yet in Cp6, and since it's a bit random anyway, there's no guarantee that if I tested it on my setup that this would mean it would work for you. 

     

    If you want to see if the issue is resolved in Cp6, all you have to do is download and install the trial version, upgrade or recreate a small project that evidences the issue, and see if it works any better.

    
     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 4:57 AM   in reply to RodWard

    I think this needs to be resolved in 5.5 people should not be forced to upgrade to 6, it worked fine as far as I am aware in v5. Anyway I don’t want to know if it works in v6 as I have no intention in purchasing this at the moment. As we have all already said this glitch stops a fundamental process which should work. I’m sorry but its rubbish and I think its poor that I am having to write this. Other software companies have bugs as well but if this was a Microsoft app I reckon it would be fixed, again it’s a fundamental feature that just doesn’t work.

    
     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 5:22 AM   in reply to R Thyme

    I beg to differ...but...this is an intermittent issue that has been notoriously difficult to pin down.  Yes it does occur, and nobody is denying that.  That we (Adobe included) would like to see it fixed is also a given because no sane successful software company turns a blind eye to annoying bugs. 

     

    But in order for them to do so, they need to be able to reproduce it from sample files.  A few posts ago on this thread Vish from Adobe asked if anyone could send him project files that show the issue in order to research it, but as far as I can see in the threads, only one person offered to do so.  So Adobe IS willing to look into this for you.  How did you help them resolve it?

     

    If you REALLY want to see this issue fixed (as opposed to just complaining about it) then send some files to Adobe.  No one is asking you to send proprietary information.  Just mock up a small project that shows the issue and send them to Vish on the email address he provided.

     

    If this was a Microsoft app and you complained about some issue but were unwilling to send them the required files to debug it, then I fail to see how they would be any further ahead than Adobe.  I don't work for Adobe and they don't pay me.  But I grow somewhat tired of people bagging them for issues when they're making every effort to do the right thing.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 5:26 AM   in reply to RodWard

    I am happy to send some files in, how do i go about this and i will send a cut down version of the project that went live.

     

    I hope this helps?

     

    Cheers Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 5:37 AM   in reply to ScottGemini

    Hi Scott,

     

    Can you please send me the Cp 5.5 files where you are finding this issue as either attachment through mail to mathkyar@adobe.com or

    Upload the files to Acrobat.com and send me the links.

     

    Thanks,
    Vish.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 5:39 AM   in reply to ScottGemini

    My apologies.  If you've already sent files into Adobe, that's great.  Well done.  Hopefully more people will follow your example.

     

    (By the way, for others wanting to know how to send files, you can attach files to the Bug Report when you log it.)

     

    However, I stand by my advice that if this issue is VERY important to you then you should at least download and test the trial version of Cp6 to see if the issue has been resolved.  If Cp6 resolves it then you at least know one way to solve it. 

     

    Whether Adobe chooses to release a patch for Cp5.5 is anyone's guess, but my personal observation is that they would only be likely to do this if many users were complaining about the same thing.  As annoying as this issue might be, it has only cropped up very infrequently in the forums as far as I can remember.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 6:49 AM   in reply to ScottGemini

    Oh well, I guess it's just not that important then.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 6:59 AM   in reply to NarutoCaptivate

    Hi Vish

     

    I have sent you a file to the address you have provided.

     

    Have fun.

     

    Adam

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2012 7:12 AM   in reply to ScottGemini

    Scott, you're really missing a golden opportunity here. 

     

    Vish isn't just some Adobe support flunky reading a script of the screen in front of him to try and diagnose an issue he knows nothing about.  He's one of the Adobe Captivate Dev Team members.  He's one of the dudes that builds this app, and he's offering to PERSONALLY take a look at the issue for you!  All you have to do is take a few minutes to send him some files.  He's not asking you to spend any money.

     

    If as you say it is "VERY important", and you wanted ANY chance whatsoever of getting a fix for Cp 5.5 (let alone Cp6) then THIS is your chance.  Don't muff it.

     

    And for the record...Talking up "pirating software" on a software manufacturer's web user forum is NOT going to win you ANY points with the people you expect to help and support you.  They'd be quite within their rights to regard that as offensive.  Bad move.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 3, 2012 7:54 AM   in reply to RodWard

    I worked with Vishal at Captivate Support to correct the issue.  It is important to make sure the settings under actions are set to go to next slide upon Enter, when using a textbox with a shortcut keystroke.  I finally got it to working correctly with these settings.

     

     

     

     

     

     

     

    Donna Eversole

     

    <mailto:deversol@comcast.net> deversol@comcast.net 

     

    ......__o

    ....'\  <;

    ...()_()__

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 3, 2012 8:00 AM   in reply to DEversole

    I  see my settings picture did not post. 

    Under the Action setting make sure that " Go to next slide is selected"  upon use of Enter(or shortcut key).  Specify the number of attempts and upon last attempt...."Continue" is selected.

     

    By using this setting with a textbox and shortcut key, the assessment module works as it should.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 4, 2012 1:03 AM   in reply to DEversole

    DEversole, i think its safe to say after nearly 2 months of looking at why this didn't work and involving atleast 2 qualified Captivate tutors that 'Go to next slide is selected" upon use of Enter(or shortcut key). Specify the number of attempts and upon last attempt...."Continue" is selected' was looked at...!!!!!

    

     

    Its in Adobe hands and maybe it can get resolved.???

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 4, 2012 4:13 AM   in reply to R Thyme

    All I can say is that Vishal looked at my file and that was the thing that fixed the issue in my assessment module.  It works now and I had built it correctly with the exception of those settings.  I am very satisfied with how my issue was resolved with Vishal’s help.

     

     

     

    Donna Eversole

     

    <mailto:deversol@comcast.net> deversol@comcast.net 

     

    ......__o

    ....'\  <;

    ...()_()__

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points