I just checked and I confirm version 1.1.4.
This bug is now fixed in Ver. 1.1.5: Boundary indexing fix.
