Drop States When Drop Target Is "None" Not Working?

Hi Wendy,

Let me just start by saying I am going to argue with you in the friendliest possible spirit. I realize that we're drifting out of the realm of technical how-to questions here and into the realm of philosophy, and therefore it is possible for us both to be right from the (different) premises from which we start.

That said, I think for me it comes down to a question of whether Drop Correct and Drop Incorrect cover the entire space of possibilities. In other words, if an item is dropped, does it have to be either dropped somewhere that's been marked as a correct match, or somewhere else which therefore would not be correct.

You (and Storyline) seem to be saying there are actually three possibilities: Drop Correct, Drop Incorrect, and some other state which is neither correct nor incorrect; let's call it Drop Neither.

I feel like that logic is sound as far as it goes, but then when I look at the built-in states for drag items, I don't see a Drop Neither state. When I set up the matches between drag items and drop targets, I only specify correct matches, leading me to the (apparently false) conclusion that Drop Incorrect is defined as any drop other than those I list as correct. If there are actually two other states, then just specifying the criteria for Drop Correct means we're not fully specifying the desired outcomes by specifying only the correct matches.

By this logic, just as

context drag item is incorrect if dropped on any target other than context

I expect

content drag item is incorrect if dropped on any target other than <none>.

In both cases we define the incorrect state by a failure to match the criteria for the correct state.

If you're still reading this, thanks for indulging me! :-)

Cheers!

   -Ray