You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started clicking around the interface to see how it works.
One thing that initially struck me as odd and counterintuitive was the IN/OUT direction for the arrows. I don't know if this is just me, but my instinct was that the forward (right) arrow would denote IN (i.e. that ref is right [or correct] for MTB) and the backwards (left) arrow would be OUT (i.e. left behind). The interface is the opposite. Maybe that assumption was a result of my 1st language being English and therefore I read left to right? Conceptually, something virtually moved to the left would be left behind as I progress along while something virtually moved to the right would be kept in front of me.
Has anyone else who has tried out the interface found this to be the case?
As I said, maybe it's just me.
The text was updated successfully, but these errors were encountered:
From Debbie Krupke:
I've started clicking around the interface to see how it works.
One thing that initially struck me as odd and counterintuitive was the IN/OUT direction for the arrows. I don't know if this is just me, but my instinct was that the forward (right) arrow would denote IN (i.e. that ref is right [or correct] for MTB) and the backwards (left) arrow would be OUT (i.e. left behind). The interface is the opposite. Maybe that assumption was a result of my 1st language being English and therefore I read left to right? Conceptually, something virtually moved to the left would be left behind as I progress along while something virtually moved to the right would be kept in front of me.
Has anyone else who has tried out the interface found this to be the case?
As I said, maybe it's just me.
The text was updated successfully, but these errors were encountered: