AD
Administrator
Syncfusion Team
June 10, 2003 08:33 PM UTC
The problem is that the first click (generally)activates the embedded cell control, and then it is the cell control that gets the second click (as its first click). So, no one control gets boths clicks.
In 1.6, there is a new event exposed, CurrentCellControlDoubleClick, to handle this problem. In earlier versions, there was no good solution other than setting ActivateCurrentCellBehavior to none so the current cell control would not get activated and eat the second click.
