Skip to main content
bolanabolana
Known Participant
June 23, 2016
Answered

Multiple Advanced Actions on a single button in responsive project

  • June 23, 2016
  • 1 reply
  • 955 views

Hi everyone

I have a question about using advanced actions (or really any actions) on a responsive project.

I'm making a course that has a menu section which needs to be designed differently for mobile view (essentially buttons in a different format to accommodate screen size). I'm using Advanced Actions to hide/show buttons on the menu as I'm using transparent buttons and need some of them/all of them to be hidden so I don't get a text overlap when they are open or closed (so can't use states I don't believe).

My question is, is there a way that I can change the advanced action to be used on buttons in the i.e. mobile sections, so they perform a slightly different action on a mobile than the same button would on a desktop; essentially fires a different action? I've had a try of this on the basis that from a size, shape etc perspective for buttons/shapes and such, these are inherited from the top down unless changed. However for actions this does not seem to be the case, if I change the action in mobile view, this also changes the actions in a higher view, which does not work.

I'm wondering if anyone has come across something similar and knows how to do it or has a work around?

Thanks

Andy

This topic has been closed for replies.
Correct answer Lilybiri

Interesting question. My clients almost never ask for a responsive project, which means I cannot help you with real life experiences here. Just a couple of 'intuition' ideas. I don't think that you can have different actions triggered by the same event in the different breakpoint views. There is no system variable (yet) available that detects the used breakpoint view (hoping this will be the case in future versions). Maybe there is one (JS experts could help) but it is not made available.

Workaround: I didn't test this, but what if you use other events if you want a different advanced action? That means you cannot use Slide events. But you can move an interactive object out of a view and replace it by another interactive object: that means that you have another Success event that can be used for a different action. I will definitely try this out, if I can find some time

1 reply

Lilybiri
LilybiriCorrect answer
Legend
June 23, 2016

Interesting question. My clients almost never ask for a responsive project, which means I cannot help you with real life experiences here. Just a couple of 'intuition' ideas. I don't think that you can have different actions triggered by the same event in the different breakpoint views. There is no system variable (yet) available that detects the used breakpoint view (hoping this will be the case in future versions). Maybe there is one (JS experts could help) but it is not made available.

Workaround: I didn't test this, but what if you use other events if you want a different advanced action? That means you cannot use Slide events. But you can move an interactive object out of a view and replace it by another interactive object: that means that you have another Success event that can be used for a different action. I will definitely try this out, if I can find some time

bolanabolana
Known Participant
June 23, 2016

Hi Lilybiri

Thanks as always for your response. I'd already been through your blog hopeful you had already written about this!

I've just been having a think about this while sat outside and came up with a light bulb moment similar to your workaround. I was going to try deleting the button on a lower breakpoint view and adding another, and if that didn't work (deleted from everywhere) the next idea was to hide the original off the screen and have new buttons for the lower breakpoints. I'll give this a try and see how I get on!

I'll update when I know more and also raise a feature request

Thanks

Lilybiri
Legend
June 23, 2016

Which means that your "lightbulb" and my Captivate intuition agree? Let us hope they are correct. I will definitely check it out, am on a real responsive project for the first time at this moment.  I only blog about a use case when I have explored it in depth. Keep me informed, and log those feature requests (like having a system variable detecting the used view).