Digital Workshop

I downloaded Opus Creator 9 and started working with it. I found out that the double click trigger does not work in a HTML5 publication, though it does work in the preview. Is it a bug or is it a known issue of HTML5?

Erik Hersbach

You'll probably get better answers for this over in the Evolution section of the Forum. Also, you need to update/provide a User Profile that will give info on your dev system and related environment including Browser details.

Not sure if Erikh has access to Evolution Lars.

May I ask you Erikh, why you need a double click action?

Cheers

Graham

AFAIK the latest generally accessible Opus and Creator downloads are some version of 8. And I just surmised that any discussion of Hxxx5 for now would be in the special grouping.

Good point Lar 123

Yep - confirming that the double click trigger does not work in FF, GC or IE

Not going to bother testing in Ios.

Single click works well, so would suggest going with that unless you have a special reason to employ the double click trigger Erikh

Cheers and thank you for reporting this bug

Graham

Apologies for any confusion - Creator v9 has not been officially released but some people have been offered an early bird upgrade.

These kind of issues should be directed to support with details of browser and operating system etc. in this instance Graham has kindly done half of support's work in confirming it is a limitation of HTML5 export and now development will have to decide whether to implement it or remove it from the interface.

This message will be deleted in due course as will any others about v9 until it is officially released.

Paul

Thanks to all who replied.

I would like to use the double click trigger, because I'm developping a speech test for children where they have to tell what's on a picture. By clicking on the left and right corner of a picture the test leader will navigate forward and backward in the test. With the double click action I want to navigate to a menu. When using the double click trigger you prevent accidental navigation to a menu by the test leader or child when working on a tablet. The triggers are atached to hotspots in the screen, because I do not want visible buttons in the test area/pictures.

How can I get acces to the evolution group?


Kind regards,

Erik

Hi Erikh,

The evolution section is subscription based - you'd have to discuss this with DW.

However, this might solve your problem by creating a faux double click.

1. create a frame with a single left click
2. add a hide frame for this frame
3. add a delay of about 0.5 seconds
4. add a show frame for this frame
5. set stop mouse click pass through on general tab for this frame

a. underneath the frame above, create another frame.
b. add a single left click
c. add a go to menu page


Mack

Erik,

Inspired by Mack's idea for a workaround, I began to think 'what issue is at play here'.

I do not have the newest version you do, so no way to test this out myself. But perhaps you can give this a try. It is a longshot and has a high probability of solving nothing. But it is simple to experiment with.

* take the double-click trigger off of the image object or other obj you use. (Opus Actions allow you to 'Comment Out' the trigger or parts of the action tree temporarily)
BTW, while you're there, Rt-Clk and Copy that Dbl-Clk Trigger.
* Create a Frame obj, as large as the image size (or hotspot, or area you want for the Double-Click). I think it is best, for now, if the Frame is on top of the image (i.e., what I really mean is higher in the Organizer Tree. )
* In Std Actions, make sure the Frame is selected and then Paste. (this procedure should Paste the Dbl-Clk Trigger along with any Actions you had under it. Make sure it is not commented out)
* I would recommend that your object that is the Menu, or contains the Menu, be placed inside the Frame we're creating here. (of course I do not mean just visually 'inside', but make the Menu obj a child of the Frame)

I think that is it, and you are ready to publish and test.

I would be surprised if this solves it, but my reading and my thinking leads me to want to try separating the scope of objects being operated on.... basically, do not have Mouse-click and Double-click on the same object (the image). And then by having Menu as a child of Frame, you might have a better chance of assuring appropriate (explicit) scope of control for the Dbl-Clk Trigger. Worth a try?

I've tried Lar's suggestion, but no succes.

In contrary to Creator 8 I can not attach a (single or double) mouse click trigger to a frame in Creator 9. Not even when making a flash publication. So I'm affraid Mack's solution in not going to work either.

Erik

Looking at the HTML5 code I wouldn't expect the Double Click to work but Left Mouse 'Single' works fine in Opus HTML5.

If you cannot even get this functioning, then I'd fire off an email to support as something is rather wrong.

I'm afraid I cannot test this as I don't have Creator 9.0 and I doubt I'd be allowed to show my suggestion working on an open board - but it really does work fine - so something is up

Mack

Hi Mack,

Don't get me wrong. Left click trigger works on other objects, except for the frame. I will send an e-mail to support about this.

Erik