View Issue Details

IDProjectCategoryView StatusLast Update
00205751.4 IDE BugsImporting ProjectsPublic2017-03-02 14:30
ReporterjjanetkaAssigned ToFritz 
PriorityVery HighSeverityCritical BlockerReproducibility100%
Status ClosedResolutionFixed 
PlatformWindowsOS OS Version
Summary0020575: Importing Projects: Add Existing objects changes the Collision Event to be colliding with the wrong object
DescriptionIf you have some objects which are colliding in another project and you add them to an existing project then the collision events will not work as originally intended.

The first object imported will change its collision event to be colliding with itself as it is the only resource which it can collide with at that point and the second resource will correctly be colliding with the above object.
Steps To Reproduce1) Create a project
2) Create two objects
3) Add collision events to each object to collide with each other
4) Save the project
5) Create another project
6) Open the add existing dialogue
7) Add both objects
8) Open each object, see the collision events are no longer correct
Additional InformationOriginal helpdesk ticket:
1.4 Found In1.4.1749


Daniel Cleaton

2016-03-21 09:05

Adminstrator   ~0042484

This would depend on you importing the parent first - if you don't do this, then the child has nothing to set as its parent, so this wouldn't really be a bug. Previously, the child object would have stripped its parenting info, so then you wouldn't have received any error/message highlighting you to fix the issue.

Will have to confirm the steps still repro when it's the parent which is added first.


2016-03-21 17:25

Reporter   ~0042523

This issue doesn't involve parenting/child relationships.
This is about an object not including the collision event with an object that is lower down (and thus not imported yet) the object tree.

I would think that add existing should do a quick scan of object names to be imported so that when they appear in collision events they are not ignored.


2016-05-20 09:57

Updater   ~0043354

As an extra safety measure, the IDE could warn upon object import that it didn't find the parent referenced (if it doesn't exist) and that it'd be cleared though.


2016-10-27 16:29

Developer   ~0049945

Fixed in 7.7.1339