-
Notifications
You must be signed in to change notification settings - Fork 97
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
client: Remember last candle duration #2284
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be working!
a905534
to
fbadbf8
Compare
I think this causes an issue with our 24-hour high/low values. See description from issue #2198, but we are expecting to have the 5-minute candles loaded. See also |
@buck54321, we've been using the fiveMinBin in Also, for the |
The most recent release, v0.5.9, does not include the
It wouldn't be accurate enough to calculate the 24-hour change/high/low from the 1-hour bin. This is why I was forcing loading of the 5-min bins first. |
@buck54321, I'm forcing a request of the fiveMinBin if we don't have cache in 1a82aaf, hope that resolves the potential issue with the 24high/low rates? |
On account of the redefined candles in 0.6, if no candle bin size was selected, I believe the default should now be 1hr instead of 5min. I think this change is needed now that 0.6 is faithfully producing candles from match data only, not just mid-book for epochs. For the 5 min candles to be useful, matches need to be far more frequent. |
@chappjc what do you think?
|
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
- use spot high/low rate if available. Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
1a82aaf
to
2f386fc
Compare
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
aa1a04b
to
d0c6a4e
Compare
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
9d29c9a
to
0428f1a
Compare
Signed-off-by: Philemon Ukane <ukanephilemon@gmail.com>
cfe5f7b
to
4cab25d
Compare
page.durBttnBox.appendChild(bttn) | ||
} | ||
|
||
// load candlesticks here since we are resetting page.durBttnBox above. | ||
this.loadCandles() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah, page.durBttnBox
needs to be populated in order for loadCandles
to apply the selected
class. Seems fine but have not re-tested.
Thanks for your guidance through this PR @buck54321. It seems to be working as expected now. Everything look alright to you? After this one, I'll put up a backport PR for all the milestone items in https://github.com/decred/dcrdex/milestone/30 |
// load candlesticks here since we are resetting page.durBttnBox above. | ||
this.loadCandles() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like loadMarket
should still be called in setMarket
, just moved to right after this.setCandleDurBttns()
. Not a big deal though.
This adds the ability to remember a user's last candle duration selection and fixes an issue where the candle selection is not known when navigating away from and back to the market's view. Closes #2198
UI changes(#2284 (comment)): fbadbf8 hopefully the colors stand out.