loadbang() in js differs from loadbang in max

    Nov 19 2010 | 4:06 am
    When saving a m4l device as a preset, the loadbang() function in a js is triggered (useless, since the rest of the Max patch seems to be disabled when you initiate the save; nonetheless, it happens).
    When saving the same device as a preset, a Max [loadbang] object does nothing.
    Is this intended behaviour? I can suddenly see the cause of some mysterious buggy-ness in patches I've made. Has it always been like this?