Automated System Naming, Displaying Region, and distance to nearest trade hub on system nameplate

[Meekss]

I couldnt find where to submit suggestions so ill put it here.

• Set it so the region for K-space systems is always displayed under the system name.
• Integrate an auto naming system like Vippy has.
• Display the distance to the nearest trade hub on the System nameplate.
• Ability to update who the current inhabitant of a Hole is. (In vippy you can update who lives in a hole and that information will be used univerally with anyone else using vippy thus creating a database of what corps are active in what hole, That information is then displayed on the nameplate for the system)
  These four features are the main things that are keeping my corp from switching to pathfinder.

Here is a screen shot of what i am talking about. You can see how the Mapper gives a name to the next hole of that type alphabetically. That makes is easier to tell others where you are or where you are going and makes for much easier bookmark tracking in game.

I understand that this information is available with a click or a scroll in pathfinder but we would like it so its something that could be seen at a glance without having to interactive with the map at all(Thus everything displayed on the nameplate). Even if this was something that could be permanently toggled on or off it would be great. Thanks for reading.

[WildStrawberryEVE]

1. 
   You have that functionality - just need to hover over the button and it shows regions for all systems on the map.
2. I think there was an issue about that already and the conclusion was that there are many different naming conventions for chains and it's impossible to make everyone happy.
3. It's already crowded with numbers and buttons in system's rectangle. You have that functionality here:
   
   Together with options for safer and shorter distance.
   When living in WH do you really feel the urge to visit Jita so often that you need some extra enchancements for that?
4. Again - it's too crowded in system rectangle for such detailed info IMHO.
   Plus you have that functionality via system description panel and in intel window where you can input citadels info:
   
   

Personally I think that all the functionality you mentioned is already in PF with no special need of doubling it.

Maybe PF should be made in a way that makes modding easier, dunno, there were attempts to mod it which went quite well.

IMHO Vippy looks ugly and systems are huge. How many you can fit on the screen? 10, 20?
With big chains you would need 50 inches screen with some 8k resolution to fit all that information you would like to have ;)

I think that if PF ever needs to have more info attached to system rectangles, it should be done via hover over/switch buttons in top right button panel.

[Meekss]

As i said already I understand these features are a part of pathfinder the point is to make the intel visible at a glance, Hence in the systems Rectangle, Having to mouse over or click a system and scroll down every time you need basic info is annoying and slow. Im not saying this has to be the default but having the ability of toggle these options would be great.

[exodus4d]

Thanks for your suggestions @Meekss :)
@WildStrawberryEVE is right, most of the features are already there. I´m always up for UI improvements and reduce the required clicks for users to show them the information they need.
But, as he said, moving more information into the map view requires good arguments for it. If an information is just 1 click off (e.g. region names) I don´t see the point moving it into the map view and make is always accessible even if it not used that often.

Also see this Issue for "auto system aliases" #360

Nether the less, there is a feature requests I like:

Save inhabitants to a system would be a nice addition to the "Intel/structure" panel. (Not sure about the "auto share" feature for that information. I´m sure some groups don´t want to share their intel with others)

Please keep in mind, that Issues like this, are very unhandy. Throwing multiple feature requests in one Issue is a bad practice. - So people can discuss on a single topic/feature. That´s why I have to close this one. Feel free to create new issues with the features you really need.