> The issue with the comet zap not caring what order you type in is because it was a > quick hack to the add_comet function... basically I add 1 comet per letter in the > word, and the rest of the code doesn't know there is a connection between them. > This can be solved (in much the same way we solved it in in Casacde), but it hasn't > been high on the priority list thus far :) > > It is definitely something to fix before 2.0
I figured as much. No worries. > Also, we readded the -d or --debug mode to the stuff (like you used to do Sam :) ) > > So running in that mode will print MUCH more! I would be very interested in > crashes, since I am to a pointer where on PPC Linux, x86 Linux and windows (every > once in a while) I don't see any... but that doesn't mean anything :) Yes, as it stands right now, it prints no usefull debugging information under windows (even when run with -d), and it does crash a lot (at least under my XP install at work). The segfault seems to occur all over the place. I've included some of my stderr.txt files with tuxtype -d output to show you where the segfaults are occuring: http://raman.physics.arizona.edu/screens/tuxtype/errs/ As you can see, there doesn't seem to be much of a consistent patern. -- Sam Hart University/Work addr. <[EMAIL PROTECTED]> Personal addr. <[EMAIL PROTECTED]> Alternative <[EMAIL PROTECTED]> end _______________________________________________ Tuxtype-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxtype-dev
