1  |   Order by index

Jul 21, 2006, 9:06am

I think there's something wrong with the ordering of the callback/event
handler invokes in the SDK for (at least) aw_enter (BUILD 62).

Following an asynchronous aw_enter method call, first the SDK reports an
AW_CALLBACK_ENTER callback, then an AW_EVENT_WORLD_ATTRIBUTES event. This is
arguably OK (though inconsistent with similar methods), except that the
world attributes are populated for the CALLBACK and NOT set for the event -
with obvious concequences.

This can be recreated by changing one of the world attributes (say,
aw_string_set(AW_WORLD_NAME, "RUBBISH")) in the AW_CALLBACK_ENTER callback
handler. The value of AW_WORLD_NAME will still be "RUBBISH" in the
AW_EVENT_WORLD_ATTRIBUTES event handler, as shown below.

aw_enter
CALLBACK >> AW_CALLBACK_ENTER [RC = 0 RC_SUCCESS]

... etc. etc. etc.


[NOTE: AW_WORLD_NAME set to "RUBBISH" in callback handler]

EVENT >> "AW_EVENT_WORLD_ATTRIBUTES"

I assume from this that the AW_CALLBACK_ENTER callback is simply being
triggered from the SDK, on receipt of the AW_EVENT_WORLD_ATTRIBUTES event
.... but, incorrectly, before the event handler is invoked.

Rather than email directly to AW at the moment, can someone verify whether
this has already been raised in the BETA newsgroup please? I'd expect not
after three versions of the 4.1 SDK having been "released" to date.

Grims.

Jul 21, 2006, 2:21pm

*snickers* We can use callbacks with the SDK!?!?! Wait a darn minute! I do
not think the issue has been addressed in beta.

DM

[View Quote]

1  |   Order by index