Oct 29, 2008 at 12:19am
To demonstrate the bug:
However, if I rearrange the order of the commands, I get an unexpected error. If the “replace” method is called before the “presentation_rect” method is called, as in the following example:
then the following error shows up in the Max window:
Is there any reason why I shouldn’t be able to set the presentation_rect after a replace command has been issued, or is this a bug?
Nov 1, 2008 at 11:46am
This bug is really affecting the development of my patch right now… My patch needs to create a bpatcher and load a patch into it, and then at a much later time it needs to move the bpatchers around. This bug prevents me from moving the bpatchers around after a patch has been loaded into them.
Can anyone at c74 at least confirm this bug and let me know that it’s on your radar? … and that you’re hopefully working on it for the next incremental?
Nov 1, 2008 at 11:48am
Sorry, just realized I forgot to mention OS and Max version in the original post. I’m using:
Nov 3, 2008 at 12:53am
I’ve been informed by c74 that this bug is not going to be a simple easy fix, and therefore might take awhile. However, below is a workaround that worked perfectly for me:
var id = 103812; //could be any random number
Basically you’re telling the patcher to move the bpatcher object instead of telling the object to move itself.
Nov 12, 2008 at 9:56am
This looks more like a solution than a workaround to me…
You must be logged in to reply to this topic.