You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if it's best to have a panel or button to toggle the view. The default ship Category listing is quite large to begin with and I think being able to hide this might be a good idea.
Additionally, we don't ahve any way of pulling back recently changed fits. We don't have a modified timestamp on fits, nor a last opened timestamp. We only have a created timestamp, which I don't believe works well with this.
The text was updated successfully, but these errors were encountered:
Conflicts:
eos/db/saveddata/character.py
eos/db/saveddata/fit.py
Implements pyfa-org#983 but utilizing sqlalchemy events to update the fit modified date whenever something is added/changed.
This has been released. :D Any fitting change (adding/removing modules, drones, projected and command fits, or modifying modules by adding charges, changing state, etc) should update the fit's modified date in the database
A note for mac-deprecated users:
Recent fits will only show the most recently created fits, or most recent fits that had their name / character / notes / (whatever data is stored as the fit record in the database) changed. This is due to a limitation in sqlalchemy v0.6, which the mac-deprecated build uses, specifically with respect to the lack of events. For those still on the deprecated version, try out the non-deprecated version - if there's any issues, please let me know through an existing issue or open a new one :)
see #982 (comment)
I don't know if it's best to have a panel or button to toggle the view. The default ship Category listing is quite large to begin with and I think being able to hide this might be a good idea.
Additionally, we don't ahve any way of pulling back recently changed fits. We don't have a modified timestamp on fits, nor a last opened timestamp. We only have a created timestamp, which I don't believe works well with this.
The text was updated successfully, but these errors were encountered: