| ??? 10/05/09 17:47 Read: times |
#169455 - One step at a time Responding to: ???'s previous message |
Yes, it always pays to make only a few changes at a time, and ensure that you can always go back to the last working version.
If you don't have have a proper version control system, you can do it quite easily with just XCOPY to take a complete copy of your project "tree" - or do a "drag-and-drop" copy in explorer. I always keep my current working version in a folder called "_work", and then take "snapshots" as above into folders named "yyyy-mm-dd-hhmm" - this means that they will display in chronological order when displayed in Explorer or by DIR in name order; eg,
C:usersmeblahblahproject_work <-- current "work-in-progress"
2009-10-05-1051 <-- snapshot at 10:51 on 5 Oct 2009
2009-10-05-1000 <-- snapshot at 10:00 on 5 Oct 2009
2009-10-05-0926 <-- snapshot at 09:26 on 5 Oct 2009
etc, etc,...
Then, if it all stops working, you just do a compare between _work and the last working snapshot. If you don't already have a utility to compare folder trees, I'll recommend this one: http://winmerge.org/ |
| Topic | Author | Date |
| uVision & 89v51RD2 - stack problem? | 01/01/70 00:00 | |
| when calling a function, uC seems to can't return back | 01/01/70 00:00 | |
| my debugging technique | 01/01/70 00:00 | |
| incomplete | 01/01/70 00:00 | |
| it works now | 01/01/70 00:00 | |
| That's a huge leap! | 01/01/70 00:00 | |
| It doesn't work right in "compact" and "large" memory model | 01/01/70 00:00 | |
| it wasn't me - dwarfs did it :) | 01/01/70 00:00 | |
| Source code repository | 01/01/70 00:00 | |
| One step at a time | 01/01/70 00:00 | |
| cool advice | 01/01/70 00:00 | |
no, you didn't | 01/01/70 00:00 |