Moving block_path/block_radius
Posted: Wed Mar 23, 2011 3:30 pm
This idea came from talking with tiger_eye while he worked on this: http://forums.te4.org/viewtopic.php?f=4 ... 61&start=0
Currently if you want to modify the behavior of block_path/block_radius you can drop in an entirely new function easily, but if you just want to TWEAK the original it can become complicated and either you end up copying/pasting or creating a dummy target type to grab the original function. I suggest moving the default block_path/block_radius functions into the engine.Target namespace, and referring back to those functions in Target:getType. That way you could call engine.Target.default_block_path from somewhere else. Thoughts?
EDIT: I didn't post a patch since I know tiger_eye's patch isn't in the SVN yet. I can post one after those changes go in if you want.
Currently if you want to modify the behavior of block_path/block_radius you can drop in an entirely new function easily, but if you just want to TWEAK the original it can become complicated and either you end up copying/pasting or creating a dummy target type to grab the original function. I suggest moving the default block_path/block_radius functions into the engine.Target namespace, and referring back to those functions in Target:getType. That way you could call engine.Target.default_block_path from somewhere else. Thoughts?
EDIT: I didn't post a patch since I know tiger_eye's patch isn't in the SVN yet. I can post one after those changes go in if you want.
