Search Type: Posts; User: bluehipy

Page 1 of 5 1 2 3 4

Search: Search took 0.04 seconds.

  1. My pleasure @mx_starter :) I 'm glad it worked for you ;)
  2. The window has the same id problem.
    But your issue is related to the way you are trying to extend the chart.
    Properties declared outside of a config are actually static properties. For the...
  3. First of all, a define should never have an id specified :) It is a class not an instance. With an id specified in there all of your instances have the same id.
  4. Chart, series and axis are different instances. Mybae the chart gets destroyed but series not.You should post the way you are coding this.
  5. Maybe you should use the window onbeforeunload event so you can handle things related to that before the Ajax call gets aborted and eventually adjust the way the AJAX handlers react in that case ;)
  6. Charts have some issues. Many :)

    The dynamic aspect is not really well handled.

    How so ever in your case is probably from how you initiate / destroy the chart. If series seams to get added you...
  7. checkView: function (view) {
    var me = this,
    handles= me.handles,
    ref, selector, control;

    for (ref in handles) {
    selector = handles[ref][0]; //a selector, like...
  8. Ext,decode will not transform that into actual methods references.
  9. Hmm... surprisingly you are right. I was adding all that uglyness because in some context applyers were not called.... how so ever I checked now again and things are happening actually....I have to...
  10. I figured out that the initCOnfig is not called.
    How so ever there is a problem in offering the correct config.

    At the construction time you have a this.config that is classify, as in it being a...
  11. Well... this is a BIG minus for Ext.
  12. A simple test case:
    Ext.define('ClassA',{
    xtype:'xa',
    config:{
    prop:{p:'A'}
    }
    });
  13. :)
  14. He he :D
    Thanks =NR=, you 're cool ;)

    peace
  15. In child components you could fire events that you can catch later on parent containers, this way you can keep them independent.

    *
    I had a great teacher, I am self taught :D
    Mainly I have read...
  16. You should not need the item index in component and ... you should not make a component dependent of its parents normally. It's some how against the intention of mvc. How so ever you can use up() to...
  17. This would be some approach:



    Ext.define('BlueButton', {
    extend:'Ext.Button',
    xtype:'xbluebutton',
    config:{
    dataItem:null
    },
  18. Show us the code, to see how you did it.
  19. applyItemTpl:function(newTpl, oldTpl){
    var tpl = Ext.XTemplate.from(newTpl);
    return this.callParent( [tpl, oldTpl] );
    }
  20. Replies
    4
    Views
    708
    don't specify a layout, specify fullscreen:true maybe
  21. You could do some dirty stuff like tipsy, and store the original text in some native or custom attribute, like title or original-title, and display the full text or the ellipsis one on your will.
  22. well, this is the problem:
    itemTpl : Ext.XTemplate.from('recent_activity_list_template')
    the dom is not there at the define time.

    you may try delay it with:

    config:{...
  23. Well, probably the best solution would be:



    items: [
    {
    title:'Some title',
    xtype: 'settingsList'
    }
    ]
  24. I don't get it if in the case of a simple application you get the same error or not.
  25. I don't see anything wrong.

    If you create a new test application things are the same with it on build?
    I would check that to see if it is a framework issue or a thing that your code brought in.
Results 1 to 25 of 120
Page 1 of 5 1 2 3 4