New thread discussion greyed out and marked Reported

The system has rules in place to mark as spam and then the Articulate staff will unplug it. Normally happens if you post too many times too quickly. But, looking at the post that would not be the reason, maybe the video

Unless of course someone reported you and then the same thing happens.

Thanks, Phil. I wasn't aware that there was a limit to how many posts we can make in a day. I might have replied to 4 posts over the last 48 hrs (I know, crazy, right?), which is probably the most prolific I have ever been on this site.

I am consciously trying to be more helpful on these threads due to the number of times I log in to plea for assistance, and invariably get it.

I am also trying to mitigate against all the ranting I do about the sheer flakiness this software is at times, and hopefully not end up chastised and banished like a recent, beloved and very helpful Hero has been treated.

So this just feels... weird. I have a genuine grievance that Storyline is screwing up triggers, and I have video evidence to illustrate it. I sincerely need assistance on these trigger issues as my client needs these projects to go live ASAP.

The feedback from my original Trigger Warning thread, from the support team, was to take a look at my file, be unable to replicate the issue at their end (despite them providing video evidence that they didn't follow my process exactly AND showing a trigger not being editable when it should have been) and then have the temerity to provide the old "Storyline 360: How to Fix Unexpected or Erratic Behavior" link. Honestly, that should be this site's homepage.

As it stands, I have a deeply unhappy client who is becoming increasingly exasperated at the number of times I seem to be having 'issues' with my work tools and I am spending more and more time trying to solve issues that shouldn't be issues, dealing with disappearing Triggers, Triggers not responding to other Triggers and Triggers not disappearing when deleted until some weird key combination is performed 3 times, in a clockwise direction under a blood moon.

Ha. Irony. Posted twice in 1 minute. I see how the system works now... :)

4 posts shouldn't do it, for me it is normally if I post something very quick.

I have seen the deleting issue a few times, and it often goes hand in hand when copying and pasting slides stops working but duplication does. I think it is resource/undo related as closing and reopening fixes it.

I can have a look at the video not sure I will be any help though.

Thank you, Phil, so much.

here is a link to the video. I don't want to post it into this thread in case that might be what is causing the 'grey-out':

https://vimeo.com/757404493

For the sake of completeness (and not asking you to look at it, at all) I am attaching the file in question as well as the published output.

I cannot delete the conditions which is odd.

In terms of why it doesn't work, I am not sure. Mainly because I am not sure what it is meant to do.

I would have probably built it slightly differently possibly using a freeform Drag and drop. But the main thing for me would be to get most of the triggers onto layers so when you drop an object it shows the layer which runs the triggers and then closes the layer. It just helps me to troubleshoot. 

Thanks again Phil. Yes, I know. I shoulda/coulda/woulda done it differently but I'm under enormous time pressure to convert an existing Dragon Drop to be accessible and found Sally Wiedenbeck's solution on these boards, but it became exponentially more difficult keeping track of what was moving to where, what states should be monitored and how Storyline could monitor if the activity was attempted (Invalid Answer) and also provide a Try Again.

Dragon Drops aren't a great educational tool and nearly all my clients avoid them for accessibility reasons. however, this was asked for and time is of the essence, and needs must. I am not that familiar with these interactions as well, so I'm not completely understanding why dragged objects AND drop targets need Correct and Incorrect states. Do they? Which takes precedence? And what makes an item draggable - having these states?

I realised I just have to monitor the DropZone states and base my programming on that.

The video in question is merely showing how a partially OCD person like me needs to have an order on items, especially when it comes to troubleshooting. Hence the clip shows me simply trying to reorder the objects into numerical sequence but not being able to drag them, like other variables. The glitch is when it comes to trying to delete them - they won't disappear immediately as expected, and it's only when one clicks the +Object button that the deletion takes effect.

I'd love to see how you'd go about your solution. I have trouble visualising (sooooo tired) how dragging objects triggers layers.

 Anyway, thanks for looking. Here's an interesting screengrab I just received from my file when I tried to copy text from a word document into the Alternative Text field within the Focus Order panel.

And then this lovely beauty when I saved and exited.

I am almost too scared (and scarred) to open the file back up and see what's left.

Hope the file is OK, it should be, probably some formatting or special characters in word.

I have built very few drag and drops recently because of accessibility, and in the past built loads. I hated posting that I would have built differently, just found the it so confusing.

The Correct and incorrect states on drop objects should only be needed if you want show they are in correct place. This was the main reason why I would have built as freeform as the state change is automatic. It is the trigger that makes them draggable (unless I am mistaken)

The drop targets I don't believe need states at all.

I will see if I can unpick it and show what I was planning.

Oh! and I get the OCD, don't get me started on check boxes and radio buttons and the so many other things that wind me up.

I completely understand your pain. I totally agree.

I find it confusing and I built the bloody thing! :)