search

pinosante / VAM-Evolutionary-Character-Creation

Create beatiful girls, guys and futas using a sophisticated genetic algorithm.
BSD 3-Clause "New" or "Revised" License
14 stars 3 forks source link

Allow to set a max cap for appearances read. #33

Open pinosante opened 1 year ago

pinosante commented 1 year ago

Some user mentioned having 5000+ appearance files which took forever to load. We might want to have a default CAP of 500 or so appearance files. You can also ask yourself what would be the added value of 5000 vs. 500 appearances (not much I think).

chris-b-pacon commented 1 year ago

If the app is allowed to load 50 of 500 files, which one should be loaded? Not so easy to decide. I don't like the max cap; if a user has not the time to load 5000 files, he can put his selection to a subfolder and use that instead, so he himself can decide what to use.

pinosante commented 1 year ago

Well, which files are read first might not be important. If the user finds that important he/she shouldn't have tried the app with 5000 files in the first place. So you could also just let the array fill with 500 values and then quit reading. And which files are in the array don't matter much. But I agree that you can also educate the user and tell them to make a selection of appearances. But if I play devils advocate, there might be users who have everything beautifully organized into folders with in total 1000's of appearances all organized in folders, and then, in order to use this app, they would need to make a new folder with some selection of appearances since the app doesn't have a cap. Oh well, I'm also fine with not having a cap :).

chris-b-pacon commented 1 year ago

Capping could become feasible if the user could select a sorting order.

Another elegant solution would be to provide an additional rating similar to VAM's favorite (or not), but with more levels of rating, like from 1 to 5., and use that for capping The data for these ratings could be stored as single files in the script's data folder, or much better, as a JSON inside the data folder. There should be a function to eliminate ratings for appearances not existing anymore. This is definitely a QoL feature. :) Please create an issue for this feature if you like it.