Closed GoogleCodeExporter closed 9 years ago
Original comment by netpr...@gmail.com
on 30 Oct 2010 at 5:33
I've been thinking about the same thing and came here to suggest this idea. I
do realize that the algorithm runs through a lot of build orders, so keeping
all of them might not be practical. At the same time I feel that storing last 5
or 10 build orders would be very helpful. Especially in cases when a
sub-optimal solution (maybe a couple of seconds longer) can give you more
drones or is simpler to execute.
As far as the UI goes, I imagine a slider representing the time the build order
takes to execute, with the current one (the best so far) at the left. To the
right of that one there would be ticks representing other, suboptimal BOs that
were found before (5 or 10 max).
An ASCII mock-up might illustrate this as follows:
#-----#-#-------------#----------#
1 2 3 4 5
1: 4.31
2: 4.37
3: 4.38
4: 4.59
5: 5.10
Original comment by smalolep...@gmail.com
on 30 Oct 2010 at 5:40
Original comment by Frit...@gmail.com
on 3 Nov 2010 at 6:43
Original comment by Frit...@gmail.com
on 6 Nov 2010 at 1:20
Original issue reported on code.google.com by
nctoy...@gmail.com
on 30 Oct 2010 at 4:26