On 2013-09-06, stas poritskiy wrote:
> I am working on application. App is processing a list of files
> in folders. Folders act as a NEW-LOOP. so if all files in one
> folder had been worked on, file is then saved and next folder
> is picked up. it works fine only if i have a SINGLE folder,
> howe
Guys, as i was writing a very detailed message with code samples, following the
guide that Steven linked, i found the problem. a pretty lame one, actually.
in my class that was processing the images, i created an object instance, via
__INIT__ , self.data = attributes()
but i was iterating throug
On 9/6/2013 1:05 PM, stas poritskiy wrote:
The code in development is mine, and i am using the API provided by a main
developer.
At the moment, i am not using any try/except functionality.
here is the full Exception output:
[CODE]
Exception in Tkinter callback
Traceback (most recent call last)
The code in development is mine, and i am using the API provided by a main
developer.
At the moment, i am not using any try/except functionality.
here is the full Exception output:
[CODE]
Exception in Tkinter callback
Traceback (most recent call last):
File "C:\Python27\32bit\lib\lib-tk\Tkint
hey guys,
I am working on application. App is processing a list of files in folders.
Folders act as a NEW-LOOP. so if all files in one folder had been worked on,
file is then saved and next folder is picked up.
it works fine only if i have a SINGLE folder, however, when another folder is
there, i
On Fri, 06 Sep 2013 08:00:13 -0700, stas poritskiy wrote:
> hey guys,
> I am working on application. App is processing a list of files in
> folders. Folders act as a NEW-LOOP. so if all files in one folder had
> been worked on, file is then saved and next folder is picked up. it
> works fine only
