Suggestion for @brad: It would be great if we could control whether global transpose is applied before/after filters. Here’s one way it could be done with minimal code change:
The Key Range filter could have an extra dropbox offering three options:
A. No global transpose (default)
B. Apply global transpose
C. Apply global transpose negated
This would allow users to apply the global transpose at arbitrary points in the filter chain, and even “undo” and “redo” the global transpose before/after any filter in the chain.
[Aside: I suggest making this addition to Key Range not Transpose filters because Key Range makes Transpose obsolete. In fact, if you wanted to consolidate some code, Transpose could probably be replaced with a Key Range filter that defaults to full key range.]