Menu
▾
▴
1 Attachments
#3113 Tapping movement twice too quickly throws a "Server cannot do that" error
Exactly what the title implies... FreeCol.log attached.
I:
1: Moved my ship to Europe
2: Tapped it again before the dialog triggered
3: Selected the option to send the ship to Europe
4: Error visually behind the "go to Europe" dialog box appears
Agreed this can happen. You sent two commands to the server before the first one had been fully processed by the client. To fix this we would have lock out the keyboard until a command is fully processed. I am unconvinced that is the right thing to do.
"4. error visually behind" is probably due to the known common problem with windows on MS Windows.
Mike, maybe server could give a different error if exact same command is executed twice ?
We regularly validly execute the same command in succession (e.g. move unit in same direction), so this will be difficult to distinguish in general. We could add a sequence number to each command, or do some tricky stuff with timestamping. Any solution will just slow the server down further... which is the reason this problem occured in the first place.
Ironically, this is only a problem because the server is dutifully reporting all errors.
Agreed that the "go behind" effect is a known Windows-Java weirdness that awaits a fix from a windows user.
Following up, I checked the log file. It contains an crash that was fixed a while ago, but I doubt it was related to the problem here. So, we are in the difficult position here that the problem is real, but I am struggling to think of a way to deal with it.
No further signal on this, time to close.