-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] Add anoms with bulk import #242
Comments
Would it be more usefull if signatures page would have summary:
Personally I don't see point of addind this to info page. Though system popup could contain info "SIGS: 16, ANOMS: 15, POS: 3, PILOTS: 5" |
I was thinking of such a feature for the system popup too, seeing a summary per sig categories may be nice. |
I'd be pretty indifferent as to where exactly that information would be displayed. It's just very nice to see at first glance which and how many anoms are in a system. At the moment, either no information is added to the mapper, it's old or it doesn't have a date (or some weird date formatting :P). |
So is your ptoblem that anomalies are not listed in the signatures page? Did you copy and paste them from the scanner window? |
Okay, I've just realized that if you bulk import combat/ore anoms they get listed with the anomalies. I think this https://i.imgur.com/vHDro0c.png could be solved better. I know there are 25 combat anoms in Bacon but I have no idea how recent that information is. If people enter the number of anomalies at all. |
Currently you can find the information by hovering over signature/anomaly on signatures page. Though I agree something should be done on this area. ews could even check what data/relic sites are combat sigs and then report somewhere "combats: 10+4" where 10 is combat anomalies and 4 are combat data and relics. We need to keep in mind that people live also in systems that have null data and relic sites ;) |
It'd be nice if the bulk import feature would also add the number, type and date of anoms instead of people having to write that into the info field by hand, which many don't do.
The text was updated successfully, but these errors were encountered: