1  |   Order by index

May 9, 2001, 2:56pm

In the AW SDK documentation, it states (under AW_EVENT_OBJECT_ADD):

"Changes to existing objects are sent to your application as an
AW_EVENT_OBJECT_DELETE event followed immediately by an AW_EVENT_OBJECT_ADD
event. In other words, object changes are actually implemented as a
deletion of the old object followed by an addition of the object in its new
state."

However, my recent experiences have led me to believe this is not the case
and that in fact the AW_EVENT_OBJECT_ADD is received first and THEN the
AW_EVENT_OBJECT_DELETE.

This is using Mr Grimms VB wrapper, so, as far as I can see, the issue cold
be in one of two places:

(a) the control is raising the events from a concattenated winsock string in
the wrong order (i.e. starting with the last complete message from server
instead of the first in a given data block)

..... or ....

(b) the AW server is sending them in the wrong order.

Any comments/experiences. If I get some time I'll try it in C++ to see what
the order is, but its always the same result using AwSdkOcx3 ??

Thanks

Grims

May 9, 2001, 3:29pm

Just as a quick follow up to this, I think its actually that AW does the
change as an ADD/DELETE, because of two things I rememeber ...

Firstly, if you have a "full" cell and try to change the action command on
an object ... reducing the amount of text in the field ... it doesn;t let
you unless you move the object to another, less-populated cell, change it
there and move it back.

Secondly, if you are using the SDK to change the picture on an object (most
easily seen with pp00.rwx objects) for a moment BOTH are there.

So I guess that means its not Mr Grimms (sorry) problem and saves me doing a
C++ test.

Grims.



[View Quote]

May 9, 2001, 5:11pm

This issue was just brought to my attention.

The SDK docs are (were) wrong. Sorry about that. How embarrassing! The
correct
event sequence is ADD followed by DELETE.

-Roland

[View Quote]

May 9, 2001, 5:21pm

Awwww .... bugger!

Thanks Roland,

Grims


[View Quote]

May 10, 2001, 11:26pm

I think you are refering to aw_object_change. My own experiments with this
indicate that the bot sdk works like the browser: first the world server
tries to add, without even checking if the cell capacity would accept the
object if the 'old' object was not there. So it is an object add followed by
an object delete. The sdk docs were wrong there, it seems they have now
changed this and eliminated all references to how this happens.


[View Quote]

May 10, 2001, 11:30pm

ah I see Roland has replied :)


[View Quote]

1  |   Order by index