|
Instead each project has a text based TODO list which records outstanding mods, internal changes and bugs. Those are transferred to the mods history when they are fixed. The file itself (and the revision history text file) are part of the VS project, and are built into the EXE / DLL when it is compiled.
Since there is only me, I don't need anything more sophisticated.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You pretty much described my situation, with the only difference that we are in two
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Well, that is my way too.
"I have not failed. I've just found 10,000 ways that won't work." Thomas A. Edison
"Politicians and diapers should be changed often and for the same reason." Eça de Queiroz (1845 - 1900)
|
|
|
|
|
Bacon flavoured CListCtrl!
|
|
|
|
|
So you generate a lot of bugs just so you can eat 'em?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Of course! YUMMY!
|
|
|
|