Bug Stomp

Explorer for OS X is awful with the hanging. I cant use it here.

As for the double-message error, I've tried and tried to fix that but to no avail. The right frame sometimes stopped reloading, so I cant have it based solely on that. It really should not be happening, but it still finds a way to do so. I'll give it another go, but not before doing something more fun.

By all means prof, concentrate on the fun stuff! I figured those double pop-ups were somehow related to those everlasting browser idiosyncrasies... especially if you've already wasted energy on 'em. There no biggy anywayz.

I just got an idea though prof! How about if you keep the pop-up JavaScript in the right frame and then just get that frame to reload when you submit a chat message. If it had by chance stopped reloading, submitting the chat message would then get it going again. Just a thought though, I wouldn't be surprised if you've tried that already too.

That could work. When I jump on that one, I'll give it a try.

Any time I try to move to another page in a forum I get logged out.

My bot won't use his Seek responses in the x-initiate keyword. (He seems to Seek fine in other key words). It's hard to test because my bot doesn't initiate with me very often. But when he does, I try to trigger the Seek words, and he just ignores them and goes to an x-none response.

I've noticed a similar attitude when watching my bot chat, I often end up dissapointed when I'm expecting my bot to pick up on a seek at the beginning of the conversation...

Me too. Are we learning from our bots?

Rex- what's your browser, version, and OS? Anyone else having the Forum-logout problem?

Seeking in xinitiate... I may have left that out by accident. *time passes* And now it should be working.

I think we are saving multiple versions of the Language Center. I noticed I had both "You're welcome", and "you're welcome" as a response to "Thank you," When I clicked on the context thingy, it came up "Thank you" and "Nada." I said "huh" to myself in true bot wonderment. A third time, it came up "Nada" and "nada". I remember way back there someone said their bot retained old responses and keywords that he had edited out.

I was a little curious about how the system works for removing keywords too. Especially if there's a seek following it. Do we just remove the response, submit and ignore the seeks? or should we delete the seeks first?

Funny you mentioned that, Rahz, as that's precisely the thing I was dealing with tonight. I realized that the deleting procedures sometimes left orphaned Keywords and Context that you couldnt see, but which still affected the Bot's speech. They're all fixed now.

You have to purposely delete things now. If you're doing something wrong, you'll get a pop-up message telling you. You have to remove a Seek from within the Seek, not by deleting the Response that it's hooked to. Keywords still cant be deleted, but they can be changed.