Opened 17 years ago

Closed 17 years ago

#3074 closed defect (invalid)

SIMON2: Screen disadjustment on opie build

Reported by: SF/ys_ Owned by:
Priority: normal Component: Engine: AGOS
Version: Keywords:
Cc: Game: Simon the Sorcerer 2

Description

After aquadran fixed the [1]bug #1653599 I downloaded his [2]new opie build

Now Simon The Sorcerer 2 works, but I've noticed something weird. The game area is painted at top of the scree, inventory/actions area is painted just down of it, and at bottom a black area where keyboard is usually shown.

However, the game and the inventory/actions area react as if the game were bottom-adjusted. Also, the cursor flicker discovering us the real reaction graphics. Please take a look at the photos.

[1] https://sourceforge.net/tracker/?func=detail&atid=418820&aid=1653599&group_id=37116 [2] http://handhelds.org/~aquadran/distro/opie/scummvm_svn-20070218-r0_arm.ipk

Ticket imported from: #1662605. Ticket imported from: bugs/3074.

Attachments (3)

simon2opie1.jpg (39.3 KB ) - added by SF/ys_ 17 years ago.
Simon weird bug on opie build - explanation 1/3
simon2opie2.jpg (36.3 KB ) - added by SF/ys_ 17 years ago.
Simon weird bug on opie build - explanation 1/3
simon2opie3.jpg (38.8 KB ) - added by SF/ys_ 17 years ago.
Simon weird bug on opie build - explanation 3/3

Download all attachments as: .zip

Change History (7)

by SF/ys_, 17 years ago

Attachment: simon2opie1.jpg added

Simon weird bug on opie build - explanation 1/3

by SF/ys_, 17 years ago

Attachment: simon2opie2.jpg added

Simon weird bug on opie build - explanation 1/3

comment:1 by SF/ys_, 17 years ago

Attached the second screenshot. Only one more. File Added: simon2opie2.jpg

by SF/ys_, 17 years ago

Attachment: simon2opie3.jpg added

Simon weird bug on opie build - explanation 3/3

comment:2 by SF/ys_, 17 years ago

The last one. File Added: simon2opie3.jpg

comment:3 by SF/ys_, 17 years ago

Resolution: invalid
Status: newclosed

comment:4 by SF/ys_, 17 years ago

I had aspect correction enabled. Disabling it (as default) makes the job. Sorry.

Note: See TracTickets for help on using tickets.