On 19 October 2016 at 13:52, Józef Kucia joseph.kucia@gmail.com wrote:
Yes, it's mainly for consistency with buffer_clear_dirty_areas(), but additionally:
- having two functions with very similar names is confusing
(wined3d_buffer_invalidate_range() and buffer_invalidate_bo_range()),
Somewhat. It would be good to make that less confusing somehow, but I don't think using different terminology makes it better. One is a more specific helper for the other, and I imagine ultimately wined3d_buffer_invalidate_range() would be the only caller of buffer_invalidate_bo_range(). I.e., similar to how e.g. surface_load_location() and surface_load_texture() are related.
- dirty areas are also used for flushing modified areas when BO is
being unmapped (see wined3d_buffer_unmap()).
Yes, but I don't think that conflicts with the current name?