MOAR! This looks awesome Mathias

pylacewing - Lacewing for Python
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.
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.
-
-
Is it just me? Or did somebody else notice the title in the newest threads was wrong and attempt to fix it?
-
DG, pylacewing is the correct name...if that is what you are referring too.
Marv
-
Yes Pylacewing is the correct name but look at The Alee's post, it's say Poinc at the top.
-
No biggy. It is after midnight in the uk...
Marv
-
I'm probably asking a stupid question, but I just don't understand something about the factory.connections MultiKeyDict :
I thought connections[name] would return a ServerProtocol instance, but it returns a list of ServerProtocols. I had to use self.connections[name][0] to get the ServerProtocol I wanted, is it normal ? In Lacewing, can two connections have the same name ?PS : Also Mathias, did you check your PM ?
-
You should do something like
connection, = connections[name]
It's a design decision I took, since Moo connections can have have the same name, and since I try to share as much as I can between lacewing and lacewing.moo.
And yeah, I saw your PM, and I'll see about adding it to the wiki soon
By the way, I fixed the tutorial wiki entries (they were importing pylacewing instead of lacewing, sorry guys!)
-
don't even know what this connection,=connections[name] is supposed to do... I'm still a python noob. I'll try to understand that. Anyway I understand what you mean with this moo/lacewing design choice.
Thanks for your answer.
-
Just a reminder of the problems I was having a few days ago.
Server Protocol's self.leaveChannel(self, channel) function throws an error for the MMF2 Lacewing client: Debug code 5 which is "Incorrect data was received; perhaps the server/client is using a different version?"
also
self.acceptChannelLeave(self, channel) never seems to be called, ever.
Edit: Also, I'm having problems with the sending of a channel list. Neither channelListSent nor acceptChannelListRequest seems to be called when I send a request from my MMF2 client. No errors, so I'm not really sure what is going on.
Thanks
-
I'll look into the ServerProtocol.leaveChannel issue
I'm quite sure acceptChannelLeave is fired, so are you sure it's not a bug with your code? acceptChannelLeave is not checked if the ServerProtocol.leaveChannel method is called directly (eg. only if the request comes from the client itself), so perhaps that's it?
channelListSent and acceptChannelListRequest should be working too. Are you sure ServerFactory.channelListing is set to True?
Perhaps you could show me the code/application that this is malfunctioning with?
-
Quote from Mathias
I'll look into the ServerProtocol.leaveChannel issue
Great.
Quote from Mathias
I'm quite sure acceptChannelLeave is fired, so are you sure it's not a bug with your code? acceptChannelLeave is not checked if the ServerProtocol.leaveChannel method is called directly (eg. only if the request comes from the client itself), so perhaps that's it?You're right, it works fine. I was expecting it to be called when the connection fails (after all, channelLeft() is called). Of course, this is silly, the server can hardly say "Nope, you cannot leave the channel" if someones just powered off their computer.
Quote from Mathias
channelListSent and acceptChannelListRequest should be working too. Are you sure ServerFactory.channelListing is set to True?Hahaha, yeah, it was indeed set to false. I wasn't even aware there was such a variable existing.
Thanks, I look forward to the leave channel issue being sorted out.
-
Jamie found a rather tricky bug today, so Please login to see this link.! Will be up on Villy's server in a moment or so.
-
Please login to see this link. has been released, and it is now compatible with Lacewing build 13. I will update aquadasoft.com in a few moments, hang on!
-
Quick bugfix, Please login to see this link. has been released.
-
Another bugfix, Please login to see this link. released!
-
I get a 'server error' from google everytime i try to access the site
-
Well, it's definitely fixed now
-
Please login to see this link. has been released, and fixes pinging (this means that "dead" connections are automatically kicked now).
-
Hi Mathias, thanks for the update. Lately I'm having problems with random disconnects. The error lacewing returns is "Connection denied. Not denied". Unfortunalety nearly impossible to reproduce, because it happens so randomly.
Could this error be related to when you're disconnected due to not responding to ping in time?
I'm using the newest versions for server and client. -
Hnm, might sound like it. I'll dig a bit around to see if I can find the cause
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!