Results of some APIs in API-2 don't match API-1

I think this has already been discussed here, but some APIs that used to work fine in API-1 now give different results in API-2.

For example,


now automatically moves the new layer to the top of the layer stack.



returns a string and not a number.

I’ve gone back to using batchPlay to access these features since some of my code relies on the API-1 behavior. Also, now a bit wary of using APIs as not sure of their long-term stability. batchPlay seems to perform the same in both API-1 and API-2.

So, we’re asking around about this. It seems like unexpected behavior… We’re investigating what’s going on there.

1 Like