Problem with setting/changing name action

[Lord_Wezel]

It's been awhile since I messed with any lacewing stuff. The last version I used was the Build #18 Alpha 3, which I liked, despite the problems. I had made an upgraded chat application (originally created using Build #17) for the new build. So, when I got back on here and saw that there was two upgrades since then I decided to try it.

I took my chat app and updated the lacewing versions. I also made a very basic server to test with. I used three servers. Connecting works fine on my server and ledev.org, however, klikfarm.com's server seems to be down.

Then, I moved on to setting the name. I type in a name in the edit box, then click enter. The condition should set the name but it don't. An on name set condition never works, so the rest of my application don't work. Is there something I am missing? or is this a bug that needs fixed?

[Phi]

As a suggestion, the Connect action was updated between #17 and #18, you might want to recreate that.

[James]

Could you upload your MFA?

[Lord_Wezel]

I tried to upload but my connection is not working good right now. Here is my event lines in the MFA:

Start of frame > Connect to "ledev.org:6121"

On connect > Next frame

Upon pressing "enter" > Set name to editbox$

On name set > Join channel "Channel"

On channel join > Next frame

That is the basic form of my events. Also, I have a message at the bottom of both frames that gives status updates (connecting, connected, joining channel, etc.) However, the 'on name set' event won't work (and the message won't update past this event either).

Like I said, connecting works fine, both on my server and ledev. However, the name set action either does not work or the on name set condition does not work.

[Greg]

I've just made an app like that and it works fine for me. Make sure you have the "Global" checkbox in Lacewing's properties checked and that the "Global identifier" is the same in both frames.

[Lord_Wezel]

Thanks Greg! I can't believe I missed that! I forgot that it resets after updating to the next version. I had that same problem with #17, when I first started using it. Thanks.