Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function signature is confused #11

Open
OneFirefly opened this issue Jan 3, 2020 · 1 comment
Open

Function signature is confused #11

OneFirefly opened this issue Jan 3, 2020 · 1 comment

Comments

@OneFirefly
Copy link

Deriving a class like
public class ColliderCallback : SerializableCallback<Collider, bool> {}
and exposing it the proper way: public ColliderCallback colliderCallback;
will make it fail to show a function like
bool CallThis<Collider>() { .. }
in the list of available functions in the inspector.

Instead it will show a function
bool CallThat<bool>() { .. }
(if declared).

The included package should be loaded in a new Unity project
SerializableCallback_bug_reproduction.zip

@Siccity
Copy link
Owner

Siccity commented Jan 6, 2020

I'm not sure that SC supports generic methods at all. It's designed to show only bool Method(Collider collider) as dynamic, and bool Method() as static.
Ill check for options but I can't make any promises.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants