Opened 11 years ago

Last modified 7 years ago

#1167 assigned defect

Screen resolution is problematic in Maze and Physics (The activity extends beyond the screen)

Reported by: wwdillingham Owned by: garycmartin
Priority: Normal Milestone:
Component: ActivityTeam Version: 0.84.x
Severity: Minor Keywords: soas gpa resolution display
Cc: Distribution/OS: Unspecified
Bug Status: New

Description

When running SoaS on hardware with various non-XO native screen resolutions, activities cannot adapt to the correct resolution.

This can be seen within both maze and physics activities.

This problem arose during a gpa pilot program session with caroline meeks.

It looks like sugar is not properly reporting to the activity the proper screen resolution, which is why this bug has been filed under sugar.

Change History (9)

comment:1 Changed 11 years ago by wwdillingham

  • Severity changed from Major to Minor

comment:2 Changed 11 years ago by wwdillingham

  • Summary changed from Screen resolution is problematic in Maze and Physics to Screen resolution is problematic in Maze and Physics (The activity extendeed beyond the screen)

comment:3 Changed 11 years ago by wwdillingham

  • Summary changed from Screen resolution is problematic in Maze and Physics (The activity extendeed beyond the screen) to Screen resolution is problematic in Maze and Physics (The activity extends beyond the screen)

comment:4 Changed 11 years ago by garycmartin

I've not seen this myself to debug, but this issue is likely linked to something PyGame (or OLPCGames) is doing differently than Sugar regarding picking up resolution/dpi settings.

comment:5 Changed 11 years ago by gregorio

This was a problem seen at GPA.

  • Maze and physics were to big to fit on the screen. Not sure if that

is a problem of the actitvity itself, but a screen resolution changing
tool would be useful. This is important on SoaS when it wasn't so hot
on XO.

from: http://lists.sugarlabs.org/archive/iaep/2009-August/007546.html
specs on the computer in question are available in the early notes.

Several other activities also have this issue.

Thanks,

Greg S

comment:6 Changed 11 years ago by tomeu

  • Component changed from sugar to ActivityTeam
  • Milestone changed from Unspecified by Release Team to 0.86
  • Owner changed from tomeu to garycmartin
  • Priority changed from Unspecified by Maintainer to Normal

comment:7 Changed 11 years ago by sascha_silbe

  • Component changed from ActivityTeam to SoaS
  • Distribution/OS changed from SoaS to Unspecified
  • Owner changed from garycmartin to mchua sdz

Bulk change distribution=SoaS -> component=SoaS

comment:8 Changed 11 years ago by sdz

  • Component changed from SoaS to ActivityTeam
  • Owner changed from mchua sdz to garycmartin
  • Status changed from new to assigned

Assigning back to the activity team!

comment:9 Changed 7 years ago by dnarvaez

  • Milestone 0.86 deleted

Milestone 0.86 deleted

Note: See TracTickets for help on using tickets.