https://perchance.org/8swe0svvsk#edit

The same exact call in a code block vs a script tag behaves differently. The values seem to arrive to the plugin okay, but then get funky at some point–no idea why.

  • @wthit56OP
    link
    English
    13 months ago

    Yeah I did realise it’s an internal thing. But, if that’s the only way of me making it work without just copying that entire function someplace, then it’ll do. I actually like being able to see and use those internal things. Lets me sort out my own solutions to weird fiddly things like this. (Albeit with a lot of studying and stepping through to even figure out how to use it 😂)

    If you just make a set-in-stone function like you did for createPerchanceTree that would be find with me to be honest. Or yeah, a method on strings.

    I didn’t personally need a this for what I’m using it for, but if it’s just as easy to add that in as an optional parameter that would be good. Oh, and the root should just be any object, really. In my plugin I’m allowing people to use things like window, or an object, etc. So… please don’t throw if it’s not actually a root. Just let any object be used to “evaluate against.” Same goes for this I guess.

    I could see it could break a load of things, as you said. It’s likely only an issue because I was specifically doing deeper perchance stuff like building roots and evaluating strings myself. Probably most people won’t even find this discrepancy or notice it.