1. To get a circle into a path/poly, first :CC2SPLIT: it, then use line to path on it.

2. I don't think there is a template with this grid, this was drawn specifically for that map. If you have the 2018 annual, there is a star charts issue which includes a similar grid in the template, if not this exact one.

Placing circles concentrically can be done a bunch of ways. Either with the center modifier (I don't understand why you find it unreliable, it always works for me for normal entities. I don't know if it correctly handles things like multipolies, and it can't handle symbols correctly which are complex entities made up from several others.), or by using snap and using a common center point, or by just typing in the coordinates for the center of each circle (and make them the same obviously), or even by placing another entity first and use for example endpoint. To make the sizes of the circles increase linearly, either use snaps, or type in the radius manually, increasing it by the desired number for each circle.

Lines can be easily drawn using radial coordinates. Draw them from the center first, then trim them to the inner circle. You can also use array copy to distribute them around a circle, or even Symbols along.

The numbers are just text with a rotation matching the angle of the line + 90, with a low center as text justifciation, and placed using the endpoint modifer.

It might not be a simple one-click solution, but with all the precision tools in CC3+, drawing grids like this is one of the things it excels at.

Turn off the demographics coloring: City -> Layers -> All BLDNGs with shading

If that doesn't work, try hiding all the layers that start with BLDNG

That's a known problem with Logitech mice. They use crappy switches. I actually use Logitech myself because of a range of other advantages, like the great power play charging system, no other manufacturer have anything else coming close. But I also end up replacing the thing regularly because of the crappy switches, experiencing the exact same things you describe, even in the more expensive models.

But most other makers have their issues too. The one I had before my logitech streak was a Razer, and it actually came with replacement switches, but of course, not for the switch that actually did wear out, my wheel button. And the one before that came with a battery that started to grow out of it's compartment. All good mice as far as operating them and functionality goes, they just don't last.

Yup, it's the rendering pass. Increase the pass size.

Templates have different advantages and disadvantages. Generally, all maps with particularily "fancy" elements have constrained dimensions because the new map wizard doesn't have the facilities to just scale the map area (technically, CC3+ doesn't have a separate understanding of the intended mapping area and outside elements like this, everything is just "the map"). So for these kinds of maps, free scaling is impossible. You can always edit the mapping area after creating the map though. Everything is still just regular entites, you can manipulate it as you wish, you just have to do some manual work, since it won't be 100% ready straight out of the new map wizard.

Note that the SS3 Pro template require proportional scaling. This is set up this way due to the legend at the right, it would look weird indeed if it was scaled arbitrarily. So the new drawing wizard enforces a 5:4 ratio on that template. So 17 by 11 is not a valid size for this particular template.

You'll notice how the width and height change in relation to each other if you just exit that particular input field instead of directly clicking the next button. Change one, and once you exit the field, you'll see the other update to the appropriate value for the constrained ratio.

Is that red polygon in the middle a separate polygon you can manipulate? Could it have been there from before you assembled the multipoly, perhaps as a copy of the blue entity?

Multipolies take on the properties of the current settings when created, not the properties of it's member, so that the multipoly itself became an outline could just be that fill style was set to hollow when you issued the command.

But, if that central red section is part of the multipoly itself, it is something I haven't quite seen before. If that is the case, can you post the .fcw file so we can take a look at it?

It seems to delete just fine for me without effecting the landmass, so just to clarify:

• When you click to select it, you do click somewhere on that stray part out in the sea right, and not where it overlaps with the landmass? (As that would cause them both to be selected)
• After clicking on it to delete it, but before hitting 'Do It', do the command line reads as 1 entity selected and not 2?

As an addendum, after deleting it, if you want that outline, you can easily add back a correct version by using the change like draw tool command.

But if you are going for a very complex coastline, you may wish to use a glow effect instead of a outline anyway.

Do her user have access to the location you installed the program to? (i.e. can she browse to that location using windows explorer, there should be a few png files in there, can she view those in an image viewer?)

Assuming she can, on the CC3+ command prompt, try typing menudm @fcw32.mnu and hit enter. This should load the default menu file, and CC3+ does remember this between sessions, so if this works, it shouldn't have to be done again.

The trace always goes through the point on the entity you used to select it. If it goeas around all the coast except for the section you want, it is an indication that you didn't select the entity to be traced using a place inside that area.