 |
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
 Posted: Sun Jun 22, 2008 5:37 am
[BUG 2.28] Using * to preselect options no longer works for #PICK and %pick.
|
Not sure what's happening here, but no longer will * preselect an option in %pick or #PICK (in most cases - see below).
1. Open CMUD.
2. Escape to untitled session.
3. Use any of the formulas below to produce the bug.
| Code: |
#FORALL %pick("p:Select","test","*testtwo","testthree","*testfour") {#SAY %i}
#PICK {p:Select an action:} {kill:kill @mob} {kick:kick @mob} {*stun:stun @mob}
#FORALL %pick("p:Select",@stringlist) {#SAY %i} //use #var stringlist "*test|testtwo|*testthree|testfour|*testfive" |
All three of those codes above should have something highlighted, however, none of them do. Now, for the peculiar part:
| Code: |
#VAR Actions "p:Select an action|o:1|kill @mob|kick @mob|*stun @mob"
#PICK {@Actions} |
works.
I pray that this will be fixed soon - a few of my scripts that has been distributed uses preselection (such as spellup scripts) and will no longer keep the options selected.
Charneus |
|
|
|
|
Toxic
Adept
Joined: 27 May 2008
Posts: 299
|
Posted: Sun Jun 22, 2008 7:49 am
|
Confirmed. This is also a huge bug for me.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Jun 23, 2008 4:51 pm
|
Confirmed and added to bug list. Did this just break in 2.28, or was it broken in any previous versions? I didn't change anything with the %pick or #PICK command so I'm not sure what's going on here.
|
|
|
|
|
Toxic
Adept
Joined: 27 May 2008
Posts: 299
|
Posted: Mon Jun 23, 2008 4:55 pm
|
Broken in 2.28 only. I think it has to do with when you fiddled with wildcards being in stringlists. Specifically starting the line... ie {* test|(%w) test}
|
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Mon Jun 23, 2008 5:54 pm
|
| Toxic wrote: |
| Broken in 2.28 only. I think it has to do with when you fiddled with wildcards being in stringlists. Specifically starting the line... ie {* test|(%w) test} |
Not true. I have the old installation files (I keep them for reasons like this). I've installed 2.27, 2.26, and 2.25. I've confirmed that 2.25 is the last version this bug did not exist.
However, I am inclined to agree that it is probably something to do with the wildcard preference. Not sure how it can be fixed, though - and even so, I wouldn't think it would affect %pick("p:Select one:","*test","testtwo") and whatnot.
Charneus |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Jun 24, 2008 9:25 pm
|
Well, this one was hard to track down.
It's definitely been broken for a while, and it had nothing to do with the wildcard changes. The problem was the stupid Windows ListBox control. Apparently, changing the Font of a ListBox causes all of the "Selected" state information for the list to get cleared. In CMUD, it was setting the Font of the form to the current system font (Tahoma on XP, Segio UI on Vista). Since it was changing the font *after* the selected state of the various items in the list had been set, Windows was clearing this information.
So in 2.29 I am setting the font *before* the Selected items are set so that this doesn't happen anymore. Hopefully there won't be any alignment or other font side effects from moving the font change earlier in the form creation procedure.
I actually consider this to be more of a bug in Windows. When a Windows Listbox gets a new font, Windows should be responsible for maintaining the state of the object. Really annoying. |
|
|
|
|
Tech
GURU
Joined: 18 Oct 2000
Posts: 2733
Location: Atlanta, USA
|
Posted: Tue Jul 01, 2008 6:18 am
|
I just tested with the cases charneus supplied and this is working now.
|
|
_________________
Asati di tempari! |
 |
|
|
|
|
|
