Editing logic: how to keep track of bodies and why are map keys changing?

jacob_kingery

In an editing logic function, I want to be able to determine which, if any, of the bodies selected in the dialog are the same as in the previous definition and retain some of the information from the previous definition for those bodies.  The only way I was able to get this working involved a nested loop comparing evaluated queries between the current definition and the previous, which feels rather inefficient.

To avoid this nested looping, I would like to create a lookup map from each body to an index that can be used to get the information for that body, but my attempts haven't worked out.  I was able to use evaluated queries for each body as keys in the map, but something happens to them between when I create the lookup map and when I try to use it the next time the editing logic function is run.
When I create the map, it looks like this:

{ { queryType : TRANSIENT , transientId : Tr:JHP } : 0 }

But then when this map is in the previous definition, the keys are changed to be like this:

{ JHP : 0 }

Somehow the keys are changing from the transient query itself to the transientId (without the 'Tr:' prefix?).

So, I guess there are a couple questions here.
1.  Is this a reasonable way to approach the problem of keeping track of bodies, or is there a different way that would be better?
2.  Why are the keys in my map changing, and what can I do about it?

kevin_o_toole_1

1. The best way to find the matches between two queries is to just do a qIntersection(). This results in a query for the entities present in both queries, and allows you to keep regular, unevaluated queries in the new and old definitions.
   
   
2. It's possible there's some sanitization run on your map that results in the definition change you're seeing, but it's hard to say before looking at actual code.

kevin_o_toole_1

1. The best way to find the matches between two queries is to just do a qIntersection(). This results in a query for the entities present in both queries, and allows you to keep regular, unevaluated queries in the new and old definitions.
   
   
2. It's possible there's some sanitization run on your map that results in the definition change you're seeing, but it's hard to say before looking at actual code.

jacob_kingery

I can see how a qIntersection() could help a bit, but I don't think it could eliminate having to loop over things.  I was able to get the map working by using transientQueriesToStrings() to get just the ID strings (e.g. 'JHP') to use for the keys, but things ended up getting restructured to no longer use editing logic.