ns
pushed para testing em ns/mantis
b36fe4d22b v 0.13.0 Beta
c37cd0df75 WIP string variables
string variables work in the simplest case already
all the trouble comes from the stuff that is in schemas or made at
runtime
so I have a lot of complex stuff to figure out
and even more important: to figure out how the user interacts
for example: should frame variables be inherited or not?
do I need a way to get this stuff recursively?
then how do i evaluate a string from a node in a different frame?
I would need to use THAT node to look up the variables, right?
NO SPOOKY stuff can be allowed
anyhow this is a WIP, might forget about this for a while and come back
some unsaved stuff I forgot to add. trash?
Fix Schema fail when Group linked to In/Outgoing
The problem was that I was attempting to get the next node
but it hadn't been generated yet because it was in a node group
There was never a problem with outgoing connection after all
it was only handling the held link from the outgoing connection
that was messed up, and only then if the next node was a group!
oddly, it did work in some situations with the old code
because the node groups were generated.
this code maybe could be cleaned up by forcing the node group
to generate as soon as it is encountered
but I think this solution, though less elegant, is better
since I can then deal with the connection to the node group
which is already handled well elsewhere. So this doesn't add
complexity or modify the schema solve as a system.
Fix syntax error
Get String Variables at Execution Time
Cleanup misguided changes in DummyNode
3b5e420b37 Add Custom Interface Socket Types
this commit (re)introduces custom node socket interface types
I did this a long time ago but didn't really understand it so I let Blender
do it automatically
But I am bringing it back because it lets me set some custom variables
for different socket types, such as default values or whether the socket
should be an array or not.
Interface Classes set the multi and default value now
note that this is VERY untested and probably doesn't work for Schema
update interface draw for correct UI and clarity
removes default value from xForm for outputs
removes array if interface item is a connection
and visa versa
fix: unbound local error when updating group interface
initial versioning for new interface classes
Implement Custom Interface Classes
this commit implements versioning and basic functionality for
- default values on group sockets
- arrays and connections editable in the Node Group Interface
- array support for regular Node Groups
tested and working with Human, Elephant, and Stego files.
Disable "Connected To" feature
this one is a little too ambitious and it will be too hard to implement
Fix: default value disabled for Matrix
(it is not yet implemented)
Fix: correct default value type for vectors
New Feature: Default Values for base tree
Fix: interface panel doesn't have an identifier
Fix: make default values work with more socket types
this commit also improves the error message
and it unfortunately(?) adds an assert from something I think is a safe assumption.
Initialize Tree with correct version number
WIP: Route Group I/O through interface nodes
This commit does not work! But it is a good start.
The purpose of this commit is to move towards bundling connections
at the base of each group in/out so that I can cache things, manage
variables, and most importantly for present purposes, send arrays
in and out in a more consistent way. Probably I revert this commit
and do something very similar without the intervening node until I
get that slightly simpler strategy working.
GroupInterfaceNodes at group in/out
This commit fixes and finishes the last commit.
All I forgot was to add the nodes to the parsed tree,
and deal with a little bit of hardcoded foolishness
that assumed there would be no intervening nodes
using socket traversal.
There will be more fixing for this behaviour in the near
future, no doubt. But this works, and it opens up
a whole lot of doors.
clean up useless prints
Fix: remove many instances of hardcoded node get
search ".link[0]" to find the rest of them and fix before release
for now, the matter of array sort id is much more pressing
Fix: Correctly Sort Links to Group Arrays
Look at the comment in readtree to understand this commit
Special note: this really needs more robust testing
but since I have tested stuff that I understand the only
test cases I am unsure about are those which are too hard
for me to imagine ahead of time. So probably I fix it if/when
someone actually encounters it.
cleanup xForm get_parent_node
Fix: lazy parents broken
Fix: Spline IK broken
965c6c48d6 v0.12.28 revert unhelpful broken patch
d0d622a238 Revert "Fix: Nested Choose fails when linked to group output"
This reverts commit 003e6b573a83e162d5655117101c641158fcadfa.
it was causing unforeseen problems in people's nodes and I need to
have a more robust solution:
há 1 semana atrás