Hi Richard,
I'm glad that fixed it. I didn't feel that combining two different notations (various ER forms and the ORM dot) into one overlapped notation would be appropriate or help with the 'learning' nature of ER Learning Mode.
The description text for the Binary FactType Multiplicity Display option does indicates that the mandatory dot position is ignored when this is enabled. However, I do not have the corresponding comment on the Mandatory Dot Placement property. I'll add that for the next checkin, even though the options dialog layout (which I don't see a way to control) leaves very little space for description display so it is easy to miss.
I'm a little surprised to hear about users leaving this option on. As the option category name implies, I meant it as a transitional piece to make the diagrams more readable for ER-literates while they learned ORM. The original request came from Gordon Everest, but the implementation timing was totally selfish (I was taking one of Terry's masters level modeling classes and had to produce correct ER diagrams). Finding the right algorithm for spider-crawling the crowsfoot lines around rounded corners turned out to be mathematically entertaining (I expected the white board full of algrebraic equations to collapse down to something reasonable, but nothing cancelled) and resulted in most of the work.
-Matt
Current description for Binary FactType Multiplicity Display: The display mode for overlaying Entity Relationship multiplicity display on role connectors attached to binary fact types. The 'Mandatory Dot Placement' option is ignored if this is enabled.
Adjusted description for Mandatory Dot Placement: Specify an end of the role connector to place dots for simple mandatory constraints. This option is ignored if an Entity Relationship Learning Mode multiplicity display option is enabled for binary fact types.