-
Notifications
You must be signed in to change notification settings - Fork 228
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
Use mouse to jump to any node(position) in variation window #391
Use mouse to jump to any node(position) in variation window #391
Conversation
test again
Although we can navigate by keyboard, i have made it possible to use mouse
Olivier let's also include this in 0.6? |
@featurecat Sure, it just needs to be reviewed, it's next on my queue! |
tarNode = targetNode; | ||
prevNode = tarNode.previous(); | ||
while (prevNode != null) { | ||
for (k = 0; k < prevNode.numberOfChildren(); k++) |
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.
Since the value k
is not after this loop completes I would turn it into a local variable, like you did below with m
. Same comments apply for the loops below.
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.
k is working variable, it's c style.
|
||
} else { | ||
// in the different branchs, must move back first, then move forword | ||
for (int m = 0; m < j - k; m++) previousMove(); |
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.
It looks like you copy the two loops above, do you think there is a way to avoid that duplication?
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.
more details? I dont understand
@phiming Here is my review. I've given you push access to my fork so that you can continue working on this branch if it makes things more convenient. |
Thanks for your so careful review. |
Thanks again, after all, we are volunteers. I will try best to help finish it. But since china's national day is over, I am available only at night. Sorry for some delay sometimes |
I changed code just now. Adopt suggestions from above discussion. Long variable names, list instead of array, correct typo. I push it to my homepage https://github.com/phiming/lizzie:oliver |
@phiming Thanks for addressing my comments. I'm sorry if the review felt overwhelming, my intent here is simply to help making Lizzie a good piece of software. Trying to deeply understand and review other people changes to the code base is one was to get there. Just to make things clear: there are no strict rules, all of this is just my opinion. And I think this PR needs more work before being mergeable. Don't feel obliged to work on it because you started, do as you please. Something that people often don't talk about is that for experienced people it can often take less time to re-implement something them-self than to help a contributor to meet their quality standard thought a dept review. With that out of the way, I have two additional, higher level comments on your PR.
|
@OlivierBlanvillain As I said, I have started it. But now it has been beyond my original purpose, to do some hack and let variation tree node clickable like in sabaki, and make lizzie easier. Maybe it's also a little bit beyond my ability. I am not a java programmer. About two comments you mentioned, Couldn't agree more, |
@phiming Makes sense, I'll try to finish it when I get some more time. |
O, I am still looking forward to seeing this feature... |
@OlivierBlanvillain @phiming |
Reopens #374