2006 Compo Comments

Oh, sorry, I thought you were the one who made the ZTiles game. Sorry!

Yeah, I really like Sudoku, but I would rather play the puzzles by hand, rather than using a computer of some sort to solve them. I use my own "style" for figuring out which numbers go where, involving circles, dots, and lines. Yes, crazy, but it makes the puzzles really easy.

About the votes. Personally, I don't like votes since they imply syntethizing complex judgements into mere numbers, which is actually impossible, at least in theory. Unfortunately votes are sometimes necessary.

Anyway, we have no problem in sending votes via PM to compo participants wanting to see them. They're absolutely not a secret, I consider it kind of an etiquette issue.

I got the prizes! they will be sent out as soon as possible!

can i ask what bugs you are refering to?
with the fact i can't test on hardware, so excluding specific to that issue, the only bugs i noticed was todo with the sub directory's (affect GBA version too)
one was a minor error - lead to occasional displaying a blank window and probably a system crash (reading a non-directory area)
second was a substantial error logic code wise on windows, leading to back tracking directory structures not fully working properly - a virtual drive issue

btw DeSmuMe runs the latest quite nicely

The demo we tried could only open one level of subdirectories. Trying to descend to lower subdirs made some data (?) appear on the screen outside the app's window and nothing happened.

This is classifiable as a major bug since it implies a lack of functionality on the fundamental job of the software: browsing directories. :-/

ah well, i class major bugs as being major problem in the code, that was just the wrong reference on one line, the numbers appearing outside the window... um, not a bug, debug info that was't disabled
with that line fixed and the re-construction of the code creating the virtual drive, its working properly

From wikipedia:

In software engineering the gravity of a bug is ranked according to its consequences in the program functionality. If a trivial typo in the code triggers a system crash, than it is considered a major bug.

Conversely, if you have a software whose code is completely messed up, producing a hell of redundant computations, but it presents no flow in the software functionalities, it is said to be bugfree.

lol, thats the trouble with definitions - done from a user perspective
i mean a "trivial bug could have little immediate effect, but cause a casecade effect of massive bug proportions later in time
a "major" bug could have immediate clear effect but little real effect, outside that effected bit
a system infected with "minor" bugs is windows

but still if its only the sub-directory issue meantioned, then that should be fixed and i'll work more after i get a php script done up for a compo i'm handling - for those who may interested in my little filer app, so they know its not dead

We'll be very happy to see further improvements of your app.

Indeed we are.

If you had HW, you could use (the upcoming) v1.2 ang a CF I/O compatible device for that, and save me the job :3

excuse me their be a new coding compo for 2006?

Who knows? It is not currently scheduled.