@Sparth we use the BUG modular python method of doing python. This means that having a CvEventManager.py is a big no no. I created a folder in the Assets/Python folder called Sparth and placed your event manager module there. Your screen is still where you placed it.
There is, in my opinion, a small amount of work still needed to finish this. That is to make it easier for people who come later and want to modify or use the code.
While many C programmers will tell you that "the code
is the documentation", this is only true if there is enough information in the code. Your screen code needs a short header comment saying what it is about. Plus it would be better if all the variables dealing with the same thing used a similar theme in their naming.
For example in the code the stuff about the Great Person portrait is
- _LEADER_ICON for the coordinates and size values
- sButton for the art definition information, and
- TechSplashIcon for the name of the widget
I would suggest something like _PORTRAIT instead of _LEADER_ICON, sPortrait instead of sButton and PortraitPanel instead of TechSplashIcon.
Similarly you have coordinate information for both _QUOTE and _TEXT but use quote and pedia elsewhere.
Cleaning the code up a bit will help who ever comes later. Most of the misunderstanding I had when helping you come from these simple differences in names of things that are about the same thing.