Also, although we should perhaps make some attempt to ensure the decimal
separator is always a full-stop... it turns out edsy.org doesn't
currently support importing this style anyway, so it's moot.
Despite it being unused I restored the `logfile` argument to
`Dashboard.process()`. It's set in a call to it. Further investigation
if/when we do a proper code cleanup.
* Ignore types on the darwin stuff in-class if from platform specific
imports.
* None of the HotkeyMgr __init__ methods take any args, so don't try to
pass any through. Stops mypy complaints.
Whenever A_D does a PR the checks, for some unclear reason, also contain
'other' files causing unexpected flake8 output.
i.e. PR that changes only plugins/inara.py somehow "git diff .. | flake8"
such that flake8 complains about things in collate.py, coriolis.py,
loadout.py
Sure the `for k, v in ...` means not sending any that are empty/none,
but it will still send the event, just with *no* reputations.
When you're on a fresh character you have no reputations yet, so avoid
causing an Inara API error, including status line text.
Close#581
This at least ensures we're correct after logging back in at a station.
If you relog whilst out at a Settlement then counts will definitely be
wrong now. But there are no events for using consumables, or picking
anything up anyway, so it's almost always going to be off there.
This has an array 'Offered' listing what was traded away.
'Category' & 'Received' is what you got in return, 'Count' many.
Again, we assume this only interacts with ShipLocker, not BackPack.
These are being sold to a Bar Tender.
There's a MicroResources array, one per item name. We assume this is
always selling from ShipLocker, not BackPack.
This is currently only when buying Consumables from a Pioneer Supplies
vendor.
One event per Item type, it's not an array.
We're assuming these go into ShipLocker, not BackPack.
It's unclear from my Journals if this is adding to the current or is the
total state at the time. I think it's the latter, despite not finding
where a '737844537' had come from (looks like from a mission, but that
would be reward and should have gone straight to ShipLocker?).
