I agree the axis can be confusing. The main issue is that most the widgets use (x, y) for something that should actually be (col, row). The canvas uses Cartesian axis for the data though.

Is this something you would help clarify in the documentation ?

I am not sure if I am the correct person for this. I have absolutely no clue about this crate (never used it, just looked a bit through the docs), but I will keep this issue in mind and make a PR, when I have time for it.

Ok sure thing. Thanks for the report anyway. I've requalified the issue in the meantime.

Need terms and conditions

@stbor I think the best approach would be to have a different vocabulary for each coordinates system:

• We should use the row and column denomination for everything that deals with the grid system we are using to represent the terminal (i.e all widgets rendering code).
• We should use x, y when we are referring to a more traditional Cartesian coordinates system (i.e the abstraction Canvas is built on top of).
  While this task should be easy as it should only be basic substitutions, it is probably big given the amount of code to change.