Results 1 to 4 of 4

Thread: summaryType configuration missing from column when GridSummary feature used

    Success! Looks like we've fixed this one. According to our records the fix was applied for DSGNR-1062 in a recent build.
  1. #1
    Touch Premium Member
    Join Date
    Oct 2011
    Posts
    22
    Vote Rating
    0
      0  

    Exclamation summaryType configuration missing from column when GridSummary feature used

    Im trying to add the Summary Feature to a grid panel, via ext designer. The feature itself is available, however, the "summaryType" config option seems to not exist. Further more, I cant seem to find anything about this option in the grid column docs:

    http://docs.sencha.com/ext-js/4-0/#!/api/Ext.grid.column.Column

    however, it is shown in the example for the summary feature:

    http://docs.sencha.com/ext-js/4-0/#!/api/Ext.grid.feature.Summary

    Code:
    columns: [{
            dataIndex: 'student',
            text: 'Name',
            summaryType: 'count',
            summaryRenderer: function(value, summaryData, dataIndex) {
                return Ext.String.format('{0} student{1}', value, value !== 1 ? 's' : ''); 
            }
    By following standards, I cannot directly modify the outputted UI file. So my question is, how can I make this work, without editing the ui file, and without promoting every column to a class?

    Also, please add this option to the API docs, Im assuming this is missing from designer because it was forgotten in the API.

    Thanks

  2. #2
    Touch Premium Member
    Join Date
    Oct 2011
    Posts
    22
    Vote Rating
    0
      0  

    Default replies?

    It appears that a reply in this forum is a rare occurrence. Is there a better place to post this issue?

  3. #3
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    145
      0  

    Default

    Randy -

    Sorry for the late response. We are heavy under development of Designer 2.0 and missed this. You are correct in assuming that this was missed because of it not being in the docs. I will move this thread and create a bug report based off of it.

    Unfortunately for this particular case I cannot think of a simple work around without hand editing the file.
    Aaron Conran
    @aconran

  4. #4
    Touch Premium Member
    Join Date
    Oct 2011
    Posts
    22
    Vote Rating
    0
      0  

    Default Thanks

    Thank you, this is exactly what I needed to know.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •