dot size is controlled if you call the DrawDow function that takes an actual TextDot as input. The TextDot class has a FontHeight property that you can set.
I would rather not expose a border thickness option if possible and just make it ‘look correct’ on user’s computers at least for now. I’ll try increasing the border thickness by a little bit to see if that looks better.
I understand you don’t want to expose broder thickness. That’s fine. Just thought since we can set the size you would want to also set the border thickness in relation to that (the smaller the dot, the thinner the border).
What do you think about the dot ‘modes’ in my post above?
The hardest part of that request is just the extra work involved in File I/O and properly exposed controls for setting this in the user interface. The actual drawing code would be trivial.
I understood Guido’s request to fundamentally be that there should be a number of visually distinctive shapes available so that they could be easily differentiated when there are a large number of them visible in a viewport. I’m sure the exact shapes aren’t important, but could be left to a graphic designer to be pleasing, attractive and mutually distinctive. I’m not sure the number should be limited to three, though it probably doesn’t need to be more than a dozen. If the idea takes off, it might be good if the implementation was easily extensible to include more.
Personally, I think the implementation should include functionality to hide/unhide all of a given style; also select a single style while hiding all others; possibly ghosting all the hidden styles instead of disappearing them - or maybe as an option in addition to completely hiding them.
Sure this sounds like an application in of itself, but if you’re going to include a feature why not make it one users will be surprised and delighted at instead of disappointed and wanting.
