[OPEN] [#1780] PagingToolbar customizing button text and tooltip text does not work

  1. #1

    [OPEN] [#1780] PagingToolbar customizing button text and tooltip text does not work

    We just tried to customize the button text and tooltip text of PagingToolbar:

    <BottomBar>
    <ext:PagingToolbar DisplayMsg="Displaying Trains {0} - {1} of {2}" 
    EmptyMsg="No trains to display"  
    firsttext="First Page"                         
    prevtext="previous page" 
    BeforePageText="Page" 
    AfterPageText="of" 
    nexttext="next page"                                              
    LastText="Last Page" 
    RefreshText="Refresh" 
    runat="server" />
    </BottomBar>
    But this does not work correctly for some attributes. Please see attached screenshot:Click image for larger version. 

Name:	Paging1.JPG 
Views:	103 
Size:	21.8 KB 
ID:	25356Click image for larger version. 

Name:	Paging2.JPG 
Views:	99 
Size:	13.2 KB 
ID:	25357Click image for larger version. 

Name:	Paging3.JPG 
Views:	120 
Size:	12.0 KB 
ID:	25358Click image for larger version. 

Name:	Paging4.JPG 
Views:	109 
Size:	15.5 KB 
ID:	25359


    Attributes that work fine:
    prevtext="previous page"
    DisplayMsg="Displaying Trains {0} - {1} of {2}"
    AfterPageText="of"

    Attributes that do not work:
    firsttext="First Page"
    BeforePageText="Page"
    nexttext="next page"
    LastText="Last Page"
    RefreshText="Refresh"

    thank you for your help,
    breg
  2. #2
    Hello Breg!

    I have just tried setting the custom settings to the GridPanel > ArrayGrid > ArrayWithPaging example and it works just fine.

    The problem is because you are using the default English values for the inputs. This is an issue indeed but can easily be confused if you add a single character differently. Even upper/lowercase counts.

    I have logged issue #1780 to track this defect and will post a follow-up as soon as we have it fixed. In the time being, you can just slightly change the text or even add any "invisible character" (like &nbsp;) to bypass the "default-handling-behavior".

    In case you really need to use the default value and no artifact or casing helps, just add a custom config specifying it, for example:

    FirstText="First Page"
    Would become a block within the ext:PagingToolbar one:

    <CustomConfig>
        <ext:ConfigItem Name="firstText" Value="First Page" />
    </CustomConfig>
    And this would bypass any "default value handling" server-side code.

    Hope this helps!

    EDIT: another way into "fooling" the default value inferer would be (still taking the FirstText example):
    FirstText="<b></b>First Page"

    Or any other "empty" html tag/block that does not "format" (for example, a span instead of a div).
    Last edited by geoffrey.mcgill; Jun 06, 2020 at 5:36 AM.

Similar Threads

  1. [CLOSED] changing button's text in directevent dose not work.
    By hdsoso in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: May 16, 2014, 10:35 AM
  2. [CLOSED] Gridpanel: customizing PagingToolbar text strings
    By tanky65 in forum 2.x Legacy Premium Help
    Replies: 6
    Last Post: Jun 25, 2013, 1:27 PM
  3. Replies: 4
    Last Post: Jun 05, 2013, 9:25 PM
  4. how to change the text on PagingToolbar?
    By gmpd123 in forum 2.x Help
    Replies: 1
    Last Post: Jul 24, 2012, 1:22 PM
  5. [CLOSED] Text align left for button text
    By macap in forum 1.x Legacy Premium Help
    Replies: 4
    Last Post: Jul 09, 2009, 10:52 AM

Posting Permissions