Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualKhatharr

Posted 28 November 2012 - 01:37 AM

The unique case I had in mind was one where I had to free almost all the memory in use to trigger a resource intensive system call that also took control of the device's audio and video for the duration of its execution. That platform had a couple cases like that.

In the current implementation I only have to include the header for a new scene in ns_SceneMgr.cpp, which instantiates the scene objects. If I changed it I'd have to add each new scene header to all the existing scenes and add all of them to the new scene.

The current imp doesn't really have a lot of include headers. (?) I don't understand what you're worried about there. The vclass includes the SceneMgr header and the SceneMgr code file includes its own header, the vclass header (which is redundant but explicit) and its inheritors. Apart from that the inclusions are unrelated.

Changing or adding a Scene derivative is a relatively quick rebuild. If you're concerned about the change of the enum triggering a recompilation of all scenes then I'd submit that this would happen anyway without the enum since, once again, I'd have to add headers between all the scenes. It would just mean that I'd have to do more footwork to accomplish the same result.

#1Khatharr

Posted 28 November 2012 - 01:33 AM

The unique case I had in mind was one where I had to free almost all the memory in use to trigger a resource intensive system call that also took control of the device's audio and video for the duration of its execution. That platform had a couple cases like that.

In the current implementation I only have to include the header for a new scene in ns_SceneMgr.cpp, which instantiates the scene objects. If I changed it I'd have to add each new scene header to all the existing scenes and add all of them to the new scene.

The current imp doesn't really have a lot of include headers. (?) I don't understand what you're worried about there. The vclass includes the SceneMgr header and the SceneMgr code file includes its own header, the vclass header (which is redundant but explicit) and its inheritors. Apart from that the inclusions are unrelated.

PARTNERS