That would be great!
I would happily test it for you.
If you get motivated, the next feature that i would need is the tagging that people have discussed. the idea of being able to designate a span of time, with many programs used during that span, as a certain time allocation. Your suggestion of naming the files to contain a keyword, and then searching for the keyword would work, at least in some cases. But i think adding a new feature to the program to know about a tag directly would really help me. I'm guessing the tag would start out uninitialized, and perhaps stay that way forever, meaning, it's optional for those that dont need it. From my understanding of how the program works, it would mean something like re-writing the .csv file, cuz tags are provided by the user for time already passed. Perhaps even at the end of the day. Or some other way to store tags, but then the detailed view needs to read 2 files. Or something.
thing is, i really LIKE that the program today only appends to the .csv file, and doesnt lock it. cuz then i can edit the .csv file myself, and TitleLog keeps on working happily. But perhaps TitleLog adding a tag in the past would be ok, if it keeps re-opening then closing the file for each edit. But then you're re-writing the whole file each time there's a tag entry from the user. Dunno. I can see why that doesnt fit with the current program paradigm. And as i said, i like that paradigm.