Fix cvRemap transparent border issue (Feature #582)

Added by Peter Collingbourne over 14 years ago. Updated over 14 years ago.

Status:Done Start date:
Priority:High Due date:
Assignee:- % Done:

0%
Category:core
Target version:-
Difficulty: Pull request:

Description

Due to an apparent oversight in the enum definition for border interpolation methods, the constant BORDER_TRANSPARENT is given the same value as BORDER_REFLECT_101. This masks a bug in the implementation of cvRemap, which can call borderInterpolate with a parameter of BORDER_TRANSPARENT and an out-of-bounds value of p when performing a bicubic or Lanczos remapping, leading to a runtime error. These patches fix both bugs.

0001-Fix-bounds-for-transparent-borders.patch - Fix bounds for transparent borders (1.5 kB) Peter Collingbourne, 2010-09-23 11:45 pm

0002-Assign-BORDER_TRANSPARENT-a-unique-constant.patch - Assign BORDER_TRANSPARENT a unique constant (1.3 kB) Peter Collingbourne, 2010-09-23 11:46 pm

Associated revisions

Revision e15a2ea9
Added by Vadim Pisarevsky over 14 years ago

fixed remap with transparent border (ticket #582)

Revision d0e340bc
Added by Andrey Kamaev about 12 years ago

Merge pull request #582 from bitwangyaoyao:2.4_fixBlend

History

#1
Updated by Vadim Pisarevsky over 14 years ago

thanks! the patch is applied in r3895

  • Status changed from Open to Done
  • (deleted custom field) set to fixed

Also available in: Atom PDF