diff options
author | bjarni <bjarni@openttd.org> | 2006-10-05 12:59:28 +0000 |
---|---|---|
committer | bjarni <bjarni@openttd.org> | 2006-10-05 12:59:28 +0000 |
commit | b31bfb25ca15886e047ebb7cd241e21a1a1bdf2f (patch) | |
tree | 4a3d21fb89f88716ad9e908b35bbfc8df30e3ed2 /clear_map.h | |
parent | 1671d343c30ce3e8775b41c907aa7e3b3baea2fe (diff) | |
download | openttd-b31bfb25ca15886e047ebb7cd241e21a1a1bdf2f.tar.xz |
(svn r6651) -Coding feature: added the windowevent WE_INVALIDATE_DATA
This gives the ability to invalidate some window data and recalculate as needed instead of doing it for each WE_PAINT
This event is called right away when using InvalidateWindowData(), so it may be a good idea to set a bool or similar in the window
or similar and then act on that bool in WE_PAINT instead of doing a lot of stuff in WE_INVALIDATE_DATA as it might be called more than once before WE_PAINT is called
InvalidateWindowData() will not automatically repaint the window, so if you want to repaint it as well, you need to mark it dirty as well.
Made the depot windows use WE_INVALIDATE_DATA to set when to generate the engine and wagon lists instead of at each redraw
It makes no sense to regenerate the list when say using the scrollbar if we know that no vehicle have entered or left the list
NOTE: currently there is a piece of code to generate the list when it's not needed and compare it to the stored list and assert if they mismatch
This check is somewhat slow and kills the whole idea of WE_INVALIDATE_DATA, so it's a short lived one to verify that InvalidateWindowData() is used everywhere where it's needed
Diffstat (limited to 'clear_map.h')
0 files changed, 0 insertions, 0 deletions