Hello,
I've found a severe bug between iemlib/init, iemgui/room_sim_3d and room_sim2d,
[init] seem to send a bang before [room_sim_3d] gets the canvas glist, so it says something like:
"invalid command name ".x20126a0.c coords .x20126a0.cBASE ...blablah" and in the worst case it crashes pd.
I'm about to update binambi patches, so removing dependences like [init] object is an option,
removing the bug in roomsim3d would be great, but I've no idea about what is triggering this.
I use Pd 0.47.0test4 and freshly compiled iemgui for linux from svn.
I've found out that this bug happens when drawing message are sent to room_sim when it's enclosed into a subpatch that have not been opened yet, a work around is about sending init messages after the subpatch where room_resides has been opened.
Le 04/09/2016 à 02:28, patrice colet a écrit :
Hello,
I've found a severe bug between iemlib/init, iemgui/room_sim_3d and room_sim2d,
[init] seem to send a bang before [room_sim_3d] gets the canvas glist, so it says something like:
"invalid command name ".x20126a0.c coords .x20126a0.cBASE ...blablah" and in the worst case it crashes pd.
I'm about to update binambi patches, so removing dependences like [init] object is an option,
removing the bug in roomsim3d would be great, but I've no idea about what is triggering this.
I use Pd 0.47.0test4 and freshly compiled iemgui for linux from svn.