I am finding that the "request constructor" option is going to be a big help as soon as I get used to it.   It's one of those things that I have to get used to after doing it all manually for so long.  It isn't perfect by any means, still seems to call a constructor from a distance at times.   I have three suggestions, I don't claim they are necessarily original as there have been many threads on constructors and I may have missed something.

1.   When I click the "upgrade starbase" button, I would like to see a list of colonies in range.   Further data might be helpful, but I am now using a colony naming system that makes this moot (i.e.  append OR prepend a letter telling the SB's specialty (R, M, $, I, or X for non specialized).   So if I could see what starbases are in range I wouldn't have to click done and check the vicinity, check the colony(s)  and then go back.  This doesn't seem difficult as the program must already know this.

2. The upper right display(s) for constructor requests should adjust if I happen to manually divert a constructor from one job to another.   Say the display says a constructor is requested, but I divert another for whatever reason and thus the display now shows 1 en route and 1 requested.    This should be adjusted to 1 and 0.  Likewise if I manually take a constructor off an indicated route the original starbase should now show 1 requested instead of 1 en route, and so forth.    This seems a bit more complicated, however the basic mechanism seems to already be in place with the request constructor button itself.

3.  There should be a way to cancel requests if I change my mind or make a mistake (it's rare but has been known to happen).   

Just some ideas, like to hear some feedback or other ideas.

If someone knows how to do some of this already and I just don't see it, please inform!