The drop-zone parameter for general controls is not respected by mouse-dropping: atoms can still be dropped at every control and invoke MouseDrop() irregardless of its dropped-zone setting.
The parameter works correctly for MouseDrag().
Code Snippet (if applicable) to Reproduce Problem:
obj/MouseDrop(over_object,src_location,over_location,src_control,over_control,params)
var/d = winget(usr,over_control,"drop-zone")
usr << "Dropped [src] from [src_control] to [over_control] (drop zone: [d])."
Expected Results:
Nothing happens at all when you drop an atom at a control that has drop-zone not set to "true".
Actual Results:
MouseDrop() is executed and you get funny debug output from the snippet like so:
Dragged the obj from default.map1 to default.grid1 (drop zone: false).
Dropped the obj from default.map1 to default.button1 (drop zone: false).
Does the problem occur:
Every time? Or how often? Every time.
On other computers? I'm quite certain.
Did the problem NOT occur in any earlier versions?
Unknown, but probably not seeing as the developer seems to just have forgotten about MouseDrop() when implementing this parameter.
Workarounds:
Obviously there is one, but need I bother with it? ;P
It doesn't appear to be something difficult to fix, and there have been a couple of bugfix releases recently.