Yes, that did occur to me, but I took a look through the technical level of your previous posts and judged that you'd figure it out without me being too explicit!
You're right about the bounce and momentum, up to a point. They are still axis changes, but it's hard to use a simple check for ranges being set the same, particularly as you don't have control over the timing of the momentum/bounce animations.
I guess the issue is that all charts can influence all others, rather than there being any master/slave hierarchy. There are a few things that may help you with this. One is that we expose the concept of a motion state on the axis, obtained with the following method:
This will allow you to discriminate between axis range changes due to gesture or momentum etc. You can also set a listener to handle changes in the motion state
The other idea would to have a central chart range manager class/object in your app, giving you the concept of a single set of 'desired' ranges for all charts, and testing against this before requesting range changes, rather than against the individual targets of the range changes. This object would be the listener for all axis range change and motion state change events. You may or may not consider this a cleaner separation of concerns, and it may or may not be more concise - it depends on the structure of your app, the lifecycle of your charts etc.