dp

(1️⃣ ),

dip

(2️⃣) or both (0️⃣)?

I vote for

dip

as it has some mnemonics as "device-independent pixels"

@wasyl What made you pick

dp

? What do you think about using

dip

?

To be fair I just never used

dip

. Google search shows 481mm results for

dp

and just 80mm for

dip

. I’ll be honest I thought nobody uses

dip

really 😄 I now realized it might just be me and my friends, in which case having both makes perfect sense

From the other hand, google uses

sp

and

dp

in xml, so why should we use other naming? 🙂

Alright, so I'm not dropping

dp

, but it'll see an incompatible change as it'll now return

Int

(instead of

Float

), unless you use the upcoming overload that takes a

Float

. I think I'll leave

dip

here not deprecated for at the very least one release. Your input might influence whether I deprecate it and drop it later.

Nice! 🙂

@louiscad Hi, are we planning to change this

dp

and

dip

API? If you have any plans or vision for it, I really want to help here and submit the PR for the same. 🙂

Hi @Hitanshu Dhawan, it's planned, I just had a few changes in my life, plus seeing family, plus changing priorities at work, and ongoing publishing process changes for Splitties (CI speed-up among other things) that made me not publish a version in a while. Next release (dev versions are not considered as releases) will have it.

Cool, do let me know if I can help 🙂