Search found 1150 matches

I think the way of calling cascadeChangesForTask makes it slow. Doing like below gives a better performance. g.getTaskStore().startBatchCascade(); g.getTaskStore().forEachTaskUnOrdered(function(task){ if(task.hasOutgoingDependencies() && !task.hasIncomingDependencies()) { g.getTaskStore().cascadeCha...
I think so, it depends on what kind of changes you want to cascade in your example.

I timed the zoom in and zoom out with console.time and timeEnd

zoom in: 197.939ms
zoom out: 202.094ms
zoom in: 193.362ms
zoom out: 190.681ms

looks pretty fast to me.
Thank you for the report. I can reproduce it now. I have created a ticket for this.
I tried it on Chrome and firefox. I was not able to reproduce this. What is the way you add the nodes?
Yes, look at the example I have given. For now you could try, Ext.define('MySchedulerGridView', { extend : 'Sch.view.SchedulerGridView', alias: 'widget.MySchedulerView', horizontalLayoutCls : 'MyHorizontalLayout', generateTplData: function (event, resourceRecord, resourceIndex) { renderData = this.c...
Normally you would sort on the store. In this case the eventStore. You can find more information about that over here:!/api/ Or else what is exactly what you want? For an override you could try.... Ext.define('MyHorizontalLayout', { extend : 'Sch.ev...
Why do you want to cascadeChanges for each task at once? It is a very expensive call and not common to use this function for each task in the store in one loop. For each found dependency it updates the parents of the task as well. for example if you do this, it will be much faster.... var tasks = g....
There is only support for one TimeAxis at the moment. So I think you could try to use the resources for the working days.
I will look into it....
Happy to report we have fixed the scrolling problem. Please try this out in the next nightly build.