My states don't work like they are supposed to

I'm trying to emulate How to mark viewed tabs (http://learn.articulate.com/tabs-interactions/) and my states aren't working like they do in that screenr.

Around 2:51 in the demo he does a preview where he clicks on the button and it immediate goes to the selected combined with the visited "x"

In my case  I get the visited "x," but my button remains with the hover art and doesn't show the selected until I move the mouse outside of the artwork. And if I move the pointer back over it goes right back to hover.

First question: How do I get selected to appear immediately upon selection and not after I move away?

The other issue I'm facing is getting the button art set up in the first place. If I insert a button I don't see any way to change the shape of the button to have that chevron for the selected shape.

And if I draw my own shape I have problems getting the text to look right. For some reason when I duplicate the states the text doesn't show in the state preview panel. The text does show in the state when I preview/publish the story file. It is really strange.

Second question: How to make button artwork from scratch?

37 Replies
Mike Enders

Anna,

The basic gist is that your squares on each of your layers were covering up the pointer section of your arrow on the base layer.  So, the fix is to remove the squares on the layers and use the base layer square as your backing for each layer.  

https://mike.viewscreencasts.com/ce7e9143053a42399a2374584e250ccd

Mike

R Rothrock

Thanks Mike. That is (more or less) the process I followed. And for me I still get wonky selected states if I do it "my way."

The difference (and this is what seems to lead to the problem) is that I didn't draw over the top of the artwork. On the selected state.

I used Format > Change Shape. When I do that every time I get the problem.

The solution is pretty clear, "Don't do it that way."

However I think that what I did is a pretty reasonable thing to do. Maybe that could get fixed for the future?

Anna Porter

Mike:

Just wanted to report back that "support" was not very supportive!  He basically argued with me that first you didn't cover "visited states" in your video and then that a visited state wasn't really necessary in my case anyway!  See the full text of our emails below:

 

Hi Anna,

 

The visited state in your file, in my opinion, is the keyto this issue. In the tutorial, Mike did not use a visited state.

 

If you want to use a visited state to your button, itwill be better if you will apply the visited state by using variables. But ifthere's only 4 tabs, I think there's really not much use to it since thestudent can know that she had already visited all 4 tabs.

 

Variables are a way to remember information—such as auser's name or numeric input—and then present dynamic content based on thatinformation. They're also a great way to add conditional interactivity to yourcourse.

 

Storyline makes it easy to work with variables withoutwriting any code at all. Here's how:

http://community.articulate.com/tutorials/products/working-with-variables.aspx

 

Just reply to this email if you need more help.

 

Regards,

 

Sid Apolinario

Customer Support Engineer

Articulate Support - http://www.articulate.com/support/

 

P.S. How are we doing? Let us know.

http://www.clicktools.com/survey?iv=3912b7e23b10a2&q1=5004000000Mhhh5&q2=0034000000gJwus

 

 

 

--------------- [collapse]Original Message ---------------

From: Anna Porter[annamarie@porterworks.com]

Sent: 9/26/2012

To: Articulate Support [support@articulate.com]

CC: 

Subject: RE: Case #00297411: There seems to be a"bug" (...    [ref:_00D30Txo._50040Mhhh5:ref ]

 

Hi Sid:

This was an idea that staff member, Mike Enders,demonstrated on a recent video tutorial. It seemed like a good idea to let a student know for sure that he/shehas visited each button since that's a requirement before moving on.

 

Anna

Anna Porter

 

360-631-5631 w

425-753-0385 m

360-652-9332 f

annamarie@porterworks.com

www.porterworks.com

 

    

 

 

-----Original Message-----

From: Sid Apolinario,Articulate Support [mailto:support@articulate.com]

Sent: Tuesday, September 25, 2012 9:23 AM

To: annamarie@porterworks.com

Subject: RE: Case #00297411: There seems to be a"bug" (... [ ref:_00D30Txo._50040Mhhh5:ref ]

 

Hi Anna,

 

Thanks for contacting Articulate Support!

 

Quick question please. Since your buttons only showslayers but stay on the same slide, why do you need to use a visited state?

 

Just reply to this email if you need more help.

 

Regards,

 

Sid Apolinario

Customer Support Engineer

Articulate Support - http://www.articulate.com/support/

 

P.S. How are we doing? Let us know.

http://www.clicktools.com/survey?iv=3912b7e23b10a2&q1=5004000000Mhhh5&q2=003

4000000gJwus

[/collapse]
Mike Enders

Anna,

Sorry about that!

As I reviewed your file some more, I may have been mistaken in my saying that it looked like a bug.  The reason that both the X and the triangle show up is that the hover state is still active.  So the X shows up once the tab is visited, but the triangle that resides on the hover state will continue to show up when you hover over the button.  It's just not real noticeable on mine due to the coloring and size.  So this would be a design consideration when you're creating the visual look of each state.

Mike

PS.  And I would be remiss if I didn't add that Sid and the support folks really are awesome.  I'm not sure Sid was arguing as much as trying show another option.