You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If directories typed into "Pictures Folder" and "GPS File" boxes (rather
then using buttons to set these) nothing happens.
only Beginning synchronization with UTC Offset =-4 hours and maximum time
difference = 120 seconds. is printed
What steps will reproduce the problem?
1. Type in directory name in the "Pictures Folder" box
2. Type in full path to file in the "GPS file" box
3. Hit "Synchronize"
What is the expected output? What do you see instead?
Output is only "Beginning synchronization with UTC Offset =-4 hours and
maximum time difference = 120 seconds."
What version of the product are you using? On what operating system?
Windows XP SP2, GPicSync .93
Please provide any additional information below.
If I do the above and then use the buttons next to the file location boxes
to select the directory and the box, then the text in the boxes do not
change at all, but it works.
Original issue reported on code.google.com by gabewe...@gmail.com on 17 Jun 2007 at 4:00
The text was updated successfully, but these errors were encountered:
Hello and thanks for your feedback.
What you've described is not the same as issue 1 which was abut parsing the gpx
file
(which is solved now) but it looks the same.
The two fields (in front of "Pictures folder" and "GPS file" buttons) are just
there
for feedback and you must select them through the dedicated buttons. I prefer
to do
it this way so I'm sure that they are valid paths.
Also if you look at a newer version (last version is 1.04) you'll see that
there is
a "quit and save settings" so next time you launch GPicync he will remenber the last
folder or gpx files (when you use the corresponding buttons).
Thanks again for your feedback, I'll add a warning message for the app.
francois
Original comment by francois...@gmail.com on 17 Jun 2007 at 6:57
Original issue reported on code.google.com by
gabewe...@gmail.com
on 17 Jun 2007 at 4:00The text was updated successfully, but these errors were encountered: