Hey, I asked a few times in Synchronet IRC, but I do believe that people wereãtoo busy for quasi-synchronous communication at the time, so I figured I'd postãhere a little bit about it.ã I'm still working on development of the same shell that I was previously. ãThe last real step I need to finish before I roll it out for alpha/beta peopleãto start peeking at is being able to let them switch back from that shell toãsomething else when they find areas that it's helplessly broken, and when theyãwant to access functionality that I simply don't have coded in yet...ã So I started using bbs.select_shell(). Now I just realized that part of theãproblem might be that I'm currently debugging it as a door, and not as a shell,ãso let me know if that's my primary fubar and I'll just shut up and slink away.ã*grin*ã Anyway, I realized that after pulling up the correct routine for selecting aãnew shell, I'm still stuck in my code. Is that something where I need toãactively search out the shell that I've switched to, clean up my shell'sãenvironment, and jump to that code? The other 'shell' methods that I've seenãdon't seem to have anything to do with activating a new shell. I just don'tãwant users to have to log out and log back in in order to get to the new shell.ã Like I said, I'm having an inkling now that this might just be due to theãfact that I'm debugging it as a door; if so, sorry to waste your time, but feelãfree to poke fun of me a bit! :)ãã---ã þ Synchronet þ Tinfoil Tetrahedron BBS
telnet://tinfoil.synchro.netã