No estimated time atm. I'm currently stuck in the Makefiles-- while I have a deb package building smoothly, OSX is really a pain. If you want to test on Ubuntu or Debian I can get something ready. There are a few regressions I'm working through with the gui toolkit atm, but in about a week or so most things should be working.
I haven't looked at building on Windows yet. But if someone wants to donate a windows laptop and a Faraday cage to store it in, I'll dive in. :) -Jonathan
On Sunday, January 3, 2016 2:00 PM, João Pais <jmmmpais@gmail.com> wrote:
#yiv8808675196 body {font-size:13px;}Is there an estimated release time of your edition, or do you need any help with testing etc?
Hi list,I'm playing with adding a simple animation api to data structure drawing commands. The parameters will be sent to the GUI, and the GUI will take care of the ramp, delay, etc. I'm thinking of just making it a simple "set it and forget it" api. That is, you send a message with your ramp and delay times to the GUI, and you just blindly trust that the GUI will make things happen in the right amount of time. The alternative I can think of is to have the GUI call back when an animation is finished, but that would encourage mixing the two clocks (i.e., GUI and Pd clock) in unpredictable ways. Does this simple approach seem like a reasonable design? The biggest problem would be that a long-running animation could skew. But in that case you could probably amortize the cost ofsending more messages over the longer time period.
-Jonathan