Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium Member feelinforyou's Avatar
    Join Date
    Dec 2012
    Posts
    99
    Vote Rating
    4
    feelinforyou is on a distinguished road

      0  

    Default Different sprite trigger look for ComboBox

    Different sprite trigger look for ComboBox


    If i look at the examples of Ext JS 4. The Combobox seems to have the same trigger-look as the other triggers in the default state. Lighter in the top and darker at the bottom.

    http://dev.sencha.com/deploy/ext-4.1...ndex-gray.html
    You can see this in the first picture.

    But if you look at the examples of GXT 3.0.1 and GXT 2.3.0, the Combobox seems different.
    You can verify this in the second picture.

    I have looked into the trigger-sprites of GXT 2.3.0. In the resources, if you go in the path "resources\images\default\form", you can see the sprites of every trigger. Everyone has the same look and seems to descended from trigger-tpl.gif. But the first state of trigger.gif is different, without the color change. This ist the one for the combobox. So the trigger always looks different.
    Attached Images

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,734
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Interesting to note, and probably not deliberate, but a bug? If you require GXT to look identical to Ext JS, you can create an appearance that will make these details the same (or custom css in gxt 2).

    I can file it, but this is a) behaving correctly and b) internally consistent, so I'm not sure how high of priority this will be, especially considering that this has been consistently different for quite a while (i.e. we would be changing the look for any app that has used GXT 2 or 3 up until now, and possibly 1, though I don't have that running locally atm).

  3. #3
    Sencha Premium Member feelinforyou's Avatar
    Join Date
    Dec 2012
    Posts
    99
    Vote Rating
    4
    feelinforyou is on a distinguished road

      0  

    Default


    What about this little inconsistency? Is it going to be fixed for 3.1? Now it will be the right time for this.

  4. #4
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,734
    Vote Rating
    90
    Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light Colin Alworth is a glorious beacon of light

      0  

    Default


    Our target release for 3.1.0 is two months after the beta, which puts it right now, and we're freezing code and going through vigorous testing, so we're a few weeks too late to reconsider something like this, especially after a year of no follow up from any user.

    GXT 2 is being used as the benchmark for GXT 3 look and feel, except for Neptune, where we are starting with Ext JS's version, and making allowances for the fact that the theme is being applied to a totally different codebase, and as a requirement of the project must be customizable without writing code, only config. The GXT 3.1 final theme builder will include basic functionality to allow developers to replace images with either compiled images or SVG files that should have theme properties applied to them, so this customization should be available to you in any new theme going forward.

Thread Participants: 1

Tags for this Thread