frustrated with torque
by Foestar · in General Discussion · 11/25/2009 (6:43 am) · 3 replies
I know that design comes with errors and mistakes. But sometimes I just get so frustrated with torque to the point where I wonder why I even try.
Last night while attempting to place in new music in my main menu I accidentally saved an old file over my new one losing some of my work. The file I saved over was just an in game menu. Nothing too big, so I wasn't worried. However, for some unknown reason this caused the play button in my 2nd main menu page to stop working all together. I checked with my function and it's still there and should work..... yet doesn't. I've tried even recreating the button and found that it still doesn't work. So the problem isn't in the gui. It seems the my code which was working no longer works for no particular reason. I've had problems like this so much that combined with the loss of some work has really caused me to become frustrated with torque all together.
I was hoping maybe someone knew a reason why my function would stop working over night when no change has been made to the code at all.
The code I use is a simple load into a mission code which as I said worked before.
Last night while attempting to place in new music in my main menu I accidentally saved an old file over my new one losing some of my work. The file I saved over was just an in game menu. Nothing too big, so I wasn't worried. However, for some unknown reason this caused the play button in my 2nd main menu page to stop working all together. I checked with my function and it's still there and should work..... yet doesn't. I've tried even recreating the button and found that it still doesn't work. So the problem isn't in the gui. It seems the my code which was working no longer works for no particular reason. I've had problems like this so much that combined with the loss of some work has really caused me to become frustrated with torque all together.
I was hoping maybe someone knew a reason why my function would stop working over night when no change has been made to the code at all.
The code I use is a simple load into a mission code which as I said worked before.
function loadCharacterChoice()
{
Canvas.setCursor("DefaultCursor");
createServer( "SinglePlayer", expandFileName("~/data/missions/charchoice.mis") );
%conn = new GameConnection(ServerConnection);
RootGroup.add(ServerConnection);
%conn.setConnectArgs($pref::Player::Name);
%conn.setJoinPassword($Client::Password);
%conn.connectLocal();
}About the author
Foestar Entertainment Biohazard Entertainment
#2
11/25/2009 (10:20 am)
I second this. No developer should be working without a source code management net of some sort these days, and Subversion is a pretty good net.
#3
I have spent time programming in multiple languages and I can't tell you how much Subversion (as well as Git and Hg) has saved my neck at times - especially when you're working with other people.
Just remember the few rules that'll save you pain:
o Check in your work often, as minor changes are easily forgotten in large commits
o Annotate every commit you make, we mere mortals forget too easily.
o Wherever you're checking your code in to, make sure it is a robust set up, after all, you're relying on it to keep far more important things than just your present work.
You can find subversion at it's home: http://subversion.tigris.org/
In addition to running subversion, you should consider also using tortoisesvn (if you're running windows. Otherwise the command line will see you through ;), as it makes the whole process far nice (again, only under windows), and you can find it here: http://tortoisesvn.tigris.org/
12/06/2009 (5:54 am)
I have to agree with that.I have spent time programming in multiple languages and I can't tell you how much Subversion (as well as Git and Hg) has saved my neck at times - especially when you're working with other people.
Just remember the few rules that'll save you pain:
o Check in your work often, as minor changes are easily forgotten in large commits
o Annotate every commit you make, we mere mortals forget too easily.
o Wherever you're checking your code in to, make sure it is a robust set up, after all, you're relying on it to keep far more important things than just your present work.
You can find subversion at it's home: http://subversion.tigris.org/
In addition to running subversion, you should consider also using tortoisesvn (if you're running windows. Otherwise the command line will see you through ;), as it makes the whole process far nice (again, only under windows), and you can find it here: http://tortoisesvn.tigris.org/
Torque Owner Daniel Buckmaster
T3D Steering Committee
I know how you feel - I've often become so frustrated with something that inexplicably doesn't work, doesn't work for a very good reason and refuses to be fixed, used to work and now doesn't, and even when something used to be broken and became mysteriously fixed, that I've questioned my choice of engine, my abilities, my ambition, and whether I should really be programming anything at all.
I really can't help with the problem you've got right now, except to suggest you get TortoiseSVN set up and commit your work each night, and after each coding/scripting milestone during a day. That way when something stops working, you can roll back and see exactly what changes have been made and what might have caused the problem. Saves a lot of hair-pulling.