-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3] Vertical order book width is sometimes to small #2734
Comments
It's not due to number of decimals after the decimal point, but the numbers before the decimal point. HB's order book is not as thin as GDEX. For this kind of extreme case, I guess it's necessary to show the horizon scrollbar. By the way, the |
Indeed, when an orderbook is so narrow it displays all the obscure orders at the end of it we have a few markets with up to 10000x the market price, making the table unable to hold all the digits. We need to look closer to the vertical order book view for this. The horizontal orderbook doesn't have this issue as it's limited to how many orders it displays initially. |
Let‘s check: |
Would introduction of scientific notation help in that case? Is that feasible towards traders minds? |
I will take a closer look at this again. The panel has a fixed width, as it would grow when required, but never shrink, making the orderbooks with less space requirements be extremely stretched. The size only changed once reloaded. |
I propose that when the price of a bid/ask goes away from the median to much, it's not going to be visible. This problem only persists mainly because the market has to few bids, and the edges are either 0.0000001 or 10000000. We should only allow +1 digit from the median price. If the median is 1.0 we allow up to 99.9 to be visible. If the median is 10, we allow up to 999 etc. Markets that has enough liquidity orders will not have this problem because the UI will never receive the edges of the order book. However, there is also a requirement for a better handling of dynamic width, with is problematic with current structure and needs more time. |
I think need to low the NUMBER OF DECIMAL POINTS and asjust the font.
https://www.huobi.co/en-us/exchange/btc_usdt/
The text was updated successfully, but these errors were encountered: