Back to General and Gameplay Programming

1 (interface) header with 2 cpp (implementation) files?

Cris Kop · 2015-05-28T06:16:08

Hi, I'm currently running a 'design issue'. This is my situation: I have a CMainApp class, which will handle the main application. This class has a member of the CMenuManager class, which (obviously ) handles menu rendering and user input. Currently the menu handling code is part of the CMainApp implementation: CPP file. Now to keep things readable and clean, I want to add a 2nd CPP file with all the menu handling code, which will also be in the namespace of the CMainApp and have a part of the implementation of the CMainApp (all menu handling stuff). For my case this is a good solution. But before I run off I was thinking if there might be a better/ cleaner way to do this. Separating into another class will create extra complexity with interfacing and continously sending data around from one class to another. What would you say, pro's and cons on the proposed solution?

General and Gameplay Programming Programming

Started by cozzie May 25, 2015 07:13 PM

9 comments, last by thatguyfromthething 8 years, 11 months ago

thatguyfromthething

-801

May 28, 2015 06:16 AM

Don't put in a "main app" or a "something manager" class just because. Some things are better off done without OOP. Once you get away from the idea your program needs a main class, then it suddenly makes sense to have your menus etc. be its own separate class.

This is my thread. There are many threads like it, but this one is mine.

1 (interface) header with 2 cpp (implementation) files?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

1 (interface) header with 2 cpp (implementation) files?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines