+ * Debugging random non-lod strokes when you expected them to be LoD. When you see a "slow" stroke, check the last debugging line (it appears once per stroke
+ *
+ * Possibilities:
+ *
+ * * If m_d->desiredLevelOfDetail is zero, then some GUI signal has reset the LoD with image->setDesiredLevelOfDetail. That usually happens during zoom
+ *
+ * * [MOST PROBABLE CAUSE] m_d->canUseLodN() --- then there is some slow non-lod stroke is still running and therefore the LoD is not available (this is by design, it can be fixed but needs work)
+ *
+ * * lodBuddyStrategy is null --- the stroke doesn't support lod
+ *
+ * * m_d->lodNNeedsSynchronization --- can only cause a delay before starting a LoD stroke