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
Just got a Thumby for Christmas and have been having lots of fun with it!
I've been making a lot of separate sprite files, and it looks like even with the "Emulator" option checked in the file, the emulator starts losing track of them. I'm not sure if there's a pattern to which files fall out of its sight first. When I click the "files" button in the emulator widget, all of my files are listed.
sample stack trace (it's just behaving the same as if the sprite file doesn't exist/doesn't have the emulator checkbox ticked)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Games/LilBuddy/LilBuddy.py", line 118, in <module>
File "/Games/LilBuddy/LilBuddy.py", line 28, in __init__
File "/Games/LilBuddy/LilBuddy.py", line 115, in reset
File "/Games/LilBuddy/Form.py", line 155, in __init__
OSError: [Errno 2] ENOENT```
I have 16 files showing in the file list, and 13 of them are .bin sprite files. Unchecking the "Emulator" checkbox for a file (that isn't called until later in the program) gets it past the error above.
My program runs fine when pushed to the Thumby :)
The text was updated successfully, but these errors were encountered:
Just got a Thumby for Christmas and have been having lots of fun with it!
I've been making a lot of separate sprite files, and it looks like even with the "Emulator" option checked in the file, the emulator starts losing track of them. I'm not sure if there's a pattern to which files fall out of its sight first. When I click the "files" button in the emulator widget, all of my files are listed.
sample stack trace (it's just behaving the same as if the sprite file doesn't exist/doesn't have the emulator checkbox ticked)
The text was updated successfully, but these errors were encountered: