Well... I think discussions about how something ought be called or not are certainly among the ten most superflous human activities. So you have my permission to call that thing that I refer to as 'tick' anything else that you want
.
I'm pretty sure that if I loved history, I would've known a few examples where language barriers started wars.
We've just used the terminology from the broker API, therefore the name 'tick' for that thing, which is represented by the TICK struct in the software.
OK, so it is FXCM insanity or just illiterate API programmers, whatever... And it's not a first time. FXCM 'lot' is also not 100000 of base currency like the rest of the world, but something completely different.
But to call 1min bar a tick and 2min bar is suddenly not a tick? Weird! And how can a tick have 4 prices? And how can it last for 1 minute exactly, how that makes it a tick? Blah...
I agree it's stupid chasing the reasons for bad terminology, but it's still confusing and error prone to translate every occurence of work 'tick' to 'bar actually' in mind. Not to mention that some of your previous explanation how various price function operate on ticks didn't make any sense to me, only now I understand why.
