GUI optimizations
jnettels opened this issue · 5 comments
The output path for the gp5 files in the GUI always resets when I reopen the program. It would be more comfortable to have it remember my output path (or all the choices for that matter).
This way I only need to hit create tabs when I got new CLDC.
Also: A tickbox labled "convert official Rocksmith songs" would be neat. This would save some conversion time when I got new CDLC (and make users aware of this feature in the first place).
Those are really minor points, but noteworthy :-)
Storing the previous settings will require to save a config file somewhere. I left that out initially for simplicity, and also because I don't really like it when random software clutters up my file system with tons of config files :) It is a useful feature, though.
I'm not quite sure I get the "official Rocksmith" thing. I can't really distinguish CDLC from official songs (at least not in a quick and easy manner), so best I could do is exclude songs.psarc and perhaps the rs1compatibility files. If I'm going to write a config file, anyway, I could also just save all the files that were previously processed and allow an "incremental" update, converting only those files that are new.
Your average user is lazy, so whenever he has added a new CDLC, he wants to update his Tabs-Collection with as least effort as possible in the shortest amount of time.
My request was not formulated well, though... I didn't think about the official DLC in the DLC folder. You have a hard time excluding them, of course and I don't think that is necessary.
Another thing came to mind though: A user who has doesn't know that CDLC exist will be irritated by the tickbox I proposed...
The incremential update would be super fast, but it would only work when the filenames of the psarcs change with new versions, right? So if I download a psarc where the charter deleted the version number and the filename doesn't change, I won't even know why the gp5 doesn't update...
No, I would of course save the last modification date of each file, so if you overwrite it with a new file, it would get updated.
Wow, alright!
Then just forget about the "official content" tickbox, it won't be necessary, I guess :-)
Maybe have only a tickbox for the inremential update, in case you want to rebuild the full collection (but that might not really be necessary as well)
It took a long time, but I finally updated the GUI. It now remembers settings and also stores a simple timestamp in the output directory. If requested, only those psarcs which are newer than that timestamp will be converted on the next run.
Features will be available with the next release.