Go to timestamp is a great feature however it needs to be improved slightly to allow users to have a benefit of that.
1) It expects time to be in a different format from time displayed in logs (expects 14:33:46,295, but in logs 14:33:46.295 - comma vs dot) which means user cannot paste here value he saved earlier
2) It jumps to EXACT time and if EXACT time not found in logs it just does nothing, it would be great if in that case it would jump log entry with closes time
3) Elements in To to Timestamp dialog are ordered other way around (e.g. pressing Tab key at Date box focus moved on Cancel button instead of Time box)
The behaivor you advice is the one we implemented. For me Log4View jumps to the closest log entry if there is none matching the time stamp exactly. If the time stamp is too high/low for any message, Log4View jumps to the last/first message. Please note that also the date is used to find the nearest message. Could you send us your logfile and timestamp that is not working?
Regarding 1 and 3)
We just released a new version 12.5.9 with the timestamp dialog fixed.