Search:

There are 2 sources of truth - you're contradicting the JS engine:


onButtonTap: function(button){
var form = button.up('formpanel');

form.mask();

form.getRecord().save(function(){
...

Why not let the engine make the determination of when it's no longer in use since it's the thing that really destroys it? Why not say: the point of destruction is to indicate to the GC that the...

This issue really does make ExtJS/Touch apps very fragile. A missing 2 line check in the framework is certainly a bug when it means 10,000 devs now need to walk on egg shells when using unmask - lest...

Hey I don't deny the challenge, but the alternative is that every async call also needs to include a check for whether the component is destroyed or not. This leads to devs writing functions that...

The modern framework is written in a way that is unsafe for asynchronous code that manipulates the dom. This is a big source of bugs when apps are used in practice.

Many of the underlying methods...

Ok, was looking at Touch's History implementation, ExtJS 6's simpler / better implementation is unaffected.

So for packaged, Sencha Touch apps:

https://fiddle.sencha.com/#fiddle/v08...

In other words, I spoke too early, sorry about that. It only affects devs who have to use window.location.hash in their route handlers. If you still consider this a bug and need a test case let me...

So this may be a bug or it may be an enhancement, depending on your view. If you think it's a bug I'll put together a test case.

Before iOS9:
Dev's callback fn for a route has access to...

I reposted it in the ExtJS 6 forum and Don added it to the bug tracker. Too far reaching to be ignored.

iOS9 now asynchronously updates window.location.href, which causes any ExtJS or Touch apps with history support to break.


Here's a link to the issue:
https://openradar.appspot.com/22186109

...

iOS9 now asynchronously updates window.location.href, which causes any Touch or Ext JS apps with history support to break.

Here's a link to the issue:
https://openradar.appspot.com/22186109

It...

Here's a fix for Sencha Touch on latest Chrome.

I had looked into one of the other fixes posted, but it seems to be checking the wrong variable (safari version), which will cause it to break in a...

I reported this almost a year ago. Someone may have reported it earlier - who knows. Little hope of getting a fix apparently. As noted, this affects all data shown in all views, since they make use...

The cache I'm referring to is Ext.data.Model.cache. If you type that in the console, you'll see that Touch maintains a reference to every record you create - independent of stores. It uses this when...

You can refresh a form with:


formInstance.setRecord(modelInstance);

Not sure what you're talking about.

Rather than have to reset Ext.Msg (a singleton) throughout your code, I would create a new instance when you need it to scroll:


Ext.create('Ext.MessageBox', { height: 200, scrollable: true...

Something like:



Ext.define('MyApp.view.MyTabPanel', {
extend: 'Ext.tab.Panel',

initialize: function(){
this.callParent(arguments);

Are you trying to refresh the "form" or the "stores"? You're saying both in this question. If you want to refresh a store:


Ext.getStore('UnqualifiedNameOfYourStore').load();

Another option is to simply do:


Ext.create('Fiddle.model.User', jsonFromServer);


The advantage is you can update any record within your app without needing to maintain a reference to it....

JavaScript is very flexible, and that naturally extends to Sencha Touch, but there are conventions that have developed over time. I'd suggest you read through some of the guides to get a sense of...

Yes, that'd be the case if you're scrolled to the top or bottom. You could add to the previous post...

(1) animate the scroll of the container in your handler:



var scroller =...

(1) Overflow: visible the container, and convert your titlebar and toolbar to gpu textures, with animated classes:


.mycontainer > .x-scroll-view{
overflow: visible;
}

.mytitlebar,...

You can add it in the list config:



Ext.define('MyList', {
extend: 'Ext.List',

config: {
itemCls: 'LPNListItem'
}

Can you post the callstack? That will help debug...