Changing fill in an Smartshape is disrupting advanced actions

[Justenuf2bdangerous]

Is this just a glitch, or a bug that needs reporting? We're building a simulation and needed to create a smartshape that had two versions of an image as the fill for two different states. this smartshape is hidden during the early stages of the interaction, then hidden again after the action is completed and the simulation moves on. In order to accomplish this there are actions incorporated into the slide that first hide the shape on entry (because it's possible to return to the slide later), then show it when the correct action is triggered. Once shown, a button is activated with the simple advanced action to "show next state" allowing the user to toggle through the states continuously to simulate the actual inputs. On exit from that part, the smartshape is hidden again to allow further simulation to take place.

The problem arose when we were asked to change part of image fill. When we opened the smartshape and changed the fill (not the name of the shape, not the state names, not the location or n anything else - just the fill) - all the commands related to the smartshape in all other advanced actions defaulted back to "continue" as if the smartshape itself had been deleted and replaced with a completely new object.

Any ideas as to what happened here? Basically, its like I changed the color or corrected text inside the shape and it broke all its relationships - which can't be a good thing.

[Lilybiri]

Shapes and advanced actions are my 'specialty' I was puzzled by your question, because I never experienced this behavior. I tried to reproduce it but without success. My test project was like this:

• Created a smart shape with two states, each with a different image fill
• Added a shape button that triggered a simple statndard action
  • Play audio clip
  • Delay Next actions by 3 seconds
  • Show Smartshape
• I changed the image fill for both states in the smartshape, and the advanced action did not change at all

My first idea is that you have a conflict with names. I'm used to label most objects, but certainly each object that is used in an advanced action. What about the naming in your example?

[Justenuf2bdangerous]

We're going to run this again this morning and change the shape name from the default to see what happens. The name was not changed, just the fill. It may take a while to unwind this and see if there is another element that could have disrupted the associated actions. The simulation is for an interface that has multiple buttons that change their function in response to previous selections, so each screen has several sets of actions prior to branching off into the subprogram screens. Everything else seems to be working as expected, but this glitch caught my attention - it could make using states less attractive in a complex layout.

[Lilybiri]

I never did see that problem, and I am using shape buttons all the time in

combination with advanced/shared actions. It is also the first time this is

signalled in the forums, where I am often around.

On Jan 27, 2017 2:40 PM, "Justenuf2bdangerous" <forums_noreply@adobe.com>

[Justenuf2bdangerous]

OK - this is obviously a "glitch" associated with this particular program. After resetting the advanced actions with the correct object name again, we attempted to reproduce the issue and the project functioned as expected, without dropping the object. We opened a copy of the project on another computer with the issue still intact and did exactly the same thing and had no problems there either. We are going to consider it a one time glitch at this point, but keep an eye out moving forward for any recurrences.

[Lilybiri]

Fine, keep us informed. Those issues are the worst, being inconsistent.