Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (103 - 105 of 18300)

Ticket Resolution Summary Owner Reporter
#18844 fixed Legacy build regression? dylan babynus
Description

I'm running large application using dojox.grid.datagrid in declarative mode for years (since 2009). All was working fine until 1.10.4. Since 1.10.5 and up to 1.11.1, my dataggrid is not rendered any more : store is correctly filled in, but no row is displayed in the grid, without any issue logged is the console. Was there any change in the datagrid and the way it is managed that could explain the behavior ?

Exemple of code :

<div dojoType="dojo.data.ItemFileReadStore" id="objectStore" jsId="objectStore" clearOnClose="true"
  url="../tool/jsonQuery.php?objectClass=Action" >
</div>
<table id="objectGrid" jsId="objectGrid" dojoType="dojox.grid.DataGrid"
  query="{ id: '*' }" store="objectStore"
  queryOptions="{ignoreCase:true}"
  rowPerPage="25"
  columnReordering="false"
  rowSelector="false"
  loadingMessage="loading..."
  fastScroll="false"
  onHeaderClick="unselectAllRows('objectGrid');selectGridRow();"
  onHeaderCellContextMenu="dijit.byId('listColumnSelector').toggleDropDown();"
  selectionMode="single" >
  <thead>
    <tr>
      <th field="id" formatter="numericFormatter" width="10%"># ${id}</th>
      <th field="name" width="60%">${name}</th>
      <th field="color" width="15%" formatter="colorFormatter">${color}</th>
      <th field="sortOrder" width="10%">${sortOrderShort}</th>  
      <th field="idle" width="5%" formatter="booleanFormatter">${idle}</th>
    </tr>
  </thead>
</table>

store objectStore contains correct values, but grid contains no row (the div with attchpoint="viewsNode" is empty. Any hind you help. Thanks in advance.

#18843 fixed requirejs compat with selector/_loader.js dylan dylan
Description

https://github.com/dojo/dojo/pull/211

#18842 fixed declare only merges "-chains-" in mixins (not superclasses) Michael Van Sickle <[email protected]…> Bryan Forbes
Description

The following code demonstrates the issue:

var A = declare([], {
        '-chains-': {
                initialize: 'after'
        },

        initialize: function () {
                console.log('initialize in A');
        },

        other: function () {
                console.log('other in A');
        },

        postscript: function () {
                this.inherited(arguments);
                this.initialize();
        }
});

var B = declare(A, {
        '-chains-': {
                other: 'after' 
        },

        initialize: function () {
                console.log('initialize in B');
        },

        other: function () {
                console.log('other in B');
        },

        postscript: function () {
                this.inherited(arguments);
                this.other();
        }
});

new A();
// logs out the following (expected):
// initialize in A

new B();
// logs out the following (unexpected):
// initialize in B
// other in A
// other in B

The following code in declare.js is only taking into account mixins and not the superclass:

                // collect chains and flags
                for(i = mixins - 1; i; --i){ // intentional assignment
                        t = bases[i]._meta;
                        if(t && t.chains){
                                chains = mix(chains || {}, t.chains);
                        }
                }
Note: See TracQuery for help on using queries.