cejay2001

This latest update seems to be on the Beta Channel only.  Is this correct, that this version is not a official stable release?

Cheers,

Chris

Ok, fair enough.  Is that in the GMS Help as I didn't find anything relating to a 1 step delay?  If not, there will continue to be a lot of confusion around this.

It also seems particularly messy, but more so for me as I am converting legacy code.. I guess if you are building something from scratch and are aware of this change then it is not such a big deal.

I don't think so.  From my understanding using the "with" statement is still fine, as long as you are not trying to access deactivated instances.  In my case I have called instance_activate_all earlier in the script, so they should be accessible using "with".

At least I think so. :|

I did end up putting the object instances into a ds_list just so I could enumerate them after re-activation.  Kinda sux but at least it gets me moving until a fix comes along or I understand the functions better.

Seems to still be a problem with reactivating instances.  I can't perform "with" or even enumerate instances using "instance_number" on objects that have been reactivated in the same script... in fact I'm unsure how many steps it takes before an instance is accessible again.

I guess the work-around would be to put all the instances into a ds_list or something and enumerate that instead, but makes for unnecessary code especially if this is not the intended way for instance re-activation to work.

Anyone else has similar issues?

eg.

instance_activate_all();

[follwed by]

with (some_obj)

[OR]

instance_number(some_obj)

Neither of these methods appears to find any instances.. at least within the same script