On Mar 25, 2006, at 1:03 AM, Jeffrey Ellis wrote:
After seeing that the app was behaving as expecting, I started a
more robust
test. Instead of using the same set of 7 missing files in the Target
location that I had been testing with, I tried removing ten additional
files, by deleting the files, which were in sequential order when
sorted by
Name, from the Target. Now, although the folder had not changed in
any other
way from the number or names of files remaining, the same file set
that all
previous tests were run on (i.e., no new files had been added to the
existing structure), I started to get a bunch of nilObjects as
items were
added to the Target listbox. I looked at the filenames causing the
nilObjects, but those same files had been tested for a week, in
both Source
and Target locations.
Does the strange behavior happen if you restart the app for the
second run. The symptoms you are describing sound like symptoms of
failing to reinitialize variables, although I'm just guessing. You
should be able to at least track down where and why the nilObject
occurs using the debugger. Then if you don't understand that part of
the code, post it to the list and I'm sure someone will be able to
help you. That would be better than simply asking the list to debug
your app for you.
Regards,
Kevin
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
