CCMDB.accdb flickers or flashes: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (Ttenbergen moved page CCMDB.accdb flickers or flashes at times to CCMDB.accdb flickers or flashes without leaving a redirect)
mNo edit summary
Line 1: Line 1:
{{Bug}}
{{Bug}}
If this happens 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. I have a long-term goal to change how we do the cross checks, they have sort of grown as we have built the program and have not been re-factored in over 10 years.
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.


This is related to [[Problems related to event timing of data consistency checks]] and would be addressed by [[Cross Check Engine]].  
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]].  


== Related articles ==  
== Related articles ==  
{{Related Articles}}
{{Related Articles}}

Revision as of 14:34, 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.

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=CCMDB.accdb_flickers_or_flashes&oldid=157954"