onClientMarkerHit ignores element's interior

[Sergeanur]

I have a client-side marker, placed into a non-zero interior, but onClientMarkerHit would still trigger if element in interior 0 enters the marker. I assume onClientColShapeHit has the same issue, though it's more evident with markers since they ignore hit element's height on the client side.

[patrikjuvonen]

It's been like this forever. I don't see why it should be changed, also because it'll be backwards incompatible. Just keep doing the checks yourself.

[Sergeanur]

This is not the case on server side. Also I'm not sure anyone would ever expect for marker to work outside of intertior it's visible to and therefore requre a backwards compatibility for this.

[Citizen01]

This is not the case on server side.

Well it should ! Test it again. This is why on(Client)MarkerHit gives you the matching dimension in your handler function.

[Sergeanur]

This is why on(Client)MarkerHit gives you the matching dimension in your handler function.

Obviously that's for dimension only, not interior.

[Citizen01]

OH GOD ! Sorry for that I genuinely thought it was about dimension for some reasons. I read too fast sorry.

[patrikjuvonen]

Do you happen to know or have you tested how col shapes behave with different interiors?

I'm thinking if adding a new parameter would be a good solution as then we'd still have backwards compatibility. We'd have to make it server-side as well, though.

[Unde-R]

@patrikjuvonen you still want to work on this? or I can do it.
If so what are the plans, adding the third parameter to onClientMarkerHit/leave & onMarkerHit/Leave?

[patrikjuvonen]

@patrikjuvonen you still want to work on this? or I can do it.
If so what are the plans, adding the third parameter to onClientMarkerHit/leave & onMarkerHit/Leave?

@Unde-R Hey, I'm going to unassign this from myself. Feel free to work on it. I wouldn't personally mind e.g. 1.6 to fix this bug as such and break scripts that "exploit" the bug. For now though, a parameter must be added for backwards compatibility reasons.