Right Click Bug Puzzle (?)

Try to add a second trigger on button 1 as follows :

"Change state of Rectangle 1 to Hidden When the user right click"

Thank you so much Al !

Nice try!

But this is only a partial solution

Of course if you add that new trigger and then you right click upon Button 1 then Rectangle 1 is hidden ...

BUT (still) if you right click upon Rectangle 1 itself then Rectangle 1 refuses to be hidden ...

(somehow the right click event is absorbed and it never reaches Rectangle 1 ...

or something like that ... I do not know)

Nikos

Nikos, I'm seeing the issue you had described in your original post. It seems the stacking order of objects with right-click triggers determines which one is 'caught', and to me, that is unexpected behavior. I would open a support case for that here: http://www.articulate.com/support/contact/submit.php. As a workaround, would then use a layer to catch the second right-click. It's a 'hack', but at least it would allow you to finish your project on time.

Thank you Michael!

I totally agree with you ... IT IS NOT as expected ... and it has to do specifically with right click ...

(right click in a flash based project is somehow expected to be problematic ...)

I did open a support case ...

I' ll try to find a workaround ... new layers maybe ...

or the safe solution of using (let's say) a (new) button for hidding the rectangle(s) ...

I think there are some more similar or analogous puzzling triggering behavior cases I have come across ...

I will try to collect and post them in forums ...

Thank you once more for your help!

Hi Nikos, in my test I had used a layer and that seemed to work. See attached a simple example.

Michael thank you!

excellent and very simple way of solving the buggy behavior (from the user's perspective ...)

In my project I have to use not only one transparent Rectangle

but many freeform hotspots instead ...

that is because I want right clicking upon the button itself to lead to a different result

than the right clicking upon the  "rectangle" itself ...

so I have to cover the area of the rectangle (which is left around the button) with a freeform hotspot

and use another hotspot to cover the button itself ...

Also, in my project, the buttons and the initially hidden rectangles are on several layers and not on the base one ...

but I hope that that will be no problem (?) with a little fine tuning of their properties (I suppose) ...

But can right clicking on an object on a layer make hidden an object on another (lower) layer?

A layer can "see" the objects on base layer only?

(I am not so much experienced as you are ...)

IF NOT then I have to redesign the whole project or give up the transparent-layer-solution and use new button for triggering the right click actions ...

It is so much helpfull and valuable to have YOU all

(you ... expirienced storyline users and eLearning developers like you Michael ...)

around here ...

For now (in the relative support case) they seem to be missing the point ... but they will finally get it (I'm sure) ...

Hi Nikos, I'm glad this solution will work for you. Keep us posted about any other fix solution(s) you may get from your support case.

Cheers, Mike

Mike I have just edited my recent post ... and added those comments:

But can right clicking on an object on a layer make hidden an object on another (lower) layer?

A layer can "see" the objects on base layer only?

(I am not so much experienced as you are ...)

IF NOT then I have to redesign the whole project or give up the transparent-layer-solution and use new button for triggering the right click actions ...

What is you experience about that?

See a Storyline 4 workaround

based on the idea of Cleo Sinues ...

The attached .story file shows the problem (in Rectangle 2) and the solution (in Rectangle 1)

PS: ... when Rectangle 3 is in Normal state both rectangles (1 and 2) work as expected

... I will make a post here for Storyline 5

Nikos

The same solution stands for Storyline Update 5 also ...

The Transparent Rectangle should be placed above Rectangle 3 (which "causes" the problem when hidden)