Current filter:
                                You should refresh the page.
                                  • Hello,

                                    I'm creating this ticket as per Roman's request here (see comments section).

                                    The new Quick Runtime Customization feature was designed with a default way to invoke it, which is to press and hold on any of LayoutControl's child element. Unfortunately, there seems to be no way to deactivate that gesture and let the developer choose how the customization panel gets displayed.

                                    Since the customization can be invoked programmatically, a developer could choose to show it upon pressing a dedicated button instead. Especially if its app is already using a similar press and hold gesture to other ends.

                                    You must allow a developper to disable your handling of press and hold without taking away the ability to use the customization panel.

                                1 Solution

                                Creation Date Importance Sort by

                                The press and hold gesture is implemented as a finite state machine (FSM) which has three states: hold, hold with indicator and the final state which invokes the CostomizationForm.Show method. You can tune state timings using the OptionsCustomizationForm.QuickModeInitDelay and OptionsCustomizationForm.QuickModeLoadTime options. Setting the QuickModeInitDelay option value to any big number will disable the standard gesture processing.

                                • David Lemieux 03.06.2015

                                  It's more of a hack than a real solution, but I guess it's better than nothing.
                                  I'll write an extension method so that the true purpose remains clear when reading code.

                                • Roman Kalachik (DevExpress) 03.06.2015

                                  David, I believe that this use case is quite rare, and that's why I am wary of creating a separate property for disabling that gesture. If we get more feedback indicating that people use the touch friendly customization form this way, we will add that property.