Pd devs: The other option would be to add a check to sys_onloadlist(classname) before calls to sys_load_lib(classname), however that's basically equivalent to sys_load_lib not printing the error after it's internal check with sys_onloadlist...
From: Liam Goodacre <liamg_uw@hotmail.com>Cc: Pd-List <pd-list@lists.iem.at>Subject: Re: [PD] 0.49-0test1 multiple lib loading? was PD 0.49-0test1 releasedMessage-ID: <VI1PR0102MB358410933E034BCD3F42FE31FC040@VI1PR0102MB3584.eurprd01.prod.exchangelabs.com> Content-Type: text/plain; charset="utf-8"I do have more than one copy of Zexy lying around, but I don't think that's what's going on here. I've cleared all my search paths, so the only thing that it recognizes should be the Externals Install Directory (Pd/externals). I create one object [declare -lib zexy] and zexy loads. I create another [declare -lib zexy] object and I get the error message. Of course it's no use having two [declare] objects in the same patch, but it's very common to have them multiply loaded within abstractions, which is what is triggering it for me.Wouldn't it be possible just to withhold this error message? I can't see why it would be useful in the first place.