[#SQ-400] Screen refresh problem - dashboard

squeakland

Screen refresh problem

Created: 18/Sep/09 06:09 PM Updated: 02/Dec/11 05:42 AM

Component/s:

etoys, etoys-linux

Fix Version/s:

future release

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. Photo 6.jpg
(71 kB)

Issue Links:

Duplicate

This issue is duplicated by:

SQ-924 Etoys does not start on laptops with screen resolution 1366x768 under sugar

Related

This issue is related to:

SQ-455 project doesn't paint, except where cursor is (miner lamp bug)

Description

« Hide

When starting Etoys4-ToGo-RC under Ubuntu 8.04 (netbook edition as default on Classmate 3, but switched to classic desktop view), the screen remains black on startup (see attachment). Screen updates only every other second or so.

This does not happen in the "mobile desktop" view. In the classic mode, double-clicking the title bar fixes it (maximizes window although it was already almost maximized). The car animates smoothly. Double-clicking title bar again, to go back to original size, restores the problem. Black screen at first, then jumpy animation.

Sort Order:

[ Permalink | « Hide ]

teefal added a comment - 19/Sep/09 10:57 AM

I experienced a similar thing using the plugin on the Mac. The difference is that the screen initially painted (Bert's collision example), but the non-moving parts went away, leaving only the moving parts visible. We had to close the project and reopen it to continue.

[ Permalink | « Hide ]

Bert Freudenberg added a comment - 14/Dec/09 01:22 PM

Reproduced on an XO-1 running F11, see http://wiki.laptop.org/go/F11_for_XO-1 (I tried on build 10 which includes etoys-4.0.2339). It works fine under Sugar, the problem only shows when switching to GNOME using the Sugar control panel and running Etoys from the menu.

It happens when resizing the OS window using the window frame's maximize button. When resizing using the window frame borders it works fine. Clicking Etoys' full screen button works, too. It is only in "maximized" mode.

Also, while in the broken/maximized state, Squeak consumes significantly more CPU. Unmaximizing restores CPU utilization back to normal. Profiling might reveal what it is doing.

Interestingly, it works fine on an XO-1.5 running virtually identical software http://wiki.laptop.org/go/F11_for_1.5