Hello,
I have a manually created detailview that is opened by an action. The detailview contains a tabbed group with 4 tabs, that contain:
First tab: 2 Lookup-Controls
Second tab: 3 ListPropertyEditors (ListViews)
Third tab: 3 Lookup-Controls
Fourth tab: 1 Lookup-Control and 1 ListPropertyEditor
All controls are shown or hidden by appearance rules.
Now the problem:
The ListPropertyEditors have "AllowEdit" enabled. When I try to edit a field in a row, the editor needs 2 seconds for every character or for changing the state of a checkedit. All other operations in the detailview work normal, but deleting 10 rows with 3 fields out of the listviews takes 1 minute.
If I try the ListPropertyEditors (the ListView) stand alone outside the detailview, editing and deleting is totally normal. "ImmediatePostData" is not set for a control.
This looks like Q455387, but I have much less controls and the CPU takes 28% while editing in the detailview and 2% when editing standalone.
Have you an idea ? You know, I can't send you the project because it is too complex and 3tier.
Thank you
Michael
We have closed this ticket because another page addresses its subject:
ConditionalAppearance - How to avoid excessive Appearance and ImmediatePostData rule updates and improve overall form performanceRepositoryTextEdit very slow in ListPropertyEditor in DetailView
Answers approved by DevExpress Support
Hello Michael,
You can deactivate rules tracking by deactivating the AppearanceController. Please refer to a similar ticket: Appearance is refreshed with every keystroke.
See Also:
Performance - Delay ConditionalAppearance rules updates until the editor value is validated
After commenting out all 9 appearance rules the behavior is normal again.
How can I deactivate the rules after the detailview is completely drawn ? The elements don't need to be changed after the view is drawn.