This happened to me many times: When creating custom buttons, and using images on their states, sometimes I can't see the transform handles when selecting them. In this file, buttons 1 and 2 don't show their handles when they are selected while button 3 does. What's wrong?
Hi Mauricio, I have seen this behaviour before and I think it is a bug within Storyline as there is no difference between the buttons. I also found that if I tried to use the Format painter to paint the button states it creates an error and doesn't work. You buttons are behaving the same way that I experienced. I never reported this bug to Articulate, as I always ended up just recreating the buttons.
Thanks! That's what I thought. After a year of working with Storyline, I've observed it's very sensitive about the order things are built, specially buttons. Adding multiple objects to states, using bitmaps on them and doing copy/paste is not stable at all.
Thank you for sharing your story file with us, and thanks Sam for stepping in!
I've never seen this error before with custom buttons. I've tried to recreate this in a new file and I'm not seeing the same outcome. I'm using the latest version of Storyline 360 which is Update 40 (Build 3.40.22208.0). Are you using this version as well?
I'd like to file a bug report so we can review error with custom button and not having the option to edit the size of the custom buttons.
Would you mind walking me through the steps you took? Also, are you seeing this in every project when creating custom buttons?
I'm excited to investigate this issue so that we can hopefully share a solution!
3 Replies
Hi Mauricio, I have seen this behaviour before and I think it is a bug within Storyline as there is no difference between the buttons. I also found that if I tried to use the Format painter to paint the button states it creates an error and doesn't work. You buttons are behaving the same way that I experienced. I never reported this bug to Articulate, as I always ended up just recreating the buttons.
Thanks! That's what I thought. After a year of working with Storyline, I've observed it's very sensitive about the order things are built, specially buttons. Adding multiple objects to states, using bitmaps on them and doing copy/paste is not stable at all.
Hello Mauricio!
Thank you for sharing your story file with us, and thanks Sam for stepping in!
I've never seen this error before with custom buttons. I've tried to recreate this in a new file and I'm not seeing the same outcome. I'm using the latest version of Storyline 360 which is Update 40 (Build 3.40.22208.0). Are you using this version as well?
I'd like to file a bug report so we can review error with custom button and not having the option to edit the size of the custom buttons.
Would you mind walking me through the steps you took? Also, are you seeing this in every project when creating custom buttons?
I'm excited to investigate this issue so that we can hopefully share a solution!
This discussion is closed. You can start a new discussion or contact Articulate Support.