search

OutpostUniverse / NetFixClient

Outpost 2 networking client module
0 stars 0 forks source link

Handling ServerAddress default and saved values #125

Open Brett208 opened 4 years ago

Brett208 commented 4 years ago

I have been doing a bit of use testing with NetFix lately.

I tend to find the Server Address Combo Box difficult to use reason with as a user due to how many varied settings it allows. Below are some thoughts, some of which I think might improve the situation some, but not sure any of it is the best idea.

  1. The .ini file contains what we want the default value to be, but it will set the last provided value as default. Perhaps it would be better to default to no selected value so the .ini file is used.

  2. The user values are saved over time. But these values are combined with the TCP/IP values. So now when I want to create a TCP/IP game, I have outpost2.net as a choice, which doesn't make sense. Perhaps the saved lists of IP addresses should be separate between TCP/IP and NetFix?

  3. Maybe NetFix shouldn't save a list of previously used addresses. Users may usually want to use the default .ini setting anyways outside of troubleshooting.

Maybe a better UI would be to add a use custom IP address check box and disable the combo box unless this is checked?

Maybe even better if you could use a control to specify between looking for the server vs a host Outpost2 copy.

DanRStevens commented 4 years ago

Hmm, some interesting ideas there. You're probably right about the ini file.

This makes me think about the evolution of NetFix, and why it's the way it is. It was built with an evolving set of design criteria. I'm wondering if writing a bit about the history of NetFix would help, along with what the issues were, and what problem was solved each step of the way. That might give a better sense as to why things are the way they are, and what concerns still need to be addressed if things are modified, or what concerns are obsolete and no longer need to affect the design.