Ticket #7660 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

XO Neighborhood icon drawing & erase glitches

Reported by: garycmartin Owned by: marco
Priority: high Milestone: 8.2.0 (was Update.2)
Component: sugar Version: Development build as of this date
Keywords: r+ Cc:
Action Needed: finalize Verified: no
Deployments affected: Blocked By:
Blocking:

Description

(joyride-2212) After attaching to xochat.org jabberserver and watching some XO arrival and departure churn, the departing XO icons are not 100% erased (parts of the head left on screen). Also on closer inspection, most displayed XOs have a few pixels clipped off the top of their heads. See attached screen shot (note the pixel remnants). Not sure if shared activity icons are also affected by this, I didn't see enough of them churn.

Your own XO icon also has a slight pixel or two jump to the top left for both the Neighborhood and Group view (i.e. the XO zoom effect doesn't quite align with the final placement).

Attachments

network neighborhood XO draw glitch.png (50.8 kB) - added by garycmartin 6 years ago.
0001-7660-Correctly-set-the-icon-allocation.patch (1.2 kB) - added by tomeu 6 years ago.

Change History

Changed 6 years ago by garycmartin

  Changed 6 years ago by marco

  • priority changed from normal to high
  • next_action changed from never set to diagnose

  Changed 6 years ago by mtd

Perhaps the second point:

Your own XO icon also has a slight pixel or two jump to the top left for both the Neighborhood and Group view (i.e. the XO zoom effect doesn't quite align with the final placement).

...can be dealt with in #7824.

  Changed 6 years ago by kimquirk

  • milestone changed from 8.2.0 (was Update.2) to 9.1.0

Not a blocker for 8.2

Changed 6 years ago by tomeu

  Changed 6 years ago by tomeu

  • keywords r? added
  • next_action changed from diagnose to review

  Changed 6 years ago by marco

  • keywords r+ added; r? removed

Looks fine, as long as the python bindings handle passing in floats for ints correctly.

  Changed 6 years ago by tomeu

  • next_action changed from review to package

  Changed 6 years ago by marco

  • next_action changed from package to test in build
  • milestone changed from 9.1.0 to 8.2.0 (was Update.2)

follow-up: ↓ 9   Changed 6 years ago by tomeu

|TestCase|

Boot into one XO, boot into another and see the second XO appear in the neighborhood view of the first one. Shutdown the second XO, check that the icon disappears from the first XO's neighborhood view.

in reply to: ↑ 8   Changed 6 years ago by tomeu

Replying to tomeu:

|TestCase| Boot into one XO, boot into another and see the second XO appear in the neighborhood view of the first one. Shutdown the second XO, check that the icon disappears from the first XO's neighborhood view.

That should be, _completely_ disappears.

  Changed 6 years ago by marco

  • next_action changed from test in build to approve for release

  Changed 6 years ago by marco

  • next_action changed from approve for release to add to build

  Changed 6 years ago by cscott

  • next_action changed from add to build to add to release

Exact packages and versions, please. Also tag them dist-olpc3-testing.

  Changed 6 years ago by marco

sugar-0.82.2-1.fc9

  Changed 6 years ago by cscott

  • next_action changed from add to release to test in release

Committed to stable repo: http://mock.laptop.org/gitweb/gitweb.cgi?p=repos;a=commitdiff;h=e0489cd6dec4b910445f489632adb44ba136c1c1

Should be in build 758 and following; please test.

  Changed 6 years ago by frances

tested in 8.2-759 and no icon image was left behind after leaving chat.

  Changed 6 years ago by garycmartin

  • next_action changed from test in release to finalize

Tested in 8.2-760, left running in the neighborhood view for half a day on a fairly active xochat.org jaberd server. No redraw graphic glitches seen. Working for me.

  Changed 6 years ago by gregorio

  • status changed from new to closed
  • resolution set to fixed

Closed with no doc needed. GS

Note: See TracTickets for help on using tickets.