Quote: "Good idea! 700 lines is easily manageable but the more you add in the harder its going to be to keep track of - you want to start thinking about change control now before stuff gets out of hand and you find yourself using variables like 'fred' and 'dave' (which you'll mean to change later but never get round to)
"
another great point - its an easy trap to fall into, in my opinion!
i've re-written quite a bit using a sort of method for naming things now so where:
player position - was: playerposx#
player position - now: PlayerPositionX#
player money - was: money
player money - now: vMoney
I use a v before the name if its an integer variable and it also helps me to distinguish between types (i mean to say between strings and integers) as i find it odd coming from a sort of php perspective with: $variablename, going to: variablename$ - just things im getting used to.
additionally i've gone back over everything already and renamed objects, pictures and so on into a more logical path, so where:
was: Playercharacter.dbo
now: \characters\MainPlayer.dbo
and when referring to objects in my code i have started to name them rather than use numbers the whole time - i've realised already i've got to a point where i'm having to assign a group of objects id's in the hundreds just to make sure i haven't already used that object number.
I think im going to write some code to:
Check if object id is available/free.
If so save the objects name into an array along with its respective object "id/number" then when im loading an object i can just select the objects id from searching for the name in my array..
sounds like a plan at the moment anyway - or i might just do this statically a list of objects and their id's at the start of the program. not sure yet.
\\goes back to design document rather than posting on here
Paul
