WadC 1.2 (release candidate) and future

Hi folks,

splitting from http://www.doomworld.com/vb/wads-mods/51336-wadc-community-project/ , discussion about the future development of WadC.

So there's ongoing wadc development at http://github.com/jmtd/wadc and a release candidate packaged at http://www.staff.ncl.ac.uk/jon.dowland/tmp/wadc_1.2-rc1.zip

suggestions or requests for features are welcome. Stuff I would like to eventually do include

• speed it up a lot - especially when you build data structures (if you try to use the lisp example to create some generalised routines and then try to build a crude blockmap list for e.g. avoiding collisions with a lot of random choices, it crawls)
  
• split the GUI out so you could have a wadcc
  

could you add a way to set thing tags and actions for hexen things?
the current setthinghexen(type,arg1,arg2,arg3,arg4,arg5) has no tag or special argument for things.
maybe something like:

• setthinghexen(type,tag,special,arg1,arg2,arg3,arg4,arg5)

Worst said:

could you add a way to set thing tags and actions for hexen things?
the current setthinghexen(type,arg1,arg2,arg3,arg4,arg5) has no tag or special argument for things.
maybe something like:

• setthinghexen(type,tag,special,arg1,arg2,arg3,arg4,arg5)

Possibly, yes. Although

Note that arg1 in linetypehexen() is the same as tag in linetype().

so arg1 = tag, leaving actions. But if that were true, how would you set arg1 (or does arg2 slot down to arg1, leaving arg5 empty?) Either way, there's some improvement to make there.

Hexen THINGS entry:
* Thing ID (aka tag or TID)
* X/Y/Z pos
* Angle
* Type (aka doomednum)
* Flags
* Special
* Args[5]

Hexen LINEDEFS entry:
* First and second vertices
* Flags
* Special (aka type)
* Args[5]
* Front and back sidedefs

So, it's important not to confuse the type of a thing (its doomednum) with the type of a line (its special), or the tag of a thing (its TID) and the tag of a Doom linedefs (its single argument).

May i suggest to add a function like a "operation recorder", in which you perform some operations (creating a room with some characteristics, for example) like in a normal editor and the corresponding code is created, so that you can use it elsewhere repeatedly?


Lorenzo

Lorenzo said:

May i suggest to add a function like a "operation recorder", in which you perform some operations (creating a room with some characteristics, for example) like in a normal editor and the corresponding code is created, so that you can use it elsewhere repeatedly?


Lorenzo

That already exists for hand-drawing linedefs.

@Jon: i didn't notice this first time i used it... :-(