I have been creating some View/Try/Test mode material from Screen recordings in SL3, however when I look at the slides that include Text Entry, I have an unassigned trigger automatically created. Although all modes work perfectly, I am curious why this is there (on every once created with a Text Entry' field and whether it should be edited or removed.
I have added a PNG screen shot of the unassigned trigger.
Thanks for including the screenshot! I'd be curious to take a closer look at your file, as this 'unassigned' trigger doesn't normally appear when you insert a screen recording slide with text entry.
Would you mind sharing a sample of your file with me? You can attach it directly to a new thread comment.
Sorry for the delay in responding, however due to confidentiality I am unable to share content. However I believe I have found out why it happened. I recorded myself logging into a system (using my username and password) and then changed the 'Text' answer on the Try and Test files (changed it to a generic username and password) and once I did this, it made the original created trigger unassigned. I have tried it without changing my login details and the duplicate trigger does not occur.
Ah, great find! Thanks for sharing that with me, Anthony. Good luck on the rest of your project, and let me know if you run into any more snags along the way!
3 Replies
Hi Anthony!
Thanks for including the screenshot! I'd be curious to take a closer look at your file, as this 'unassigned' trigger doesn't normally appear when you insert a screen recording slide with text entry.
Would you mind sharing a sample of your file with me? You can attach it directly to a new thread comment.
Hi Alyssa,
Sorry for the delay in responding, however due to confidentiality I am unable to share content. However I believe I have found out why it happened. I recorded myself logging into a system (using my username and password) and then changed the 'Text' answer on the Try and Test files (changed it to a generic username and password) and once I did this, it made the original created trigger unassigned. I have tried it without changing my login details and the duplicate trigger does not occur.
Thanks
Ah, great find! Thanks for sharing that with me, Anthony. Good luck on the rest of your project, and let me know if you run into any more snags along the way!
This discussion is closed. You can start a new discussion or contact Articulate Support.