Skip to content
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

Resizing not handled correctly #12

Open
clarkminor opened this issue Apr 10, 2013 · 2 comments
Open

Resizing not handled correctly #12

clarkminor opened this issue Apr 10, 2013 · 2 comments

Comments

@clarkminor
Copy link

When resizing the window, the gaps between the order book, the y-axis price labels, and the chart itself don't dynamically adjust. This is problematic on both very large and very small screens, since it either case it does not utilized the screen space efficiently.

Here's what it looks like under a vertical split on 1680x1050 monitor:

7Np0and

And here it is fullscreen at 2560x1440:

GTSHdnT

I think it would be nice to have adjustable layouts that could be written to a config file, but I have no idea how much work that takes in ncurses.

@BleuSquid
Copy link

As an addition to this, I would love to have configurable candlestick-width, or configurable history-length, such that it auto-resizes the one, to fit the constraints of the other: If I choose 2-hour history, i'll get shorter-duration candles. If I choose 20-minute candles (instead of the default 15), keep a longer history for them.

If I want 5-minute candles or shorter, the current behaviour seems to work fine, on even widescreens with small fonts, as excess history is just not displayed.

@prof7bit
Copy link
Owner

candlestick width is now configurable. Unfortunately I still have only 24 hour trade history, its a huge download, there is no api for downloading consolidated ohlc data from mtgox, I need to download all trades. I am aware of this problem and already have some ideas (caching it locally so I never have to download the same old trades ever again). I leave this issue report open and tag it as "enhancement" request until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants