like "Error in the input data, trying to parse the file anyway") that the program knows something is wrong with the input data, so the user knows it is not the program itself. So my suggestion is - give some user feedback (alert box, message in the status bar. This software (RouteConveter) did not produce any error, or other visible user feedback than a broken output, so my first thought was b) - either code wise (wrong parsing), or UX wise - no user feedback, that something went wrong while processing the data. I used this file in different programs and online tools before in search of a fitting tool, I did surprisingly not ran into this problem (means the other programs are less strict/accurate with parsing - a decision in design). When something in software is visibly broken it let me, as a tech person, interpret it in 2 ways:.Yes, the first thing I did when finding that bug.Test file with the correct version: test_1_1.gpx.txt Test file with the wrong version: test_1_0.gpx.txt There is no user feedback like "cannot import file / wrong format / error in format". IOException: Server returned HTTP response code: 400 for URL: http: //To me it seems that it does not remove the " at the end when parsing the URL, which would explain the 400 response.įurther the program tries to interpret (wanted behavior?) the file and the result is some garbage: NavigationFormatParser internalRead SEVERE: Error reading with slash. NavigationFormatParser$InternalParserContext parse INFO: Reading '"' with a buffer of 1048576 bytes 4: 11: 24 PM slash. Expected elements are 4: 11: 23 PM slash. UnmarshalException: unexpected element ( uri: "", local: "gpx"). Expected elements are 4: 11: 22 PM slash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |