Duplicate Signature ID - Issue #233

Issue #249 resolved
Pezz created an issue

Issue 233 still not resolved.

Creating a new bug as I can't reopen the old one.

Comments (14)

  1. Pezz reporter

    Hey mate,

    I'm not sure, just by going on what your forum post has said, that this fixes the issue.

    Bug 233 was about when you have, say, ABC-123 and ABC-456 sigs in a system and there is no way to record them (nothing to do with EVE Scout really).

    Am I mis-reading what you've said on the forums?

    Cheers.

  2. Andrew Clark

    Does this happen in game, multiple sigs with the same 3 letter prefix?

    As far as I'm aware every mapping software I've used assumes that this is not the case?

  3. Pezz reporter

    If it wasn't a problem, why do ya reckon a bug was opened, then re-opened, then re-opened again?

  4. Andrew Clark

    You make a fair point. Just strikes me as quite an odd assumption for every mapping tool to make given that this can/does happen. Have you any suggestions for how you'd like a fix to work?

    Full "abc-123" style sig references for all? Full references only when a duplicate is detected? Or have you something else in mind?

    I'm more than happy to work on a solution for you.

  5. Pezz reporter

    Just provide an option to record ABC-123 and ABC-456...

    It doesn't happen that often, but when it does it screws up copy + paste which TW can't currently handle.

  6. Andrew Clark

    Ok leave it with me I'll take a look. Not sure of timescale, it's core functionality that needs to be modified!

  7. Josh Glassmaker repo owner

    BM field is going to be the new class and type auto naming feature. Its all just concept still so thats why its just a text field. It will hopefully work by setting up a format like C{wormhole-class} - {jumps-from-home} with the ability to set that different for both directions so any EVE bookmark naming convention can be accommodated.

  8. Log in to comment