[CLOSED] Debugging java script code - my classes are ending up in eval code

[RaphaelSaldanha]

I get the following result on Windows 8



IE version IE 11.0.9600.16438

[Dimitris]

Check this out:

http://www.sencha.com/forum/showthre...rately-anymore

[Daniil]

Thank you, @Mimisss. I were going to test with ExtJS 5.1.0, but somehow I forgot it. You reminded that to me.

Yes, it hits the breakpoint with ExtJS 5.1.0.

One more issue that is fixed in ExtJS 5.1.0.

Matt, once I commit my ExtJS 5.1.0 to SVN, I will post a follow-up here.

Apologize for the inconvenience.

[matt]

Thanks Guys for all the time you have put into resolving this problem !
I was very close from stepping away from Ext.Net 3.0. Now I can move on to the other challenges with the upgrade. I hope with normal debugging it will be pretty straight forward.

[Daniil]

Excellent! We are here to do our best helping you.

Matt, once I commit my ExtJS 5.1.0 to SVN, I will post a follow-up here.

It is going to happen later this week or very early next week.

[RaphaelSaldanha]

+1 to ExtJS 5.1.0.

[matt]

Superb, until then I will be using my small "hack" :)

[matt]

PLEASE IGNORE... not related to the thread... function complete was triggering onReady where I had error. (in previous release the error was not detected)

Hi,

I have upgraded to the latest version in trunk 6248 (Ext.Net 3.0.0.34915 with Ext JS 5.1.0.107).
My hardware and software configuration has not changed.

The debugging issue is fixed in this version. Although another issue was introduced. For some reason following error is called

Element cache already contains an entry for id 'ext-window'. Use Ext.get() to create or retrieve Element instances.

Ext.Boot:

        loadElement: function() {
            var me = this,
                complete = function(){
                    me.loaded = me.evaluated = me.done = true;
                    me.notifyRequests();
                };
            if(me.isCss()) {
                return me.loadCrossDomain();
            } else {
                me.createLoadElement(function(){
EXCEPTION THROWN BY -------> complete();
                });
                me.evaluateLoadElement();
            }
            return true;
        }

I will try to create sample where we can reproduce the problem.

Matt

[matt]

Hi,

I have located real problem of the error I was receiving (my previous reply)

Once we have 3.1 (extjs 5.1.0) released this thread can be closed.

Thank you

[Daniil]

Thank you for the confirmation that the debugging issue is fixed. Do you mind I close the thread right away since it is fixed in SVN?