Zugg Software :: View topic - [1.29] Using Find in Settings Editor results in Access Violation, hard crash

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

I noticed this in 1.27 but hadn't posted yet.

Searching for a particular string in the settings editor result in an access violation.
Oddly when I search for the term 'wielded' then CMUD crashes with
Error: Access violation at 0x25726325 (tried to read from 0.25726325), program terminated.

That's the only term I can find that causes a crash so far.

Since it's such an odd bug I'm guessing you'll want the pkg Zugg - it's the same package I mailed you for the parser error.
Subject: [1.27] Access violation when opening package (forum post 108727)
Sent: Sat 14/04/2007 02:31 (GMT)

The automated reply gave it ticket #20691 if that lets you track it.

On another note - is it possible to have the settings editor remember when you have the search box visible? I use the search a lot and it's annoying having to reselect it.

Posted: Wed Apr 18, 2007 2:01 pm

I think that is specific to your package. I can't get it to fail for me.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Yeah, makes me think I have a corrupt trigger with the word 'wielded' in it. Still, might be worth a look

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Just updating to 1.29 and bumping. Do you need me to email the package again Zugg?

Posted: Sat Apr 21, 2007 1:37 am

Guinn, what was the PKG filename? I can't figure out how to search this silly helpdesk system for the ticket ID number. Seems like that should be easy and I've emailed the author about this. But for now it looks like it's buried with all of the other hundreds of crash dumps. I thought I had moved the issues with attached files to a special folder, but I don't see #20691 there.

Anyway, feel free to email it again to sales@zuggsoft.com to bypass the help system. Sorry I didn't get to this, but I was just too busy with all of the other issues I was trying to fix.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Just sent again. ElysiumRPG.pkg
(oops, sent to support first time. sent to sales too now)

Posted: Mon Apr 23, 2007 8:54 pm

Looks like it's a problem with one of your buttons. You have really long captions for your buttons and it's causing some Windows API crashes. I'm investigating some possible fixes. But it has nothing to do with the Search function. If you just try to click on your button that starts with "%proper..." in the settings editor, you will see the same crash. This button contains your "wielded" word, so it's the one that is trying to display from the search.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Ahh okay. To fix for now then I've created a variable with the caption and have the button showing the variable instead.
I couldn't actually change it in CMUD though, so I grabbed SQLite and edited the pkg file directly to rename the offending caption Twisted Evil

Posted: Mon Apr 23, 2007 9:50 pm

Just out of curiosity, and so I can avoid this problem myself, how long was this caption?

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Hmm, on a related note Zugg. I've now made the variable that contains the above caption (@invButton). The problem now is that the button caption doesn't update when the variables referenced in 'invButton' change... any way to force a button to look inside variables referenced within a variable that's in the caption?

Posted: Mon Apr 23, 2007 10:12 pm

My suggestion would just be to break it into more than one button, since it's just info display. You could quite easily use toolbar-mode buttons and separators to recreate (or to mostly recreate) the old look.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

heh, I suppose it doesn't matter a great deal, I've largely stopped mudding and mainly play with CMUD out of interest rather than because I'll go back to mudding properly. Will wait for the API fix ;)

Posted: Tue Apr 24, 2007 3:01 am

Turns out there doesn't seem to be a specific length problem in the API. It depends upon the button size as well. The problem is that the settings editor is not expanding the caption. So while the expanded caption works within the main button window, the raw caption doesn't fit in the sample button in the settings editor.

For the settings editor, I'm putting a limit of 64 characters on the display. That seems to help for now until I can find more real documentation on what the limits are for the Windows API.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

What I have done in a similar situation is to create an expression trigger that sets the Variable that I am using for the button caption as the value to an expanded string. That way every time the expression changes the variable changes. When the variable changes the button updates.