No idea what the purpose of this is. Looks like some half-baked idea that never went anywhere.
ReadProject64ChtDev() was never called. The function can read the contents of the XML file as a string, but it does not parse the XML. There is also no XML parser in the source tree. The function always returns NULL.
WriteProject64ChtDev() was only called for known-value searches.
The writer contained a bunch of memory leaks, so removing this code is better for everyone. I tried to fix these in #41, but also broke the calls to CS_GetHit(Byte|Word) in ResultsToString(). Oh well.
In addition to removing the XML stuff, I also fixed some warnings that have slowly cropped up. Some of these warnings were introduced recently in #41.
According to Gent, this was created as a workaround for flaky crashes in the cheat search. It provided at least something to look at for disaster recovery. We're now going to focus on improving stability instead of these workarounds. But in the near future, I also want to start working on a more proper "session persistence" for some of these things.
I was always annoyed by losing my debugger sessions when closing a ROM. And it's going to get worse when I start adding basic navigation "bookmarks" to the debugger and memory editor. I want to persist this info across sessions. But I want to do it without Ad Hoc XML writers, and I don't want to bring in an XML parser anyway. That's ridiculous.
No idea what the purpose of this is. Looks like some half-baked idea that never went anywhere.
ReadProject64ChtDev()was never called. The function can read the contents of the XML file as a string, but it does not parse the XML. There is also no XML parser in the source tree. The function always returns NULL.WriteProject64ChtDev()was only called for known-value searches.The writer contained a bunch of memory leaks, so removing this code is better for everyone. I tried to fix these in #41, but also broke the calls to
CS_GetHit(Byte|Word)inResultsToString(). Oh well.In addition to removing the XML stuff, I also fixed some warnings that have slowly cropped up. Some of these warnings were introduced recently in #41.
According to Gent, this was created as a workaround for flaky crashes in the cheat search. It provided at least something to look at for disaster recovery. We're now going to focus on improving stability instead of these workarounds. But in the near future, I also want to start working on a more proper "session persistence" for some of these things.
I was always annoyed by losing my debugger sessions when closing a ROM. And it's going to get worse when I start adding basic navigation "bookmarks" to the debugger and memory editor. I want to persist this info across sessions. But I want to do it without Ad Hoc XML writers, and I don't want to bring in an XML parser anyway. That's ridiculous.