proposal: instead of using x/y/z for 3d coordinates, use h/v/d, horizontal, vertical, depth

[eniko@mastodon.gamedev.place]

@ratsnakegames so actually if you use h/v/d then that opens up x/y for texture coordinates, perfect!

[jordan@sometimes.social]

@mdreid @eniko thing is, I’m gonna remember this one

[oblomov@sociale.network]

@eniko «ok but which horizontal is which»

[oblomov@sociale.network]

@eniko jokes aside, it's not a bad proposal. It's the same reason why I use row/col instead of x/y or i/j as indices in matrices.

[maia@mastodon.art]

@eniko i mean depth is already used for size in the z dimension, like width and height are for x and y, so it should’ve been obvious already

[jessechounard@hachyderm.io]

@oblomov @eniko I avoid row/col because that's y/x (not x/y) and I have to stop and think about it every time.

[gilesgoat@toot.wales]

@eniko What about row mayor / column mayor matrices ? ( and row / column vectors V * A or A * V ? )

[staringatclouds@mstdn.social]

@eniko

h/b/d - height/breadth/depth ?

[oblomov@sociale.network]

@jessechounard @eniko see, your problem is that you're using y for the row, which is obviously wrong 8-D

[gkrnours@mastodon.gamedev.place]

@eniko what about h / u / d for horizontal, yurizontal and depth ?

[irina@critter.cafe]

@eniko h/v/d, obviously standing for height, vvidth, and distance-