Adds a timeout to the stop function as to avoid a stop and an instant request after that

[ianmurrays]

I had an "issue" where my app would instantly request something after the bar had completed, making it look like it just returned to zero instantly. Since that looked kind of weird I added a timeout to the setComplete method with a customizable threshold.

By default, the threshold is 0 meaning it behaves just like normal.

[chieffancypants]

This should already be accounted for:

angular-loading-bar/src/loading-bar.js

Lines 267 to 274 in 2bc4045

	// Attempt to aggregate any start/complete calls within 500ms:
	completeTimeout = $timeout(function() {
	$animate.leave(loadingBarContainer, function() {
	status = 0;
	started = false;
	});
	$animate.leave(spinner);
	}, 500);

What value did you use for your stopThreshold? Could you do me a favor and try using that same value in place of the current 500ms and see if that solves it? If so -- we can simply make that configurable to accomplish what you want without the extra timeout

[ianmurrays]

I actually used 100ms and it seemed to work better. Didn't notice that there was already a stop timer.

[chieffancypants]

So in other words, the timer already included isn't working as well as yours?

Looking through the current code, I did notice that the completeTimer isn't canceled as part of the _complete() method. Maybe that is the reason.

[chrisg2]

I have just created a pull request that cancels completeTimeout as part of the _complete() method - see #79.

[chieffancypants]

completed with #79