Opened 15 years ago

Last modified 14 years ago

#850 new defect

etoys - strange screen scaling and clipping

Reported by: martin.langhoff Owned by: mchua sdz
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Etoys Version: Unspecified
Severity: Unspecified Keywords:
Cc: etoys-notify@… Distribution/OS: Unspecified
Bug Status: New


Etoys on SoaS has strange problems of screen sizing and clipping.

For example, in Demos & Tutorials, the second tutorial many things are clipped, and some objects don't appear on screen.

This can be "fixed" by setting the scaling to "no scaling" but this prevents elements of the Sugar UI from displaying (such as the frame).

Change History (8)

comment:1 Changed 15 years ago by erikos

  • Milestone changed from soas_fossvt to soas_linuxtag

yes - there is as well a flickering when starting etoys. We need to check if this is Soas only - or happens in distro packages as well.

comment:2 Changed 15 years ago by erikos

  • Bug Status changed from Unconfirmed to New

comment:3 Changed 15 years ago by bert

The "Demon castle" tutorial issue is valid. A work-around is to first choose "no scaling" and then "scale to fit" which uses the proper scale factor. I filed an upstream report:

The flickering should be reduced in version 4.0.2213. This is the upstream bug:

comment:4 Changed 15 years ago by erikos

Thanks bert for following up. I guess #983 is handled by the upstream bug as well?

comment:5 Changed 15 years ago by bert

  • Cc etoys-notify@… added

No, the flickering is unrelated to the wrong scaling factor.

The "Demon castle" tutorial was made before the current scaling policy was in place. It simply needs to be updated (re-saved at the right resolution).

comment:6 Changed 14 years ago by sascha_silbe

  • Component changed from Etoys to SoaS
  • Distribution/OS changed from SoaS to Unspecified
  • Owner changed from bert to mchua sdz

Bulk change distribution=SoaS -> component=SoaS

comment:7 Changed 14 years ago by sdz

  • Milestone changed from Strawberry to Unspecified by Release Team

What's the status here? Can we close this?

comment:8 Changed 14 years ago by sdz

  • Component changed from SoaS to Etoys

This is a Etoys issue that got accidentally assigned to SoaS during an auto-tag. Reassigning - sorry for the confusion.

Note: See TracTickets for help on using tickets.