Nine years ago a performance improvment was made to EmbeddableUIElementBase.IsHotTracking to check if the mouse cursor was over the element before checking to see if hot tracking was enabled. At that time the cursor check was simply a boolean field, so it made sense to do this. A little while later that boolean field was replaced with a property that evaluates the cursor position on each call, but the IsHotTracking evaluation order was not reverted.
The call to Cursor.Position (used by the IsMouseOverElement property) is a native call that incurs a noteable cost when initializing the appearance. Resolving the value of IsHotTrackingEnabled is enormously faster when extending EditorWithText and EditorWithTextUIElement myself and rearranging the order of the hot tracking evaluation.
Please consider revisiting the performance of IsHotTracking.
This has been addressed as of 12.2 build 2006.
Hello rastedt,
I created the following case for you: 'CAS-97922-5TYV4B' and will update you through it.
Thanks Mike!
I know it would probably be more appropriate to submit something like this through the feature request channel but I've never heard back on anything I've submitted that way, and always get stellar response on the forums.
I forwarded this post over to Infragistics Developer Support and asked them to write it up for developer review.