Lovely. You're really good at putting these things together.

Attaching doesn't automatically make corners for you. The only thing that modifer does is to ensure the nodes are in the exact same place, so for your road, it would ensure the start node of the new road is at the exact same point as the end node of the existing one. But line endings are perpendicular to the the direction of the line, so unless the direction of the two road pieces are 100% the same, there will be gaps, which is what you see both with your original example with the effects, and the later one in the last post.

As for symbols, you cannot really attach these to each other. A symbol only have one node, the symbol origin (or placement point). You can attach them to a line or snap them to a grid, but using attach to make them line up won't work.

Look for EType in CStuff in the entity record first. That tells you what kind of entity this is. You'll find the ID's in _ESTRUC.H.

My issue from the very brief look I gave that one was that I didn't seem to actually get valid entities at all, just uninitialized memory. Which may be due to a mistake on my side, or perhaps something that needs to be done that I don't know about, there is no documentation about that call.

The important thing to remember about dealing with a path is that it is a primitive, it isn't a container for other entities like a sheet, symbol or multipoly is. As such, you cannot access the line segments in the path, because it doesn't contain any, it just contains nodes. So there isn't a way to get a reference to these before exploding. You can figure out what the lines will be by looking at the nodes in the path, but there aren't lines to get references to. (Also, changes in the drawing list can cause things to shift around in memory, so holding a pointer to an entity in the drawing list that was acquired prior to a modification may very well not be valid anymore.)

I haven't tried exploding from code myself, but I guess that would be the EExplode function. That function does have a parameter of type EXPPROC which looks like a callback function, maybe that could be of some use in determining the new lines, but I haven't really figured out how to use it properly.

Not sure exactly how the algorithm is working internally, but it seems to like keeping the start/end node of the polygon (which would be located where you started drawing the poly in the first place.)

A few ways to deal with this:

• Try taking out smaller chunks, doing it over several operations.
• Draw a completely new polygon instead, using the trace feature of the tool to trace the part of the coastline you want to keep, instead of using the edit feature.

Yup, Gifts of the Old Ones.

If you are running a recent (less than 10 years old) 64-bit version of Windows, you don't need to do anything.

You can't set it at generation, but you can set them via the global operations afterwards. (Tools -> Global Set)

True. You don't need much snow before any resemblance of the roof structure is completely gone.

Note that unless you actually edit the actual bitmaps to make your own variation of the originals, you shouldn't copy the official files to other folders. That's just going to put in into trouble the next time you are viewing the map on a new computer since you will also need to recreate your copied folders exactly as before as well, instead of just relying on the installer putting things right (and it will also prevent others opening the map properly if you ever give someone the map file.)