Lacewing Build #18 Alpha 3

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    This is the third alpha of Lacewing Build #18. The previous builds have been tested privately.

    Please login to see this link.

    Build #18 uses the new version of liblacewing, which is an entirely different library than what was used by earlier versions of the extension. It is incompatible with the previous protocol specification, and there's a public pylacewing server at ledev.org:6124. The old Lacewing server will be taken down as soon as this is released as a stable build.

    Please report all bugs in this thread. Thanks for testing!

    The new pylacewing version (1.0) has been released on Please login to see this link.. I'll upload it to the Google Code project page soon also ;)
    This allows you to do

    Code
    python -m easy_install pylacewing

    to install pylacewing, in case you find that useful.

    Would this update change anything regarding update 17.

    I have already coded everything in build 17, and it works. And i don't want to mess my code up by updating, i mean would i have to recode anything if i would update?

    Also will this update fix the bug in swf with peers not disconecting sometimes. Cause sometimes when i close the application the peer remains on the server. It does happen very rare, but it's quite annoying.

    Also will the condition on name denied work in swf?

    My signature is the awesomest!

    Quote from nivram

    Skyhunter, maybe wait until this build is out of alpha. After all, everything works you say, so what would be the point in the risk of hosing your program.

    Marv

    This! Really, we do try our best to make sure new releases work correctly (which is why we coordinate pylacewing and the C++ extension and API to be released simultaneously), and especially this new release will hopefully kill all the possible problems you guys have been experiencing (and make it easier for Jamie to maintain the C++ side also) :)

    Even though the protocol has changed entirely, the changes are pretty much only behind the scenes (4GB messages are pretty cool in my opinion), so making the extension code work should be a non-problem, and old pylacewing code only needs calls to disconnect() changed ;)

    Build 17 MFAs can be opened with the 18 Alpha, but then once saved, it's not safe to open them with 17 again.

    In other words, you should simply save under a different filename. I don't want to discourage anyone from using the 18 Alpha, else it won't get tested.

    I did do a quick stress test, the previous builds of the server extension seemed to crash randomly on connection once in a while, I made a client app that connects, sets name, joins a channel, then leaves, then repeats the process very quickly, seemed to handle this fine at first, froze at connection attempt 1498 for some reason though? neither app crashed but something went wrong..?

    When sending a file, the MMF2 application will sometimes freeze for around 5-20 seconds.

    When receiving a file, the MMF2 application will sometimes freeze for about the same duration or even crash. The impact seems to vary depending on the file, where I'm completely unable to receive certain files.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login