novasmoof / cprocessing Goto Github PK

We use the projects nanovg and glfw

GLFW affects the following possibly implemented functions:

• CP_System_GetWindowTitle

NanoVG Affects the following possibly implemented functions:

• CP_Settings_Get_Fill
• CP_Settings_Get_Stroke
• CP_Settings_Get_StrokeWeight
• CP_Settings_Get_Tint
• CP_Settings_Get_AntiAlias
• CP_Settings_Get_LineCapMode
• CP_Settings_Get_LineJointMode
• CP_Settings_Get_BlendMode
• CP_Settings_Get_ImageFilterMode
• CP_Settings_Get_ImageWrapMode
• CP_Settings_Get_TextSize
• CP_Settings_Get_TextAlignment
• CP_Settings_Get_Scale
• CP_Settings_Get_Rotate
• CP_Settings_Get_Translate
• CP_Settings_Get_ApplyMatrix

I think the best way to keep track of things like this would be to create variables for each piece of state as trying to make NanoVG and GLFW support our desired features would require a lot of waiting and we are capable of keeping track of that it's just slightly memory intensive.

An example of my proposed solution would be like the following:

static CP_Color FillColor;

CP_API void CP_Settings_Set_Fill(CP_Color c)
{
        FillColor = c;
	nvgFillColor(GetCPCore()->nvg, nvgRGBA(c.r, c.g, c.b, c.a));

	// Enable fill
	GetDrawInfo()->fill = TRUE;
}

CP_API CP_Color CP_Settings_Get_Fill(void)
{
        return FillColor;      
}

In the file CP_System.c, there is a struct named GameStateFuncs and it contains a function pointer for the init, update, and exit functions used by C Processing. And when creating an implementation for DigiPen-Faculty#9 I made a structure called CP_GameStates which serves the exact same purpose. I am now wondering if I move GameStateFuncs into the .h file, or if I should replace it's usage in CP_Setting.c. Or if both should just exist independently.