Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

When using an ELB interaction and the X that closes each popup window is slow to respond. I have to tap it many times before it closes.

Explorer ,
Apr 04, 2018 Apr 04, 2018

When using an ELB interaction, for the phone display (this is a Captivate 9 Responsive Project/running in Captivate 10) and the X that closes each popup window is slow to respond. I have to tap it many times before it closes. This behavior is constentent whether using an iPhone or Galaxy. I have checked to make sure there are no textboxes over the X.

I also moved it further away from the text boxes. How can I change it so that the learner can activate it with a single tap.

Thanks

234
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Apr 04, 2018 Apr 04, 2018

I think the X is too small and the one selected requires you to click right in the middle which is hard to do on a phone. Also, on the phone, the hand does not show when you hover over, so the user does not know that they are not on the "sweet spot".  I changed the close button to an Text Button instead and it works much better.

Translate
Community Expert ,
Apr 04, 2018 Apr 04, 2018

Maybe you could ask this question on the ELB website? We are not able to see which interaction you are talking aout, nor how it was set up. Help with Captivate itself and/or the packaged interactions can be found in this Captivate forum.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 04, 2018 Apr 04, 2018

I think this issue is relevant to any interaction. A more general question would be...if you designed an interaction (Captivate 9/responsive) an X to close the popup in the phone view, but there is a lag causing the learner to tap it multiple times, what could be some of the issues. I added an image

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 04, 2018 Apr 04, 2018

I think the X is too small and the one selected requires you to click right in the middle which is hard to do on a phone. Also, on the phone, the hand does not show when you hover over, so the user does not know that they are not on the "sweet spot".  I changed the close button to an Text Button instead and it works much better.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 04, 2018 Apr 04, 2018

Well that is simply bad design for a responsive interaction.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 04, 2018 Apr 04, 2018

Any suggestions on the best way to build this type of interaction in a Response environment.

I am publishing in html only, so i cannot use the Captivate interactions. There is a delay before the slide with the interaction deplays, so I am creating a lot of interactions on my own. But, this is the first mobile course I have built.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 04, 2018 Apr 04, 2018
LATEST

Captivate learning interactions are compatible with HTML5. The older widgets are not compatible.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Help resources