Proposition: Rename Overlap to Intersect

I think, from a general use of the word position, overlap is a much better word to use than intersect, which is less well known. Technically, yes, overlap means 'over' but I do think it makes perfect common sense as it is.

Having said that, I had no idea there'd ever been any confusion.

I think overlap is a name well-suited for what it does. If new users have trouble with it, the feature should be clarified in the help file if it already isn't.

'Intersecting' implies a point of intersection. 'Overlapping' is perfectly valid, just one of those things you learn with mmf2.

Eilyahu is correct. Intesection Point is a coordinate as which two non-parallel lines intesect. MMF objects are not lines and they do not have a single point at which they intersect, but many points (pixels) which for-lack-of-a-better-word 'overlap'.

Object A overlapping B returns true, as does B overlapping A. If you don't interpret it as placing priority on the first object over the second, they are actually 'overlapping' in an undefined order.

Alternately you could say they 'coincide', which is defined as 'Correspond in position; meet or intersect'. But that also introduces problems if you interpret it as occupying identical X and Y origins.

I always thought that the first object in the argument was actually given "selection" in MMF. So if you wanted to then apply some changes to one of the objects, you would be applying them to the first object. Something like:

+ObjectA is overlapping ObjectB
- Set Position of ObjectA to (0,0)

This would work. However:

+ObjectA is overlapping ObjectB
- Set Position of ObjectB to (0,0)

This would not work. But since I tend to use these sorts of statements within fastloops and with multiple instances of the same objects in the frame, I guess I could be wrong here. In a simpler setup, where only one copy of ObjectA and ObjectB exist, then you could apply changes to either.

I'm pretty sure I was proved wrong on just that, mobichan. testing now in build 251 it does select both objects. Even both instances of the same object, proof thanks to the select object's # of selected objects expression.

I agree that overlap is the better word. If you want to test display order there are plenty of easy ways.

Jacob, I do not believe that 'overlap' is synonymous with 'cover'. In the context of 2D game programming is is more synonymous to 'interlace', such as interlacing your fingers. 'intersect' immediately brings attention to lines and points, unfortunately. Perhaps the word 'with' could be added, eg instead of "A is overlapping B", it could be "A is overlapping with B".

Quote from Jacob

If you have two sheets of paper overlapping, you aren't going to state that the bottom one is overlapping the top.

Actually, I would.

Quote from Jacob

I suggest that if Overlap is kept, it be renamed to "A and B are overlapping."

Sure I think it's better than my suggestion.

It is not the case that I find it more convenient to call it "overlapping" rather than "intersecting" as much as it is not the case that I think you are, as you say, right. In my perspective, the term is already clear and uncomplicated. The only better word to describe the action would be to use its root, "is lapping" / "to lap", which is to entwine or overlay two things along the other; this comes from a Greek verb of using the tongue to make contact with and ingest liquids. I find this too much already an obscure nerdishness, and I'd rather have the Clickteam guys working on things that are more relevant and useful.

I can see the confusion, but for lack of a better word, I think overlap is fine.

Because 'intersect' really does imply lines in geometry. And 'coincide' could imply a lot of things, and would only complicate further.

Really, I can't think of a simple all-encompassing term. Because there really is no simple way of saying:

Quote

Part of "Object A's" surface area occupies the same 2D space as part of "Object B's" surface area.

There is no simple real-world equivalent of two objects occupying the same space because... two objects can't occupy the same space! No common word can really express this fully. The existence of this phenomenon is purely hypothetical in our virtual programming worlds. "Overlapping" is probably the best term to use, as all other alternatives imply more confusion than overlapping could.

Old, as in ancient like me, or veteran users? (LOL)

Marv