![Smile :)](./images/smilies/icon_e_smile.gif)
(Friday afternoon, he just told me he was bored and wanted to have a look at my branch, and when i came back one Monday, it was nearly finished^^ Anyway, that's great, because it's exam time for me!)
Sounds like some unnecessary work right now, until I got it working. (The same with scripts, actually)Then I suggest to unify use and equip. Implement use functions in equippable classes and return an equip action.
Okay. So make make that a separate task then.Sounds like some unnecessary work right now, until I got it working. (The same with scripts, actually)
But wouldn't that issue still be existent, when you move an item from your inventory into a container and back?Zini wrote:That is problematic at best. Even without the problem you mentioned, your approach will get you into trouble with script execution sooner or later (there might be scripts running on the object in the store and when you move it to a different store and then back, it won't be the same object anymore).
That went even faster than I expected. I finished the task and merged into master. Please merge my master into your inventoryGUI branch and see if you can do anything with it (2 new functions in MWWorld::Class).Zini wrote:btw. I just started working on container capacity (should be finished soon).
I think that needs to be considered for the UI too. First you need to adjust the encumbrance bar. And then you have to reject drags into containers (but not player inventory) that exceed the capacity limit.