Show Posts
|
Pages: [1] 2 3 4
|
2
|
General Category / EasyUI for jQuery / TreeGrid - Indication if the component finished its loading to the DOM
|
on: February 03, 2015, 03:03:51 AM
|
Hi,
I'm trying to determine if the treegrid was already drawn, it means that the html elements were already created and added to the DOM.
Our problem is that we need to calculate text overflow for each treeGrid's cell, and if the text width is bigger than the cell's width, we will set a tooltip for the specific overflowed cell, but, while the treeGrid is not drawn completly, the calculated scroll width of a div cell will be 0, since it's still wasn't rendered in the DOM.
Do you have any indication that I can rely on in order to solve this issue?
Thanks!
|
|
|
8
|
General Category / EasyUI for jQuery / Re: ComboTree - Panel problem when scrolling on the outside area
|
on: September 09, 2014, 06:18:58 AM
|
Hi, Thanks a lot for your fix, the fix is working, but unfortunately, we still have a problem. The fix works only when the 'comboTree' is already been created when the page is loaded (document ready). But when trying to create another new dynamic 'comboTree' component on demand, the creation logics is removing the 'mousewheel' binding for some reason, and the original problem repeats itself. Please see the following example (you can notice that the fix is working till you try to append new comboTree component): http://jsfiddle.net/xFy42/29/Is there a solution for this issue?
|
|
|
9
|
General Category / EasyUI for jQuery / ComboTree - Panel problem when scrolling on the outside area
|
on: September 07, 2014, 05:16:23 AM
|
Hi, In case the comboTree contained inside scrollable div, and its panel is opened - when we move the mouse cursor outside the comboTree's bounds, but inside the scrollable panel's area, and try to scroll with the mouse wheel, the comboTree panel will move in relation to the scrolling direction instead of being closed. You can see this problem in the following test: http://jsfiddle.net/xFy42/23/Here is the steps in order to reproduce the problem: 1. Open the comboTree panel. 2. Move the mouse cursor outside of the opened panel, but still inside the parent panel area (the blue area). 3. Start moving the mouse wheel in order to scroll the parent panel, and the comboTree's panel will move with it instead being closed. As you can see in the following screenshot: How can we fix this problem? Thanks.
|
|
|
12
|
General Category / EasyUI for jQuery / ComboTree - slow performance in creation
|
on: August 27, 2014, 01:13:07 AM
|
Hi, We're using comboTree component, inside a cardView window in our web application. When we creates a floating window which holds about 8 - 12 comboTree components, we noticed the view creation takes a lot of time (about 2300 ms) , and that the main reason is when creating all the contained comboTree components. We created a similar demo - http://jsfiddle.net/xFy42/21/Where you can see in console, that creating 10 comboTrees takes about 900-1000 ms in average. you can see also that we're creating the most light ComboTree fields (without any bound retrieved data or custom callbacks or any added logic at their generation). Is there a way to improve the performance when creating comboTree or to implement this scenario more efficient? Thanks in advance.
|
|
|
14
|
General Category / EasyUI for jQuery / Re: How to destroy treeGrid component
|
on: August 12, 2014, 02:10:14 AM
|
Hi, thanks a lot for your reply.
I've tried the above code, it indeed removed the treegrid's panel and inner divs from the DOM, but for some reason the tab process's memory usage still growing on every creation\removal view of treeGrid. We tried to create treeGrid and destroy it directly 10 times, and in each iteration the memory just got bigger as like the previous treeGrid's resources weren't destroyed nor released from the memory.
Is the above code (panel destroy) supposed to remove all the inner objects and resources of the treeGrid from memory? Is there some 'jsfiddle' example of destroying treeGrid where we can test and monitor the memory leaks problem and make sure the above code works properly?
Thanks in advance.
|
|
|
15
|
General Category / EasyUI for jQuery / How to destroy treeGrid component
|
on: August 06, 2014, 10:10:00 AM
|
Hi,
i'm using Tree-grid in chrome browser. In our page, we're using a dynamic panel which can switch between views of treeGrids.
We noticed that we have a serious problem of memory leaks - After we created many views of treeGrid (where each new view in our manager panel creates a new instance of the TreeGrid component) and then removing all the existing views, the memory usage of the chrome process is not released and gets higher even more when we create & remove another views afterward.
Our need is to dispose and destroy the TreeGrid component when removing or changing a TreeGrid view. How can we destroy all the treeGrid's related DOM components and all its inner objects (columns, rows, editors, headers etc..) and to avoid from memory leaks or undisopsed treeGrid's inner objects\components? Thanks in advance.
|
|
|
|