fixed 'chunky' position for nodes when scaled

Node positions were rounded to whole coordinates when the container/layer had a scale greater than 1. There was a bit-wise or (0 | ....), when using this with decimal numbers, the decimal part of the number is removed. (0 | 1.5 will result in 1). I don't know why this comparison was in there, probably because to prevent errors when an invalid number was supplied.

I discovered this issue when using a MoveTo action in combination with a scaled layer. This fix resolves the issue, though it may cause problems when a wrong position is given (or anchor point)