discoverability of reflected methods?

FlowCanvas Forums Support discoverability of reflected methods?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #3348

    If I have a method on my Door monobehaviour called Shut(), I can find it in flowcanvas by either:

    – dragging a line off a Door-type pin, and going down through the menus Door > Methods > Shut

    – searching for Shut, and hooking up the instance pin manually

    However in most cases you don’t have a Door, you have a GameObject that contains a Door script and you use auto-conversion to get the component. If my level designer drags a line off that GameObject, they won’t get the Door function list.

    If the level designer forget what the function is called, and searches for Close(), they won’t find anything. If they search for Door by itself, they won’t find the reflected functions of Door. They’d have to dig down through Functions > Reflected > Door > Methods to see that it’s called Shut.

    It would be great if it was easier to see functions related to a type like this. Maybe there’s something I’m missing?

    One workaround is to make sure the function is called DoorShut, which means searching for Door would find it. However I don’t love the idea of every public function in every monobehaviour in the project being called Class.ClassThenFuncName(). The [Name] and [Description] attributes don’t seem to work on reflected public methods.

    Is there a better way to make such functions more discoverable?



    Another way to search in the browser is to enter “.” after the type name like so: “Door.” .

    Doing this will show all members (methods, properties, etc) of the Door type.

    Let me know if that helps.


    Join us on Discord:

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.