-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Sync up with changes from voting branch #1601
Sync up with changes from voting branch #1601
Conversation
- Add onUiReadyHandler to BisqApp and MainView - Add startApplication and onApplicationStarted to BisqAppMain - Improve MenuItem component - Use TxBroadcaster.Callback() instead of FutureCallback<Transaction>() - Apply startup changes to MainViewModel - Apply changes of data storage
ACK - checked out all branches locally and did a test trade. Everything working so far for me. |
So the ACK applies to all sub projects? |
@@ -159,7 +153,8 @@ public void initialize() { | |||
bsqFormatter.formatCoinWithCode(receiverAmount))) | |||
.actionButtonText(Res.get("shared.yes")) | |||
.onAction(() -> { | |||
walletsManager.publishAndCommitBsqTx(txWithBtcFee, new FutureCallback<Transaction>() { | |||
// TODO not updated to TxBroadcaster changes because not in sync with voting branch anyway | |||
/* walletsManager.publishAndCommitBsqTx(txWithBtcFee, new FutureCallback<Transaction>() { |
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.
Should this be fixed now that voting branch is being merged?
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.
No I did not merge the dao code, just a few parts which was required due the refactoring. So the dao code in master is still the old one from a few months back...
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.
A main reason why not merge yet is bc of PB changes need to be tested well and if we have it in master it will be harder to change, so better for the WIP state to be more flexible with PB changes....
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.
Yeah, noticing parts are there but a lot isn't.
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.
Yes, only technical refactorings (class rename, move) in the dao project got applied.
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.
utACK
@ManfredKarrer I checked out all PR's and built the client. So my testing involved the other PR's as well. |
Same question here as in #1605 (comment). Was it unintentional to merge this as @bisq-github-admin-2? |
Yes because I did not had merge rights anymore with my dev account. I merged already the other projects so it would have caused problems to leave desktop with the old version. |
@ManfredKarrer and I sorted out the merge permissions issue. See #1605 (comment) for details. |
There have been several changes in the voting branch (and api-integration) which I want to get into master to avoid that those branches run out of sync as well as to apply the improvements.
The main changes are:
Beside that there are many smaller trivial improvements, fixes, refactoring and cleanups.
Changes in that project: