search

dro4dee / gpicsync

Automatically exported from code.google.com/p/gpicsync
Other
0 stars 0 forks source link

Unhandled exception in thread started by <function sync at 0x023D2570> #41

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I try to use it with a folder of Nikon D200 Raw files
2. import the GPS data (NMEA file)
"For information, GPX file created with GPSBabel in your picture folder." 
was prompted on screen
3. When I push Synchronize button, Nothing happens, The message was 
prompted as below:
------

Beginning synchronization with UTC Offset =+8 hours and maximum time 
difference = 300 seconds
Creating an 'originals-backup' folder.
Starting to generate a Google Earth file (doc.kml) in the picture 
folder ... 
(Found DSC_1824.NEF ...

When i quit the program. the message was prompted on windown
Title of message box: "Error occured"
message: See the logfile C:\Program files\GpicSync\gpicssync-GUI.exe.log

I check the log file and content of file as below:
Unhandled exception in thread started by <function sync at 0x023D2570>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x023D3570>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x023D3570>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x023D3570>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x023D3B70>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'

What version of the product are you using? On what operating system?
GpicSync 1.10-2007
OS WinXP sp2

Original issue reported on code.google.com by pchang3...@gmail.com on 4 Aug 2007 at 7:41

GoogleCodeExporter commented 9 years ago 
I have been experiencing exactly the same error.  My error log looks like:

Unhandled exception in thread started by <function sync at 0x01B5BE70>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x01B5BE70>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x01B62B70>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'
Unhandled exception in thread started by <function sync at 0x01B62B70>
Traceback (most recent call last):
  File "gpicsync-GUI.py", line 733, in sync
  File "gpicsync.pyc", line 168, in syncPicture
AttributeError: 'GpicSync' object has no attribute 'shotDateUTC'

Original comment by ach...@gmail.com on 4 Aug 2007 at 3:51

GoogleCodeExporter commented 9 years ago 
other message was found on gpicsync-GUI.exe.log:
wx._core.PyAssertionError: C++ assertion "(size_t)(n) <= length()" failed 
at ..\..\include\wx/string.h(430) in wxStringBase::at(): invalid index in 
wxString

Original comment by pchang3...@gmail.com on 7 Aug 2007 at 1:27

GoogleCodeExporter commented 9 years ago 
Hi pchang3657 (and achorn),

Can you send me for test the traklog file, one or two pictures and the UTC 
value used.

My mail:
http://francois.schnell.free.fr/fschnellgmail.png

Thanks

francois

Original comment by francois...@gmail.com on 12 Aug 2007 at 2:17

GoogleCodeExporter commented 9 years ago

Original comment by francois...@gmail.com on 12 Aug 2007 at 2:17

GoogleCodeExporter commented 9 years ago 
francois.schnell

The jpg file and gps file has been attached (.txt is nmea format)
the size of raw is too large(can't send out)

Patrick

Original comment by pchang3...@gmail.com on 15 Aug 2007 at 12:47

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi Patrick,

You have the good mail address. Maybe your attachment is over 20 Mo (the gmail 
limit
per mail). 

If this is the case you can maybe resize your picture (and still have the same 
error)
and send it to me or put the files somewhere on a web space temporally. 

francois

Original comment by francois...@gmail.com on 17 Aug 2007 at 8:34

GoogleCodeExporter commented 9 years ago 
francois

the mail has been sent  
The jpg file and gps file has been attached (.txt is nmea format)
the size of raw is too large(can't send out)

Patrick

Original comment by pchang3...@gmail.com on 17 Aug 2007 at 2:59

GoogleCodeExporter commented 9 years ago 
Thanks Patrick for sending the data.

Strange, it looks like GPicSync can't work with this UTC value (8) for this
particular time and date  when the option "dates must match" in ON (other UTC 
values
like 7 or 9 work).

I'll investigate this problem a little latter when I'll have some time. In the 
mean
time you can unselect "dates must match" (it works for me).

Thanks

francois

Original comment by francois...@gmail.com on 17 Aug 2007 at 3:25

GoogleCodeExporter commented 9 years ago 
francois-

Has any progress been made on this issue?  I appreciate all of your hard work, 
but I
was having this problem before - achorn from comment 1.

Original comment by ach...@gmail.com on 7 Nov 2007 at 2:18

GoogleCodeExporter commented 9 years ago 
Hello Achorn,

The problem I've seen on my comment 10 has been fixed since version 1.20 (it 
happened
when the tracklog data was crossing UTC=0)
http://code.google.com/p/gpicsync/wiki/ChangeLog

Have you tried again with a recent version of GPicSync?

If you still have a problem with your data can you send me your tracklog and a
picture (and tell me the UTC Offset to use). 

Thanks for your feedback.

francois

Original comment by francois...@gmail.com on 7 Nov 2007 at 12:40

GoogleCodeExporter commented 9 years ago 
francois-

No, I haven't tried it since before version 1.20.  I will be glad to try it 
again now
that I know it has been fixed.  By the way, this is a great piece of software 
(from
my previous testing), and you are doing an excellent job of keeping up to date 
with
the issues and features.  Thank you.

Original comment by ach...@gmail.com on 9 Nov 2007 at 6:02