Version v2.2.1

What's new:

1. New methods IsCrossedTheObliqueLine() and IsCrossedTheObliqueLineWithShift()
   The purpose is to check if Blob crossed OBLIQUE line.
   Algorithm is simple: build segment between two last points of Blob's track and check if two segments intersect.

2. Exend Blobie interface: added methods IsCrossedTheObliqueLine() and IsCrossedTheObliqueLineWithShift()

Version v2.1.1

What's new:

1. Exend Blobie interface: added method GetTimestamps()

Version v2.1.0

What's new:

1. Exend Blobie interface: added methods GetID(), GetTrack()
2. Update constructors for Kalman/Simple blobs: both accepts BlobOptions struct now:

type BlobOptions struct {
	ClassID          int
	ClassName        string
	MaxPointsInTrack int
	Time             time.Time
	TimeDeltaSeconds float64
}

In case when this struct is nil, default parameters are applied

v2.0.10 - Mismatch argument order in KalmanFilter

argument missmach on KalmanFilter

v2.0.9 - Extend interface

Added new methods to Blob's interface:

1. IsCrossedTheLine(vertical, leftX, rightX int, direction bool) bool - Checks if blob crossed the HORIZONTAL line
2. IsCrossedTheLineWithShift(vertical, leftX, rightX int, direction bool, shift int) bool - Checks if blob crossed the HORIZONTAL line with shifting option

v2.0.8 - Eliminate interface errors

miss spell

v2.0.4 - Extend interface

Add new methods:

1. GetCurrentRect() image.Rectange - Returns current BBox of object
2. GetClassID() int - Returns class identifier
3. GetClassName() string - Returns class name
4. SetDraw(drawOptions *DrawOptions) - Sets options for drawing
5. DrawTrack(mat *gocv.Mat, optionalText string) - Draws blob's track

v2.0.3 - Downgrade GoCV

Downgrade GoCV's verstion from 0.26 to 0.23 (to match v1 blob package)

v2.0.2 - go.mod

play with go.mod

v2.0.0 - Bring interfaces

What's new:

1. Version v2.x.x is located in nested folder v2 according adviced major version strategy: https://blog.golang.org/v2-go-modules.
2. Switch from hardcoded blob struct to interface.
   Now it's easier to implement "Blobs" structures based on different heuristics
3. Initial implementation of KalmanBlobie using Linear Kalman Filter package.

Q: Why bring new major version?
A: Because if we would try to rebuild v1 it would break our other private legacy project which depends on gocv-blob