atom feed4 messages in at.iem.pd-dev[PD-dev] [ pure-data-Bugs-1655662 ] ....
FromSent OnAttachments
SourceForge.netApr 23, 2007 2:03 am 
SourceForge.netApr 23, 2007 2:17 am 
SourceForge.netApr 23, 2007 2:46 am 
SourceForge.netApr 23, 2007 4:42 am 
Subject:[PD-dev] [ pure-data-Bugs-1655662 ] .xa10120: no such object
From:SourceForge.net (nore@sourceforge.net)
Date:Apr 23, 2007 2:03:53 am
List:at.iem.pd-dev

Bugs item #1655662, was opened at 2007-02-09 01:54 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1655662&group_id=55736

Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: puredata Group: v0.40.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Matteo Sisti Sette (sistisette) Assigned to: Nobody/Anonymous (nobody) Summary: .xa10120: no such object

Initial Comment: Hi,

This seems to happen under "random" circumstances. It happened to me with every
kind of patches (simple and complex) and usually NOT in a sistematic manner
(that is, the same patch which once triggers the bug, after restarting PD never
does again...)

However, this patch that I attach does sistematically make this happen, at least
to me under Windows XP.

The following error message appears in the output window:

.xa10120: no such object

This particular patch uses "scripting", i.e. it creates and deletes an object in
a subpatch iteratively; however, I saw this same bug happen a lot of times with
patches which didn't make any use of scripting at all. I attach this just
because it is the only one I have that is sure to trigger the bug.

Sorry I can't "isolate" it further.

Matteo Sisti Sette

----------------------------------------------------------------------

Comment By: IOhannes m zm�lnig (zmoelnig)

Date: 2007-04-23 11:04

Message: Logged In: YES user_id=564396 Originator: NO

unfortunately i cannot reproduce this with your patch on linux with pd-0.39-2 (vanilla) and pd-0.40-1 (vanilla).