It is perfectly valid to set Count to zero, in which case only a single candidate at the original position is generated. This can be very useful in conjunction with setting RemoveConflicts to True so that overlapping labels are removed without spending time trying to move the labels around. It will not find a placement that is as good as if more candidate positions were considered, but in most cases it gives a result that is good enough with a very low performance penalty.

It is perfectly valid to set count to zero, in which case only a single candidate at the original position is generated. This can be very useful in conjunction with setting removeConflicts to True so that overlapping labels are removed without spending time trying to move the labels around. It will not find a placement that is as good as if more candidate positions were considered, but in most cases it gives a result that is good enough with a very low performance penalty.

It is perfectly valid to set count to zero, in which case only a single candidate at the original position is generated. This can be very useful in conjunction with setting removeConflicts to True so that overlapping labels are removed without spending time trying to move the labels around. It will not find a placement that is as good as if more candidate positions were considered, but in most cases it gives a result that is good enough with a very low performance penalty.

It is perfectly valid to set count to zero, in which case only a single candidate at the original position is generated. This can be very useful in conjunction with setting removeConflicts to True so that overlapping labels are removed without spending time trying to move the labels around. It will not find a placement that is as good as if more candidate positions were considered, but in most cases it gives a result that is good enough with a very low performance penalty.