Ive been making an e-learning with a lot of variables, and a lot of conditions, and now this far into the production, Im getting a bit confused about what a trigger that I may have built earlier is for.
Also, I think that if i ever had to make changes to this e-learning in the future, it would take me a LOT of work to recall/figure out which trigger was for what...
Is there any way we can add comments to triggers easily so we know why we put them there?
What I sometimes do is place a shape or a textbox off-screen and put all my notes in there. The learner will never see it but if you need to edit the course later you may find it useful.
I haven't seen a lot of posts about this - so I'd recommend you share directly with our product development team here in the form of a feature request!
+1 for this! Some of the lengths that we sometimes need to resort to when getting the presentations to "sing" will cause major heartache for a future maintenance programmer.
If you have to have your comment among a certain group of triggers:
Adjust variable Comment assign = "This is a comment" when timeline starts object = *
* - choose object among whose triggers you want the comment.
You can even make it "//This is a comment" if necessary :)
well, yes. you *could* do that. But the idea of actually causing code to execute at runtime unnecessarily is somewhat abhorrent.
*if* you were prepared to do such a thing (although it's poor practice), then you'd be better off putting fake JS triggers onto place and commenting within the JS about your other triggers (or doing some logging). This would still a bonkers way of doing anything though...
Ideally it would be good to see
1. allowing "grouping" of triggers into (multiple) user-definable categories so that we can track what the blazes each set of triggers are for. this is different to what objects a trigger may be associated with. These categories would need to be available across an entire story, not just within scenes or slides.
Thanks for chiming in to share that this is a feature you would like to see as well. As you can see, there have just been a few folx here who have mentioned this, and it was quite a few years ago.
12 Replies
Hi Jay,
What I sometimes do is place a shape or a textbox off-screen and put all my notes in there. The learner will never see it but if you need to edit the course later you may find it useful.
Hope this helps
Harri
Sounds like a good thing to do until Articulate do this for us! Thank you Harri!
No problem
I've just got to a very similar place myself.
As an ex programmer I'd really like to see some way to annotate some of the more complex things I've done.
An off screen text box is an unpleasant and seemingly unprofessional work around!
Hi Alan,
I haven't seen a lot of posts about this - so I'd recommend you share directly with our product development team here in the form of a feature request!
+1 for this! Some of the lengths that we sometimes need to resort to when getting the presentations to "sing" will cause major heartache for a future maintenance programmer.
If you have to have your comment among a certain group of triggers:
Adjust variable Comment assign = "This is a comment" when timeline starts object = *
* - choose object among whose triggers you want the comment.
You can even make it "//This is a comment" if necessary :)
well, yes. you *could* do that. But the idea of actually causing code to execute at runtime unnecessarily is somewhat abhorrent.
*if* you were prepared to do such a thing (although it's poor practice), then you'd be better off putting fake JS triggers onto place and commenting within the JS about your other triggers (or doing some logging). This would still a bonkers way of doing anything though...
Ideally it would be good to see
1. allowing "grouping" of triggers into (multiple) user-definable categories so that we can track what the blazes each set of triggers are for. this is different to what objects a trigger may be associated with. These categories would need to be available across an entire story, not just within scenes or slides.
2. comments enterable for each individual trigger
3. comments enterable for each trigger category
+1
Hi Marie-Jo,
Thanks for chiming in to share that this is a feature you would like to see as well. As you can see, there have just been a few folx here who have mentioned this, and it was quite a few years ago.
If you could share the details of the feature you would like to see, and how you would use it with our team here, that would be helpful.
Done
Perfect. Thank you!