Lacewing Build #19

Lacewing Build #19 is now available:

http://lacewing-project.org/LacewingMMF.zip

Hopefully this should resolve the outstanding problems with build 18. This build will also soon be available for the iOS and Android runtimes.

A few things to note :-

- This is not protocol compatible with any previous build of Lacewing. A public pylacewing server is running at ledev.org:6129, although this will move to port 6121 in the next 48 hours.

- Although you can open old MFAs with Build #19 (right back to OINC MFAs with the converter), the extension properties will be reset. Opening an MFA with an earlier build after saving it with this one will result in corruption.

- Lacewing has now moved from rSDK to the Edif SDK, and is sharing code across several platforms. This has required major internal changes, so it's quite possible some behaviour will have changed or some things might be broken.

Thanks to Konidias, Hempuli, Looki and SToP_GAP for all the testing these past few days :-)

huzzah!

http://klikfusion.com/awesome.jpg

:D

Did you use the JSON Generator? >_>

Due to the cross-runtime code sharing, it's not a conventional Edif extension (it doesn't use the Link* or anything).

I would have otherwise, though!

Wow, nice to see a progress. Keep updating!
When I'm trying to compile library terminal says:
(...)
cc -DLacewingLibrary -DHAVE_CONFIG_H -fvisibility=hidden -fPIC -DPOSIX_SOURCE -O2 -fno-exceptions -fno-rtti -c -o build/addr_flat.o src/c/addr_flat.cc
src/unix/Timer.cc: In constructor ‘TimerInternal::TimerInternal(Lacewing::Timer&, PumpInternal&)’:
src/unix/Timer.cc:56:23: error: class ‘TimerInternal’ does not have any field named ‘LegacyTimerThread’
make: *** [build/Timer.o] Błąd 1
make: *** Oczekiwanie na niezakończone zadania....
radeg@radegPC:~/Pulpit/lacewing/2.2$

What do I have to do?

#edit
It worked when I put inside ifdef:
Lacewing::Thread LegacyTimerThread;

Will it work without problems?

It will - I was sure that was fixed. Thanks.

Updated the archive to include the Android version (for Android runtime testers).

Thank you Jamie, very nice !! :D

Hooray for the new release :D I've got a question though: I use Windows, do I need to compile the sources at http://lacewing-project.org/ myself or can I get the Lacewing.h and Lacewing.dll somewhere else?

You do need to compile them (I intended to supply binaries but never got round to adding it to the distribution build script).

There's an MSVC project file in the 'msvc' directory, which should be able to build Lacewing.dll out of the box. Lacewing.h is in the 'include' directory.

It worked flawlessy, thanks :)

Silently updated the extension to fix an issue with "On error" not being triggered.

Hey Jamie.. any release-date for the iOS port of lacewing? ;)

Seems that "On channel join denied" still doesn't work. Nothing very important, but still... :P

Ouch, sorry - somehow that fix escaped my main source folder. It's fixed now (same URL).

jamie ? ;)

I don't know - Andos seems to think it would require some changes to the runtime in order to link against the correct frameworks at build time.

I'll let you know when I have more information. All the code is ready, at least...

To release the iOS version of Lacewing we need to modify the export mode a little bit (behind the scenes). Otherwise the lacewing code will be included in all iOS released games even though they don't even use the extension.

I don't really have an estimate yet. I will talk with Francois.

Quote:

---

Originally Posted by Jamie

Ouch, sorry - somehow that fix escaped my main source folder. It's fixed now (same URL).

---

Wow, you're fast :D Thanks :)

Yet another thing I'd like to know: What's the difference between RelayServer and Server? Seems like the RelayServer is more similar to structure in the old Lacewing. Which one should I use?

P.S.
RelayServer keeps printing some stuff while running:
"[Lacewing] Preparing to send type 0, size 32".
What's that and can I somehow stop it printing?

Build the Release configuration for Lacewing.dll if you don't want the debug output.

The extensions for MMF2 implement the Relay protocol, which is the high level protocol with channels and such (this is available through Lacewing::RelayServer in C++).

Lacewing::Server is a raw socket server - it doesn't implement any protocol at all, just straight TCP.

I've silently updated the extension again with a fix for a crash when the extension is used across sub-applications.

Sorry about this - I guess some things just don't get found until the extension is public, and I'd rather not have everyone wait for build 20.

No need for "sorry" Jamie. You're doing the best you can and yes, things do just slip by.

Thanks for the update.

Marv

Yeah it is not a big issue to have to re-download the fixes. Anyone who is actively using Lacewing right now is probably watching this thread every day anyway. :P New Lacewing users will always get the latest version when they download it, so no sweat.

Thanks again, Jamie.

Well, so long as it doesn't cause any confusion, I guess!

Those using the liblacewing from C++ should note that liblacewing 0.2.3 has just been released.

Jamie you might also want to make note of the changes for conditions of messages sent from server to a channel or to "me". That is new in build 19 and it will break some games/apps that were using those features in previous builds.

It will break those apps? How so?

Instead of 1 condition (Message received from server), there's now 2 (Message received on channel from server, message received directly from server).

So, how will it break existing apps?

Because if they're sending channel messages to the client from the server and use "On message from server", it won't fire. They need to use "On channel message from server" instead.

I've got yet another question:
How do I start a new thread in the new Lacewing? In build #17 I had a line:

Code:

---

Lacewing::Utility::StartThread(ping, &Server);

---

And what's the difference between starting a thread in Lacewing and starting a thread in C/C++?

The thread functionality is a class now:

Code:

---

Lacewing::Thread MyThread ("Some Name", YourThreadFunction);
MyThread.Start (SomeParameter);

---

The difference is that C/C++ has no facility for starting threads. Lacewing uses whatever functionality is provided by the operating system (WINAPI, or pthread on Unix).

I hope you're aware that most of the liblacewing classes aren't thread safe! Maybe you should consider using something like Lacewing::Timer (if possible) rather than a thread. Failing that, use the EventPump Post() method to run code at a safe time in Lacewing's event loop.

Thanks for the quick reply, as always :D

I had no idea, thanks for letting me know :) You mean something like this?

Code:

---

void onTick (Lacewing::Timer &Timer)
{
  //Ping all clients
}

Lacewing::EventPump TimerPump;
Lacewing::Timer Timer(TimerPump);
Timer.onTick(onTick);
Timer.Start(30000);

---

To ping each 30 seconds?

Both the Server and the Timer should share the same EventPump, but otherwise, yes.

Did you know that the protocol has pinging built in to detect lost connections?

Really? :D Is that some class I need to use or is pinging done automatically?

It's automatic!

By the way, the correct usage of the EventPump in a console application:

Code:

---

int main (int argc, char * argv [])
{
    Lacewing::EventPump EventPump;

    /* Create any classes you want to use, passing EventPump to the constructor.  Example: */

    Lacewing::RelayServer Server (EventPump);
    Server.Host ();

    /* This function will not return.  Internally, it will loop forever,
      letting the other classes know when a socket is ready etc. */

    EventPump.StartEventLoop ();

    return 0;
}

---

Wow, that's great! :D Lacewing keeps surprising me :D
And thanks for the code sample :D

Sorry for bothering, but I've got YET another question xD
Could you please give me a sample code on how to iterate through all clients in the server/channel?

No bother at all! :-)

Iterating through all clients on the server:

Code:

---

for (Lacewing::RelayServer::Client * Client = Server.FirstClient ();
                Client; Client = Client->Next ())
      {
          printf ("Client %s is present\n", Client->Name ());
      }

---

Iterating through all clients on a channel:

Code:

---

Lacewing::RelayServer::Channel::ClientIterator Iterator (Channel);

for (Lacewing::RelayServer::Client * Client = Iterator.Next ();
            Client; Client = Iterator.Next ())
    {
        printf ("Client %s is in the channel\n", Client->Name ());
    }

---

If you get any "unresolved external symbol" errors with this code, grab the edge liblacewing source from here.

Thanks again! :D I'm sure it's gonna be helpful, not only for me :D

EDIT:
I had the "unresolved external" problem and compiled the source you gave me and it compiled correctly. Do I need to use that *.DLL too?

Sorry for the double post, but it's a different thing now. There seems to be a bug in the Relay Client for MMF. The function "StringWithSize$" takes only one parameter - the index. Shouldn't it also take the size?