Support Forum

It explained here in the part when they say about dealing with a TreeStore:
https://docs.sencha.com/extjs/4.2.1/#!/a ... cfg-record

1. The print does not work that well. May be exporting to PDF and image is a better solution than this. Well printing depends on browser implementation. For me in my chromium v28.xxx it looks good. But of course you can try both print and export plugin to decide which one will work better for your ...

All the files provided with previous version should be overridden with new ones.
Or if you have special folder for our library you can just remove all its content and put there new files.

Wrap your destroy call with try-catch construction. That's all. No need to write anything in catch section.

task.parentNode will do the trick since task implements Ext.data.NodeInterface.
https://docs.sencha.com/extjs/4.2.1/#!/a ... parentNode

It's still not runnable. We need a runnable test case. Also there is a lot of code please get rid of non-relevant lines. Or as an option you could take some of our examples and try to reproduce your issue there. p.s. BTW from what I've seen in your screenshot I'd say that exception occurs in constru...

You can listen to 'update' event on a TaskStore.

I'll put my two cents in. First you specify plugins as plugins: new Gnt.plugin.Printable({ and then you completely overwrite them in initComponent : // Add some extra functionality plugins : [ Ext.create("MyApp.TaskContextMenu"), Ext.create("Sch.plugin.Pan"), Ext.create('Sch.plug...

It's browser related issue. FF and Chrome do translate dates differently. To make both of them consider the dates the same way you just need to be more specific in data definition. I mean you need to specify timezones for your dates like this for example (here I set timezones to GMT): <BaselineStart...

I need runnable test case so I could reproduce the issue. Only then I can assist.
This XML file doesn't give me much information. I attached it to our basic example and it works just fine.