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ã