I just installed 2.17.0 and I get the following error 3 times every time I open Purr Data:
"Your profile can not be used because it is from a newer version of NW.js. Some features may be unavailable. Please specify a different profile directory or use a newer version of NW.js"
I don't know if I have ever installed a specific version of NW.js, unless I installed it a while ago while looking into Node with Max - I think Node.js and NW.js are related, but honestly this branch of javascript is outside of my knowledge base so I apologize if I'm wrong!
Purr Data says I am running nw.js version 0.14.7.
I ran a quick test of Purr Data and didn't find any glaring issues - but I don't know what features the warning is talking about to test those specifically.
That fixed it. Thank you!
I just installed 2.17.0 and I get the following error 3 times every time I open Purr Data:
"Your profile can not be used because it is from a newer version of NW.js. Some features may be unavailable. Please specify a different profile directory or use a newer version of NW.js"
I don't know if I have ever installed a specific version of NW.js, unless I installed it a while ago while looking into Node with Max - I think Node.js and NW.js are related, but honestly this branch of javascript is outside of my knowledge base so I apologize if I'm wrong!
Purr Data says I am running nw.js version 0.14.7.
I ran a quick test of Purr Data and didn't find any glaring issues - but I don't know what features the warning is talking about to test those specifically.
So my 2 cents is that I use pd-l2ork as if it was Vanilla but with an editing environment that I find much easier and enjoyable to use. So I personally would like pd-l2ork to exhibit the behaviors of Vanilla when using Vanilla objects, so I can still code in pd-l2ork but if I need to use the patch for a lib-pd based application I won't run into problems (I haven't so far).
This [tgl] issue was more of a surprise behavior than a "I need it to work like Vanilla" scenario - I thought that [tgl] was limited to 0/1 only, and any nonzero numbers would convert to 1. I didn't know it would pass the nonzero number that is sent to it. Come to find out even in MAX this isn't the behavior of [toggle]! However in MAX the object behaves more like how the Vanilla object behaves - it can only store "1" as the nonzero, which makes me lean more towards adopting the Vanilla functionality.
As of Pd 0.46, sending a float to [toggle] doesn't change the non-zero value of the [toggle]. I went and confirmed this behavior in Pd 0.51-4. The [toggle] object in Purr Data 2.15.2 exhibits the behavior of Pd Vanilla 0.45 and earlier, where the nonzero value is changed by sending a float. I have attached a picture showing the behavior. Not sure if this is a conscious decision or not, I was under the impression that PurrData was aligned with the most recent Pd Vanilla version.