Indeed that is a problem I only recently found out as well. The first part is already fixed (easy :)), but the second part (which definitely took me much time to pin point as well), it definitely looks like it is a Unity bug on UWP.
The reason I am telling it’s a Unity bug, is because on a completely new and empty project…:
1
2
3
4
5
6
7
8
9
10
11
//This will compile on UWP fine.
publicclassMyExample:MonoBehaviour{
publicvoidOnMouseEnter(){}
}
//This will NOT compile on UWP. Simply because it does not derive MonoBehaviour. :-)
publicclassMyExample{
publicvoidOnMouseEnter(){}
}
So unfortunately at least right now, the only way to work around this bug, is to actually comment out or delete these nodes/tasks that use such “OnMouse_X” methods, those being:
CheckMouse, ChechMouse2D, CheckMouseClick and CheckMouseClick2D (as well as MouseAgentEvents in FlowCanvas indeed).
I know by the way that another guy has already reported this to Unity. I will do so myself as well.
If the problem persists (not fixed) I will need to look at working around this in some other way, which I prefer not to, for not breaking existing projects of people who already use such events in custom tasks.
Thanks!!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.