Dan Rose
Dan Rose
> skinned meshes are not supposed to be transformed, only the joint hierarchy :+1: ```ts s.listChildren().forEach((c) => {if (c.skin!==null){newRoot.addChild(c)}}); ``` Not sure how to handle `inverseBindMatrices`, though. > I think...
> In general I do not expose everything in the CLI, which is meant to offer a subset of the library's scripting features. That's fair. Would you want to expose...
Yes, there are workarounds. It’s probably better to not canonicalize away the default port because a “null port” in the URL spec does *not* semantically mean “no port” for special...
another option would be to forbid name tokens in the protocol and port. This would make parsing considerably simpler without losing much in the way of expressiveness.
Note the semantics are *slightly* confusing. The name "use_module" suggests that the argument should be a module name, but when the argument is an atom, it is actually interpreted as...
> > Yes, there are workarounds. It’s probably better to not canonicalize away the default port because a “null port” in the URL spec does _not_ semantically mean “no port”...
> I actually like the current behavior, but it may be because I've been used to it for years. The current behavior *ought* to exist. But it is confusing that...
The more I look at this, the more I think that the issue is that we *can't* base any logic on `protocol` before having a concrete URL and that the...
What I flagged as “confusing” is that `use_module` performs two closely related functions: - It loads the file into an executable form. - It imports identifiers to be visible in...