[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Pingus-CVS] Issue 31 in pingus: Exit and entrances are badly implemeted
From: |
pingus |
Subject: |
[Pingus-CVS] Issue 31 in pingus: Exit and entrances are badly implemeted |
Date: |
Thu, 08 Sep 2011 13:11:40 +0000 |
Status: Accepted
Owner: address@hidden
Labels: Type-Enhancement Priority-Medium Component-Engine Component-Editor
New issue 31 by address@hidden: Exit and entrances are badly implemeted
http://code.google.com/p/pingus/issues/detail?id=31
Exits and entrances are currently implemented like this:
(entrance
(type "generic")
(position 459.357 577.143 0)
(owner-id 0)
(direction "right")
(release-rate 150))
(exit
(surface
(image "exits/ice2")
(modifier "ROT0"))
(position 1297 560 0)
(owner-id 0))
This implementation has numerous short comings.
1) entrances have no graphical representation at all, the user has to
manually insert hotspots, which is cumbersome and confusing for the user
2) exit are only allowed to consist of a single surface
3) animated entrances are not possible, as the entrance can't sync it's
animation easily with the release rate
4) no way to store how exists and entrances should manipulate the collision
map
5) lack of symmetry, exit and entrance implementation should be the same,
but is different
6) (type "") exists, but is not properly accessible from the editor with
the ObjectSelector
- [Pingus-CVS] Issue 31 in pingus: Exit and entrances are badly implemeted,
pingus <=