[fuchs4dMember]

Solved,

works now, probably was Browser cache related, only logical explanation I have.
Sorrry was this.
File reference was correct.
Fresh Win 8 installation with fresh Firefox, forgot to disable the cache.
Just launched everything this morning and sorting works, did not change anything from night before.
Should make breaks before posting.

Thanks again.

[fuchs4dMember]

Dimitar,

thank you, is helpful for the use of the cellrenderer with a div.
Example of div contens I get from the web, so I will have everything needed to realize.

Alexander

[fuchs4dMember]

I want an arrow to be shown in each cell as a visual hint that cell can be edited with a menu.
The popup-arrow evolved to be a standard in desktop applications, at least I have always have an arrow in lists in desktop apps.

OK, this is not a feature of the grid.
However, it certainly can be done with a custom cell renderer.
So, if someone has an example or a hint to an example, would be helpful.

Also would do an example of international flag graphics near text in the same cell.
This would have to be modified so that the arrow is always right aligned in the cell with left aligned text.

Alexander

[fuchs4dMember]

Peter,

thank you for clarifying and the link.
(This means the “keys” for accessing datasource fields from the dataprovider are a combination of the attributes “name” and “displayname”, because “name” alone is not unique in the example).

Got drop downs to work with a simple array in a grid and from there can do all I want.

To use the automatic key/value feature:

Does the automatic key/value feature also work if the data to be looked up is NOT XML based (as in the grid example), but array based?
Just for information.

Alexander

[fuchs4dMember]

Confusing in the grid example for key/values column is:

// name – the field’s name in the data source.
{ name: ‘EmployeeID’, displayname: ‘EmployeeName’, map: ‘m\\:properties>d\\:EmployeeID’, text: ‘EmployeeName’, id: ‘EmployeeID’, source: employeesAdapter.records },
{ name: ‘EmployeeID’, map: ‘m\\:properties>d\\:EmployeeID’ },

In the above dataadapter, the field ‘EmployeeID’ is defined two times.
The 2nd is a subset of the first, the 2 attributes ‘name’ and ‘map’ are exactly the same.
The 1st has 2 more attributes that the 2nd field does not have.

Makes no sense to me, especially because I think a datafield name should be unique in a dataadapter.

Saw this same issue in another grid topic with the hint to read the comments carefully, however does not clarify for me the reason that the field is defined 2 times with the same name.

Thanks for clarifiying this (why the field is defined 2 times and if so, why it is neccessary to have it 2 times or if the example would still work when the 2nd definition is ommitted).

Alexander

[Author]

Posts