 |
Xanxis
Newbie
Joined: 07 Dec 2007
Posts: 6
|
 Posted: Fri Dec 07, 2007 4:36 am
[2.16] %numparam stops working, Found!
|
Didn't have any existing code that used it before the switch to 2.15, but used the examples listed in the helpfile and could not get either of them to work. Has the command worked in earlier versions?
Editted by Vijilante: I wanted to update the title so this doesn't get lost. |
|
|
|
|
ReedN
Wizard
Joined: 04 Jan 2006
Posts: 1279
Location: Portland, Oregon
|
Posted: Fri Dec 07, 2007 4:53 am
|
Works just fine for me. I created an alias put a say statement with the function as in:
#say %numparam
and it worked like a charm when I called it. |
|
|
|
|
Xanxis
Newbie
Joined: 07 Dec 2007
Posts: 6
|
Posted: Fri Dec 07, 2007 4:57 am
|
Tested it again and it is working now, but it definitely was not working before.
|
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Fri Dec 07, 2007 12:54 pm
|
This is an old item we have been trying to track down. Something causes that function to stop working, but closing and relaunching CMud sets it back to right. I actually have an alias in my session to check it periodically, and I have yet to catch anything causing it to start failing.
In a way it is good to know the bug is still hiding. If we all keep looking for it one of us will ultimately be able to come up with a list of activities that caused it, and then we can narrow it down to some specific interraction. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Dec 08, 2007 11:31 pm
|
Yay! Bump this into 2.16 and I have a way to replicate it now, but it requires dancing through another bug that seems to be specific to my packages and session. Basically I somehow managed to get a screwed up state in my session with COM that seems to be ongoing. I am looking into tracing that. Once this state gets screwed up the right way then the %numparam bug surfaces.
Hopefully I will have some good news about this soon. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Dec 08, 2007 11:48 pm
|
Success! At least for this way to break %numparam. I am actually guessing the fault is somewhere in the MXP display because I reduced it right to this.
Procedure
1. Launch CMud
2. Close Sessions window
3. Enter at the command line
| Code: |
#SHOW %numparam()
#SHOW "<COMObject>"
#SHOW %numparam() |
Now I can move on to trying to track down the whole interaction that is breaking COM. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Sun Dec 09, 2007 9:59 am
|
Confirmed.
|
|
_________________
Asati di tempari! |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Dec 11, 2007 6:13 pm
|
Confirmed! Good catch. What's really serious about this is that it seems to break %numparam() for good after that. I used:
| Code: |
#ALIAS test {#SHOW %numparam();#SHOW "<COMObject>";#SHOW %numparam()}
test 123 |
to test is, and %numparam works the very first time, but then never again. So I'll definitely try to get this fixed for the public version. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Dec 11, 2007 8:35 pm
|
Found it! This was definitely obscure. It didn't actually have anything to do with MXP. It was just a typo in the code buried in an obscure place. It only effected %numparam after a line was sent to the screen. It could also cause %numparam to effect the AutoAppend option for aliases. Anyway, fixed in 2.17.
|
|
|
|
|
|
|
|
