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

Problem with the calculated position after a move #2

Closed
VonD opened this issue May 13, 2011 · 2 comments
Closed

Problem with the calculated position after a move #2

VonD opened this issue May 13, 2011 · 2 comments

Comments

@VonD
Copy link

VonD commented May 13, 2011

Hello,

First, thanks a lot for this great plugin!
I'm having trouble with the calculated position returned when a node is moved :

  • if i move the node upwards, the position is 0-indexed
  • if i move the node downwards, the position is 1-indexed.

For example :
root
child 1
child 2
child 3

If i move child 2 before child 1, I get : data.rslt.cp = 0
If i move child 1 after child 2, i get : data.rslt.cp = 2 instead of 1

Do you have any idea where the problem can come from ?
Thanks a lot for your help.

@vakata
Copy link
Owner

vakata commented May 13, 2011

In the 1.0 branch this is fixed. I will see what I can do for pre1.0, but now my focus is on finishing 1.0. You can easily get the actual new index by doing data.rslt.obj.index().

Kindest regards,
Ivan

@vakata vakata closed this as completed May 13, 2011
@VonD
Copy link
Author

VonD commented May 13, 2011

ok, thank you very much.

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

No branches or pull requests

2 participants