You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 new boxes related to imports into the code. They idea behind them is that IMPORTED is treated as a black box and so would visually be very similar to a primitive. However IMPORTED_METHOD would have a more similar structure to an EXPRESSION, as it has a body field.
However there are currently a few bugs related to imports:
No matter the import, both are generated.
IMPORTED_METHOD's body is often blank
And IMPORTED_METHOD is the main one that get's wired into everything, often leaving IMPORTED an isolated blank box.
Tagging Tito here too incase there is future discussion. @titomeister
The text was updated successfully, but these errors were encountered:
an initial entry input box to view a certain FN at fn_array. (The initial value is 0, which means it starts with fn, just like before.) I hope this new feature can help with the problem of 1) some very large boxes are hard to navigate and expand, 2) some boxes are not connected to the main graph
There are 2 new boxes related to imports into the code. They idea behind them is that
IMPORTED
is treated as a black box and so would visually be very similar to a primitive. HoweverIMPORTED_METHOD
would have a more similar structure to anEXPRESSION
, as it has a body field.However there are currently a few bugs related to imports:
IMPORTED_METHOD
's body is often blankIMPORTED_METHOD
is the main one that get's wired into everything, often leavingIMPORTED
an isolated blank box.Tagging Tito here too incase there is future discussion. @titomeister
The text was updated successfully, but these errors were encountered: