Search Issue Tracker
Duplicate
Votes
13
Found in [Package]
1.0.0
Issue ID
1191206
Regression
Yes
UnityEvent drawer does not handle generic event parameters correctly when the class is derived from another class
How to reproduce:
1. Open tester-attached project (case_1191206-UnityEventIssue-Updated)
2. Select the 'Base' GameObject
3. See that the Custom Event accepts the 'string' argument
4. Select the 'Inherited' GameObject
5. See the Custom Event
Expected result: Custom Event on 'Inherited' GameObject also accepts the 'string' argument
Actual result: Custom Event on 'Inherited' GameObject does not accept any arguments; no dynamic parameters can be chosen
Reproducible with: 2018.4.9f1, 2018.4.12f1, 2019.2.5f1, 2019.2.10f1, 2019.3.0a12, 2019.3.0b8, 2020.1.0a8
Not reproducible with: 2017.4.33f1, 2018.4.8f1, 2019.2.0a1, 2019.2.4f1, 2019.3.0a1, 2019.3.0a11
Reproducible with package versions: 1.0.0
Comments (3)
-
ComanderXXY
Jul 23, 2021 16:14
Inheriting the class might be a workaround.
public class IntEvent : UnityEvent<Int> { }
IntEvent is at least shown in the Inspector at least in Unity 2019.4.3f7.
-
andersemil
Jul 20, 2020 12:49
Same issue here (Function (BaseEventData) is not populating for a Event Trigger.)
Upgrading to 2018.4.24f1 fixed it.
-
BriskInteractive
Nov 04, 2019 00:16
I am also having this issue. Function (BaseEventData) is not populating for a Event Trigger.
It was working in unity 2018.4.8f1.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
This is a duplicate of issue #1196591