Zugg Software :: View topic - [1.34] Channel capture to child window; disappearing command line

Posted: Sun Jul 01, 2007 5:24 am

I have a window that I capture dialogue from channels to. The script for this is simple, and goes something like:

#CLASS ChanCap 1
#TR {~(%w~):} {#CLASS Cap 1 ; #CAPTURE ChatAetolia}
#CLASS 0

#CLASS Cap 1
#TR {H:} {#CLASS Cap 0} {prompt|nocr}
#TR {*} {#CAPTURE ChatAetolia}
#CLASS 0

It works fine, except that when a line is captured to this window, the contents of the command line disappears. Or rather, is made invisible. It is still there, and if I left/right arrow, type more, hit enter etc, it becomes visible again. Its disconcerting though, especially when typing up something with a bit of length.

P.S. Is there a way to export/view scripts in the above text style format? I know that for sharing scripts we have the package library, and xml.. but for displaying scripting on forums we only have the old format we know, and having to type the whole thing out by hand is pretty annoying. Not to mention easy to make mistakes with.

Posted: Mon Jul 02, 2007 5:25 pm

Nope, there isn't any class-script in CMUD yet. And when I add class scripts, it will use the new human-readable XML format and not this zScript text format. There are too many new features being added to CMUD that don't work very well with the text format above.

In any case, can you show some sample text that you are using to fire your trigger? I tried playing with the above triggers myself and I couldn't get it to fail. Text was captured to the ChatAetolia window, but my main command line was fine.

Maybe you have a corrupted layout file? Try holding the Shift key when you click on the Connect or Offline actions to load your session and create a new default layout file and see if that helps.

Posted: Mon Jul 02, 2007 6:12 pm

I saw this invisible command line text resurface again recently too.. It was gone for a while, but now it's back. I didn't know it was the #CAP that did it, but I also use that and have the problem so it's as good a bet as any.

There's a more readable and functional XML export on the list but it's not done yet. Might be one of those that make it to version 2.0.

Posted: Mon Jul 02, 2007 6:17 pm

I'm excited about the more readable and functional XML export coming! So much so that I thought I'd post about it.

Posted: Tue Jul 03, 2007 8:35 am

Sample input:
(Web): Borscin says, "Modded it so it'd be faster."

I'll play around with it later. I'll have to create a completely new session though. So far every time I've done anything even slightly out of the ordinary with creating new windows, I've ended up having to start afresh and recreate my session, adding the packages one-by-one etc. I have it stable at the moment and I don't want to touch it >.>

It could be the layout file. It doesn't seem to like me much at all.. its always talking back to me, so to speak. My layout, that is.

Posted: Tue Jul 03, 2007 12:18 pm

Define "slightly out of the ordinary", that might help :)

Posted: Tue Jul 03, 2007 5:05 pm

It's probably not the *.XLY layout file, but it might be the *.TBZ toolbar file. Holding down the shift key tells CMUD to recreate both files. The XLY window docking layout file seems pretty stable these days. But the *.TBZ toolbar file is more complicated and the DevExpress toolbar system has more problems with all of the dynamically created elements that CMUD uses. If the command line toolbar gets associated with the wrong toolbar handler, then it can disappear.

Also, anything that resizes the window to cause it to be smaller can also cause a problem like this. The DevExpress toolbar "wraps" it's items, and so you can end up with a case where you only see the icons (parse, etc) but the actual command line has been "wrapped" and is not visible. So also let us know if these icons are visible, or if it's the entire command line that is gone. Maybe a screen shot would help.