|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Fri Dec 17, 2010 7:50 pm
MXP Bug and child windows |
This has happened for all versions that I can think of, and I /think/ I may have posted it before.
When capturing something to a child window that contains <> tags, it will sometimes double up the <> tag.
For instance:
[Newbie] Charneus: Try using 'help search <phrase>' to find your answer.
becomes
[Newbie] Charneus: Try using 'help search <phrase><phrase>' to find your answer.
It's not doubling on input, but just the output, and it's only shown in the child window.
I realize I could turn off mxp altogether, but I do use it for the clickable links. |
|
|
|
MattLofton GURU
Joined: 23 Dec 2000 Posts: 4834 Location: USA
|
Posted: Fri Dec 17, 2010 8:36 pm |
Are you using #CAPTURE, or does it also happen with other methods? I've never seen such an issue with #WINDOW, which I use almost exclusively since I'm rearranging or otherwise doing something preparatory with the original data.
|
|
_________________ EDIT: I didn't like my old signature |
|
|
|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Fri Dec 17, 2010 9:00 pm |
I do use capture, yes, just for the color purposes. Probably should have mentioned that. I'm going to work on a way to produce it offline, just haven't had time to do that yet. Wanted to get the post out in case someone else experiences it.
Edit: I realize I actually use #WIN, not #CAP... silly me. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sun Dec 19, 2010 10:35 pm |
Does this get fixed if you turn off the Capture MXP option for the child window?
|
|
|
|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Mon Dec 20, 2010 8:34 pm |
It does not get fixed unchecking Capture MXP. Here's the procedure to reproduce this.
1. Open up an untitled session.
2. #WIN Test Set MXP preferences for this window to show unknown tags.
3. #TRIGGER {Test: (*)} {#WIN Test %1}
4. #SAY {Test: This is a <test>.}
Note how the <test> isn't doubled.
5. #SAY {Test: This is a <test> for <MXP>}
Notice how the <test> is now doubled and <MXP> isn't.
6. #SAY {Test: This is a <test> for <MXP> for <duplicates>.}
Notice now how MXP is doubled as well, but shows up in the middle of <test>? The deeper you go, the more it shows up. |
|
|
|
Tech GURU
Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Tue Dec 21, 2010 4:57 am |
Confirmed.
|
|
_________________ Asati di tempari! |
|
|
|
charneus Wizard
Joined: 19 Jun 2005 Posts: 1876 Location: California
|
Posted: Tue Jan 04, 2011 9:27 am |
Wonder if this is an easy fix...
|
|
|
|
|
|