CCMDB.accdb flickers or flashes: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
This is also related to [[Problems related to event timing of data consistency checks]]. | This is also related to [[Problems related to event timing of data consistency checks]]. | ||
* May happen when something is clicked upon or spontaneously. Will flicker any number of random times when it does happen. | |||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
Latest revision as of 13:58, 2022 November 29
If CCMDB.accdb flickers or flashes when you first open a record, or as you close it, then it’s because of all the cross checks we run. There are a bunch of screen re-freshes in the process, because some checks can run at different times and we need to make sure the screen is refreshed at least once. The cross checks have sort of grown as we have built the program and have not been re-factored in over 10 years.
The likely solution is to stop re-drawing the screen while the checks happen and to only do it once after all the checks are done. However, that would require a lot of change, as detailed in Cross Check Engine.
This is also related to Problems related to event timing of data consistency checks.
- May happen when something is clicked upon or spontaneously. Will flicker any number of random times when it does happen.
Related articles
| Related articles: |