Quote:
|
Originally Posted by JScones
I'd almost suggest that a new key should be written when manually adding entries which SH3Cmdr can check for and exclude. Something such as "NonSH3Entry=1" or whatever. Either way, though, it's only one extra line of code.
EDIT...Reflectively thinking...Perhaps by writing a unique key you can save yourself some hassle when removing your changes from the Log files? For instance, SH3Cmdr won't care whether the "NonSH3Entry" value is 0, 9, 99, 354.66 or PurpleMonkeyDishwater, so you could specifically write "NonSH3Entry=SH3Gen" and then check for the presence of this value when removing your entries.
|
Yes. Thats so much better than my proposal. And seems to work too. I have just loaded a file with additional properties NonSh3=true and it showed up fine. I must do some more testing of course.
In fact this idea will help me implement some new features easily
