2011-09-19, 15:42
MariusTh86 Wrote:When going to a next or previous item, it does save the data, it just doesn't update the list, and I realize now that if you press cancel on the next item, it still won't update the list since I only thought of doing this while saving an item..
I'm planning on making a method to update a list item instead of the entire list, but until then it'll either have to repopulate the list even when nothing has changed, or live with the current condition until I've made this method.
Gotcha. I must have not updated the list then. I think maybe I just clicked PREV after clicking NEXT and it wasn't updated. I'll mess around with that more, but it sounds like maybe it does work how I expected then. Just obviously not refreshing when clicking cancel (which is technically what I would expect as well).
In the interest of not having a lot of automatic refreshes (in the interest of speed, that is), perhaps an indicator that the program changed something and a refresh would be a good idea. Then the user could click reload, or keep performing their changes and know to click reload later. That should keep performance up until you can create a routine to just update single items (and potentially resort the list). Basically it would load NFO info on startup and then only when you clicked reload.
Any thoughts on the list not sorting by sort title? Or am I just doing something wrong?