Yes, you're right, I was interpreting the codebase incorrectly

I'm still not sure why the position handler activated, when the current limit is set, but it's not a biggie and I've found a workaround for the current handler not activating.

also, it seems that setCurrentLimit has no effect on the value returned by getCurrent()

I think there's a problem in the phidgets libraries. When I set the current limit with setCurrentLimit(), the position changed event is triggered, not the current changed event.