Open sirpy opened 4 months ago
@sirpy this is fine, though we should be consistent (I see some have 2 or 3 after the decimal point). Thanks for finding a way for it to be visible.
Why is this assigned to me?
@decentralauren for a decision. keep it as 2 decimals or increase the decimals and to how many
@sirpy OK fine - yes per my above message it is fine. Should be 4 decimals (as you mocked up). Please make sure it is always 4 decimals to avoid confusion.
Is it possible to have the last 2 digits a lighter type font / weight (e.g. light instead of roman)?
its possible, not sure it would look good. just add your decision regarding colors/fonts to use
@decentralauren
@sirpy please implement 4 numbers after the decimal, and use
for the last 2 digits. I can't tell if what's implemented is medium / roman / bold, but if you tell me I can tell you the next lightest font down.
@L03TJ3 another one to pick up if wanted :)
@decentralauren This is how it looks with weight 400.
@sirpy this looks great. Is the color styling tied to the "USD" and other sub-text styling, so that if we update the color it will update both? We may want to make it slightly lighter.
no this is specific for the G$ streams
@sanajamm will reply with a slightly lighter hex code for the gray.
verified on feature branch
Problem: When showing donation amounts the amounts of G$/usd are with 2 decimals only. so the "animation" of the value changing isnt visible ie it is very slow to update. in the image below i've increased G$ decimals to 4, so the animation is visible and changes every second of course as a pool gets more and more streams the animation might eventually show.
Solution: please implement 4 numbers after the decimal, and use