|Anonymous | Login | Signup for a new account||2014-04-23 08:50 BST|
|Main | My View | View Issues | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002656||GameMaker: Studio||[All Projects] General||public||2012-04-16 18:02||2013-03-05 14:55|
|Assigned To||Mike Dailly|
|Priority||Low||Severity||C - General||Reproducibility||<25%|
|Status||closed||Resolution||no change required|
|Summary||0002656: Still some issues with collisions and event|
|Description||keywords: [GameMaker: HTML5] Objects|
The following issue has been SUBMITTED.
Reported By: borise
Project: GameMaker: HTML5
Issue ID: 3042
Verify: Please check the FAQ first!
Scenario one: a "grandparent" object has an event handler. A "Parent"
object inherits from it and a final object inherits from the parent.
Calling "event_inherited" from the object will only call an event in the
parent it won't pass control deeper.
Scenario two: a parent object type defines a collision with another parent
object. The derived "child" object defines a collision with another child
object. In this case control is not passing to the parent's event, worse
still the child event is called twice.
Scenario one has a workaround: add extra stub events in the intermediate
object to ensure the event is inherited across "generations".
Scenario two is going to be very difficult to work around, if the child
event was called only once then inheritance could be forced using one of
the event functions, but the child event also gets called twice.
Date Modified Username Field Change
2011-10-29 08:02 borise New Issue
2011-10-29 08:02 borise File Added: collision_inheritance_2.gmz
|Copyright © 2000 - 2012 MantisBT Group|