Hello,
My equipment:
RB5009UPr+S+ router (7.24 stable)
CRS326-24G-2S+ switch (7.24 stable)
Router connected to the switch via an SFP+ RJ45 insert (ZoeRax SFP 10G), temperature 52*C, Cat. 7 cables.
In the Tx Stats tab on the CRS326, I have: Tx/Drop Packet/Bytes on all active LAN and SFP ports.
Is this correct?
yes, lot's of packets and zero drops. that's good
left column: Tx packet
right column: Dropped packet
notice the little / between Tx and Drop 
I've lot of TXDrop Queue0 Packets too. On lot of my devices (routers, cores sw, access sw, caps) and everything works fine.
Do you have errors on /interface/print stats ?
Queues will drop packets if sending part tries to persistently transmit more than queue passes ...
Again someone misled by the Winbox representation of TX and TX drop. These reports should be collected and hand over to Mikrotik. Even one report should be enough to question this Winbox UI decision.
From a software engineer standpoint, i really don't get it how people just cant understand simple ui, it literally says and i quote "tx/tx drop packets" and there's literal "[box] / [box]", logical thing is that label = representation.
In this case its quite literally what it says it is. I think its just people not being able to read.
A possible solution might be adding whitespaces between (tx" "/" " tx drop packet) as a format so its literally unmistakable but it looks worse than the original...
Anyhow i think this is such a non-problem. I've never used mikrotik before until i started like 4 months ago and never had an issue with gui...
Actually it says (from screenshot) "Tx/Drop Packet" .... and I can imagine that it's the overload of the first part of label (meaning both direction - e.g. transmit - and "count" or "total") which confuses users. It would be more clear if the first part was not overloaded, e.g. "Tx Total/Drop Packet" or something similar. And yes, white space around the "/" would probably help as well.
At the enad of the day it's not always "technical literacy" of users, it's also down to UI design (where IMO MT generally does not excel).
I could just be an ignorant andy and say the classic "its software for EnGinEeRs, NoT FoR uSeRs" but thats just not true, for me this is not an issue, but i definitely do see how it being a bit more "eye candy" not in terms of graphing and graphics in general but more in terms of a "better looking ui".
The current setup works, but it doesnt look the best, so your point stands and i agree to a point.
It literally does not say that. look close.
Look at the end of the first "section", it quite literally is the format of "Tx/Drop Packet"
This is actually the definition of beeing ignorant. Not accepting that others may have an issue because you don't experience the issue yourself.
i'm starting to think you're misinterpreting what i'm saying on purpose or trying to ragebait.
I don't know. You stated people are not able to read. But I think the labels are misleading. I fully support @CGGXANNX improvement suggestion.
I think the easy way out is changing the left label, because otherwise it would need a layout change.
It is cognitive hard to recognize the / in Tx/Drop to refer to the seperator line betweeen the 2 input fields. Most people read / as "or". This is the confusing part. Then there is also the meaning of "per", like 15€/kg. Means 15€ per kilogram.
It depends how you look at it. And when UI depends on how you look at it, then it's bad.
Tx Sent/Drop Packet would already significantly improve it IMHO. Way better than Tx/Drop Packet. Still not optimal, but would fix it for most people.
What are we even talking about Tx itself means transmitted. So youre saying that "transmitted sent/drop packet" is better than "transmitted/dropped" esentially youre arguing about terminology and formatting, its the same thing the coding world if you went and argued about the for functions having the starting brackets in the same line as for or having them a line under, some people find it cleaner one way and some the other and its just a matter of preference not if it works or not. It's absolutely fine as it is and its just needless nitpicking IMHO.
And no, i would hard argue against the argument that the "/" separator means something in the sense of 15€/kg, fifteen euros per kilogram, its the same as for example; you have to sign a document and they had a label to the left of the textbox saying the format of the input is "name / surname" and theres boxes separated by "/" separator.
Would that mean that the expected output of it "Your name per surname"?
It's basic formatting to save on space and not have menus that extend 3 screens downwards (because there would be butthurt people complaining on forums about how the menu is too long and they cant fit it on their laptops), that you have to read what it says and fill in the form, for me its not a problem, im not saying its not a problem for other people, i just find it dumb that we are nitpicking around such dumb stuff like this.
Can't make everyone happy. Use common sense.
Again it's about how you look at it. For me, when I see "Tx" (or "Rx") in a ICT context, it means "transmit" or "receive" ... meaning direction. Not "transmitted" meaning something done. But I'm not native English speaker, so it could be it's my lack of language skills. OTOH MT guys are (probably mostly) not native English speakers as well, hence occasional weird language used (in UI and docs).
At the end of the day, helping users be smarter is almost always a better solution than dumbing down products.
That's where useless crippled feature poor UI designs of most home targeted gear comes from,
To reuse and old (overused?) joke:
MikroTik IS user friendly! It's just a bit picky about who it's friends are! 
