| Re: [AD] stretch_blit problems on WinXP SP2 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Saturday 21 August 2004 14:54, Chris wrote:
> It looks mostly okay to me. Although I'm not sure how costly
> VirtualProtect is. If it's fairly costly, you may want to add a check to
> make sure the memory pointer changed or the size grew:
>
> if(stretcher_info[best].data != _scratch_mem ||
> stretcher_info[best].size < _scratch_mem_size)
> VirtualProtect(...);
>
> However, it's possible a call to VirtualProtect is negligible and you'd
> waste more time checking than with the actual function call.
I've left the test out for the time being and committed a slighly modified
version of the patch I posted earlier (with old_protect changed to DWORD
instead of int as you suggested).
Evert