Skip to content

Some naming rationalization and audioenigne.cpp cleanup - #1176

Open
BuzzBurrowes wants to merge 1 commit into
kushview:mainfrom
BuzzBurrowes:naming-rationalization
Open

Some naming rationalization and audioenigne.cpp cleanup#1176
BuzzBurrowes wants to merge 1 commit into
kushview:mainfrom
BuzzBurrowes:naming-rationalization

Conversation

@BuzzBurrowes

Copy link
Copy Markdown

In preparation for the more significant changes to support multithreaded rendering, this step rationalizes some naming to make the code a little more understandable for those new to it, and cleans up a few things.

For example, audioengine.cpp referred to the 'current' graph (in members like "currentGraph"), while much of the rest of the code referred to the 'active' graph. Active seems better and more widely used, so I changes instances of 'current' to 'active'. This also reduces confusion when you see a variable named 'current' inside a large loop block and can easily mistake that name for meaning 'the current graph being processed in this iteration' as opposed to 'the active graph selected by the user'.

'last' has a similar problem. Last in the current iteration? last in the vector of graphs?

So...
'currentGraph' became 'activeGraphIndex'
'lastGraph' became 'priorActiveGraphIndex'

To my mind those are a little better to follow through the code. And later, when I issue a pull request for the much more complicated changes that implement multithreaded rendering, I think changes like this will make that code easier to grok.

In preparation for the more significant changes to support multithreaded rendering, this step rationalizes some naming to make the code a little more understandable for those new to it, and cleans up a few things.

For example, audioengine.cpp referred to the 'current' graph (in members like "currentGraph"), while much of the rest of the code referred to the 'active' graph. Active seem better and more widely used, so I changes instances of 'current' to 'active'. This also reduces confusion when you see a variable named 'current' inside a large loop block and can easily mistake that name for meaning 'the current graph being processed in this iteration' as opposed to 'the active graph selected by the user'.

'last' has a similar problem. Last in the current iteration? last in the vector of graphs?

So...
'currentGraph' became 'activeGraphIndex'
'lastGraph' became 'priorActiveGraphIndex'

To my mind those are a little better to follow through the code. And later, when I issue a pull request for the much more complicated changes that implement multithreaded rendering, I think changes like this will make that code easier to grok.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant