Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    Success! Looks like we've fixed this one. According to our records the fix was applied for EXTGWT-3496 in 3.1 beta.
  1. #1
    Sencha Premium Member
    Join Date
    May 2013
    Posts
    12
    Vote Rating
    0
    sws is on a distinguished road

      0  

    Default Chart AreaSeries orphan sprite

    Chart AreaSeries orphan sprite


    Version(s) of Ext GWT
    3.0.6

    Browser versions and OS
    (and desktop environment, if applicable)
    • IE 10
    • FireFox 26.0
    • Chromium 31.0.1650.63
    All on Ubuntu Linux - 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    Virtual Machine
    No
    Description
    AreaSeries sprites are being left behind when the data store of a chart is cleared. As a result, progressively changing the series of a chart causes sprite debris.

    Run mode
    both

    Steps to reproduce the problem
    1. Run the AreaSeriesSpriteBug.java file in a GXT project.
    2. Lauch app, click on 'Populate' button
    3. Click on 'Clear' button (sprite remains)
    4. Click on 'Populate' again and new sprite appears in addition to old sprite

    Expected result
    Sprites should disappear from screen when the datastore is cleared.

    Actual result
    Sprite remains on screen.

    Test case
    See AreaSeriesSpriteBug.java.

    Helpful Information

    Screenshot or video
    Live test
    n/a

    Debugging already done
    • no error messages in GWT dev mode nor in javascript console
    • doing a 'replace all' without changing out the AreaSeries removes the sprites properly. But this prevents mutable chart configurations.

    Possible fix
    Investigate what happens when the AreaSeries is not changed out and a 'replace all' is called because that seems to work.
    Last edited by sws; 14 Jan 2014 at 9:00 PM. Reason: Remove debris

  2. #2
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,716
    Vote Rating
    87
    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


    Thanks, I've reproduced this and filed it internally. The fix seems to be to either override clear() in AreaSeries so that it clears out the `areas` variable, or stop tracking each area in the `areas` list, but use the existing `sprites` list that already is automatically cleared when the superclass runs clear. I'm not yet sure which is the correct solution, and will continue looking into it.

    As a workaround, you can more or less follow the areas.clear() idea, but since areas is private, you'll need to use the so-called violator pattern to reach in and tweak it. Could look like this:
    Code:
        AreaSeries<Point> ser = new AreaSeries<Point>() {
          @Override
          public void clear() {
            super.clear();
            getAreas().clear();
          }
    
          private native SpriteList<?> getAreas() /*-{
            return this.@com.sencha.gxt.chart.client.chart.series.AreaSeries::areas;
          }-*/;
        };
    This seems to fix the bug, though I'd love to get independent confirmation of this.

  3. #3
    Sencha Premium Member
    Join Date
    May 2013
    Posts
    12
    Vote Rating
    0
    sws is on a distinguished road

      0  

    Default


    Thank you Colin. That workaround addresses the issues we are having.

Thread Participants: 1

Tags for this Thread