SDK question, about Scene_Base

[BwdYeti]

Could someone explain the Scene_Base part of the SDK?
It starts on about line 2012 in 2.4
The main question I have is why it forces all instance variables of a scene to update. (Line 2099 for checking each variable, and 2145 where it actually updates)
This is... problematic when the Scene's update method also updates individual objects, causing some things, like a Window, to update twice per tick, and causing strange behavior.

 

[tibuda]

Could someone explain the Scene_Base part of the SDK?
It starts on about line 2012 in 2.4
The main question I have is why it forces all instance variables of a scene to update. (Line 2099 for checking each variable, and 2145 where it actually updates)
This is... problematic when the Scene's update method also updates individual objects, causing some things, like a Window, to update twice per tick, and causing strange behavior.

Just remove any object.update from your custom scenes.

EDIT: You asked why it forces, but this is the main idea behind the Scene_Base. Compare the default way of writing a scene and the scene-base way:

class Scene_Custom
  def main
    obj1 = Obj1.new
    obj2 = Obj2.new
    ...
    objn =Objn.new
    while $scene == self
      obj1.update
      obj2.update
      ...
      objn.update
      Input.update
      Graphics.update
    end
    obj1.dispose
    obj2.dispose
    ...
    objn.dispose
  end
end

What a mess!!!! Now look at the scene-base way:

class Scene_Custom < SDK::Scene_Base
  def main_init
    super
    obj1 = Obj1.new
    obj2 = Obj2.new
    ...
    objn =Objn.new
  end
end

Wow! It will update and dispose all my objects, and I don't have to worry about that.

 

[BwdYeti]

I guess that's nice, but I'd rather choose where things update in case order matters, or so things that don't need to go off every frame don't.

 

[tibuda]

You can disable the auto-update of your classes by returning false in "disable_update?" method. SDK::Scene_Base will not update an object if this method returns true.

class MyClass
  def disable_dispose?
    true
  end
end

 

[BwdYeti]

Oh, that's useful. Thanks. It's nice the SDK people had foresight on including things like that.
EDIT: Searching for that in the SDK, individual objects can have that added to them? That's even more useful since I'm editing Scene_Map, and don't want all the old stuff to not update, just what I'm adding. Very nice.

 

[tibuda]

EDIT: Searching for that in the SDK, individual objects can have that added to them? That's even more useful since I'm editing Scene_Map, and don't want all the old stuff to not update, just what I'm adding. Very nice.

That's how it's supposed to work.