The page freeze while dragging node

[Zoran Jeremic]

Hi,

I have the problem like in the title with my tree. This used to work
fine, but I don't know what happened with this tree. Now it the whole
page freeze when I try to drag node. There is no error indication in
firebug console except "undefineddojo._scopeArgs=[undefined];" message
in Script tab.
I don't know where to look for the source of this problem.

Do you have any suggestions?

Zoran

[Abhinav Katiyar]

Hi,

 

I saw this behavior in IE8.  I was calling a sync mode ajax call on move_node.  I changed the sync mode to false and I do not see it freezing now.

Page was not freezing in Firefox.  You can verify if you are doing something like this.

 

Thanks,

Abhinav

 

--
You received this message because you are subscribed to the Google Groups "jsTree" group.
To post to this group, send email to jst...@googlegroups.com.
To unsubscribe from this group, send email to jstree+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jstree?hl=en.

[vakata]

Can you provide a live demo so that I can help you debug? Also have
you upgraded any components or changed some scripts recently? Looks
like you have a dojo error ...

Kindest regards,
Ivan

[Zoran Jeremic]

Hi,

>I saw this behavior in IE8.

This is happening in Firefox.

>Can you provide a live demo so that I can help you debug?

I can't provide a hosting for this project, so I can't provide a live
demo.
I recorded a screen video if it can help, and I can also send you a
source code.
Video is available here http://www.screencast.com/t/NDUzYjBiYW

Here is a description of what is happening each time. When I start
application from the Eclipse, both trees are initialized, but node
can't move and everything is frozen. If I reload the page, the left
tree containing a structure of nodes is not there, but if I select
from drop-down list, that actually calls the same function for
initializing the tree, everything works fine.

>Also have you upgraded any components or changed some scripts recently? Looks like you have a dojo error ...

Yes, I made some changes in application. I tried to make a call to a
javascript function initializing a jstree from wicket page. I also
made some other changes not related to jstree. Now I have tried to
change this code like it was before, but it still doesn't work.

I've put just a peace of code (js files used for tree and wicket pages
containing this) at http://zoranjeremic.org/files/source code.zip

Zoran

[Zoran Jeremic]

I have tried this from my workplace computer (it is synchronized with
SVN, so it's the same code), and there is no freezing, but there is
still an error in firebug:

obj.o.each is not a function
(770 out of range 22)

This error happens while dragging the node and it happens exactly
before anything happens in
$("#basic_html2").bind("move_node.jstree",
function (event,data){

Zoran

On Jul 29, 11:31 pm, Zoran Jeremic <jeremy...@yahoo.com> wrote:
> Hi,
>

> >I saw this behavior in IE8.
>
> This is happening in Firefox.
>
> >Can you provide a live demo so that I can help you debug?
>
> I can't provide a hosting for this project, so I can't provide a live
> demo.
> I recorded a screen video if it can help, and I can also send you a
> source code.

> Video is available herehttp://www.screencast.com/t/NDUzYjBiYW

[vakata]

Hi,

Unfortunately I cannot use the source code as is (I cannot see the
data). Anyway - there is only one place obj.o.each is used:
the check_move function in the core. Could you please add those lines
before it (around line 810 or simply search for obj.o.each):
console.log(obj);
and tell me what you get in the console right before the error?

We will then maybe have to debug the prepare_move function which
actually sets `obj.o`, but please first tell me what the value of obj
and especially obj.o is from the above log call?

Cheers,
Ivan

On Jul 30, 12:31 am, Zoran Jeremic <jeremy...@yahoo.com> wrote:
> Hi,
>

> >I saw this behavior in IE8.
>
> This is happening in Firefox.
>
> >Can you provide a live demo so that I can help you debug?
>
> I can't provide a hosting for this project, so I can't provide a live
> demo.
> I recorded a screen video if it can help, and I can also send you a
> source code.

> Video is available herehttp://www.screencast.com/t/NDUzYjBiYW

[Zoran Jeremic]

Hi Ivan,

I did this. There is an 9 instances of Object { ot=Object, more...}
for 8 nodes I have in a tree. I didn't know what specific data you are
interested there so I recorded a video again if you can see something
strange there. I don't know if there is some other way I can sent you
these results.

http://www.screencast.com/t/NGM5ZDc2YzU

I can also send you the whole maven project if you think that is
easier to debug.

Zoran

[vakata]

Thank you, sorry I am torturing you like this :(
Can you please open the console log right BEFORE the error and open
object and exepcially the .o property so that I can see what it
contains? You can also paste it here, if it is too much work with the
video.

As for the project - I am not a java developer and I doubt I will
successfully install the work environment and project. Still - if the
above e does not help - I will :)

Kindest regards,
Ivan

[Zoran Jeremic]

Hi Ivan,

Thank you so much for your help.

> Thank you, sorry I am torturing you like this :(

Don't worry. If you don't torture me, I could spent a days trying to
solve this :)

> object and exepcially the .o property

Yes, that seems to be a problem. Each time error happens after the
first Object, and its .o property contains only False value. There are
no children like other .o properties have in other objects.
I hope this indicates something for you.

Zoran

[vakata]

Hi,

Could you please try the latest commit (rev.206).
I am really not sure that this fix will work, but test and let me
know :)

Kindest regards,
Ivan

[Zoran Jeremic]

Hi Ivan,

It seems that this work :)
I didn't test it in details, but I'm sure it will be fine.

Thank you for your help,
Zoran

[Саша Косьянчук]

i have had same problem. The reason was, that during AJAX answer because of laziness i didn't check node children existance, and put  'children' => true for all nodes. After i rewrite to be honest,  'children' => true, only when realy true, freezing gone.