Subj : bullseye.js PATCH
To : Digital Man
From : Delbert
Date : Thu Aug 16 2007 04:11 pm
Re: bullseye.js PATCH
By: Digital Man to Delbert on Thu Aug 16 2007 11:44:00
> It's working here on Vertrauen just fine. Are you actually having a problem?
Yes, after installing the fix, it looks like it's working at first, but
actually it only displays the first menu you select. IOW, you pick #3, read it,
go back to menu and pick #1, and it just shoes you #3 again, until you exit
bullseye, and rerun it.
Whatever the first choice is gets a file descripter in typeasc.js, and
subsequent menu choices fail the if test so the new filename doesn't get a new
fd after that.
That, and the "i" from bullseye.js gets changed to a 0 in typeasc.js when
implictly defined in the while(). Using load() puts both "i"s into the same
scope because neither is in a function or anything... changing the "i" in
typeasc.js to a "j" fixes that. You can see this in the log when it shows that
the user chose #1, no matter what they really chose. The #1 is "i" after being
made a 0 and then going through the while loop in typeasc.js once.
The diff I sent you illustrates this, I think.
Rob, the diffs I send are more to illustrate the problem than they are to
represent replacement code. That's all I meant when I said you'd probably want
to code the real fix your own way. ;) (I put the darn smily thing on there;)
To duplicate this bug, tail the log, go to bullseye.js, select #4, read it,
then return to the menu and select anything but #4. You will get #4 again, adn
the log will say you looked at #1 both times.
You're sure you're not using bullseye.bin? ;)
-j-
---
� Synchronet � Delbert's Place BBS | telnet://delberts.audizar.com
