Revision 81b3a40d
Added by danij over 11 years ago
Added by Files
- added
- modified
- copied
- renamed
- deleted
- doomsday
- api
- api_map.h (diff)
- api_mapedit.h (diff)
- dd_share.h (diff)
- client
- include
- src
- audio
- client
- dd_main.cpp (diff)
- edit_map.cpp (diff)
- map
- bsp
- bspbuilder.cpp (diff)
- bspleaf.cpp (diff)
- bspnode.cpp (diff)
- entitydatabase.cpp (diff)
- gamemap.cpp (diff)
- hedge.cpp (diff)
- line.cpp (diff)
- p_data.cpp (diff)
- p_dmu.cpp (diff)
- p_maputil.cpp (diff)
- p_objlink.cpp (diff)
- p_particle.cpp (diff)
- plane.cpp (diff)
- polyobj.cpp (diff)
- r_world.cpp (diff)
- sector.cpp (diff)
- vertex.cpp (diff)
- render
- plugins
- server
- api
API: Standardized map element indices across all APIs
It appears we had accumulated various different representations for
map element indices. Some indexes were 1-based, some APIs used
unsigned integers, etc... As we breaking API compatibility for this
release now is a good time to address this issue and apply a global
standard.
All map element indexes are now 0-based and all indices specified to
public APIs are represented with the platform's signed, integer type.
MapElement now stores an indexInArchive in addition to indexInMap.
This being the index of the relevant map element/definition from the
"archived" map (e.g., in id tech 1 format). The in-archive index is
specified when transferring the map element using the map edit API.
The old DD_SECTOR_COUNT (etc...) engine constants have been replaced
with a new DMU API P_Count() function.
Also, the WAD Map Converter plugin now uses the same representation.