alistair macdonald

Just upgraded to 5.1 and now dropfile does not work when embedded in a bpatcher. Dropfile works fine in the raw patch as expected (drag a folder over dropfile & a "plus" appears, drop folder & my umenu is populated); in the bigger patch where it's embedded in a bpatcher (or if I make a new bpatcher with it in), I drag a folder over the zone & all I see is the "no entry" sign. This is rather urgent as I've just distributed a patch for a big schools project where users will be downloading Max Runtime for the first time.

dropfile-not-working-when-in-bpatcher-max-5-1

It works fine here with the same setup, and the patch bellow.

If you could post an example, that would help.

dropfiles in bpatchers only work when patch locked. whereas dropfiles in parent patch work locked AND unlocked? weird behavior i guess...

The opposite in fact! Only works when UNLOCKED. BUT I have discovered the problem - my dropfile object had Ignore Click checked. In MaxMSP versions pre 5.1 this wasn't an issue, but now it is. Is one a correct behaviour? Why would you want this? And why different behaviour locked & unlocked?

dropfile NOT WORKING when in bpatcher Max 5.1