No, sorry, I can't create an alternative class whenever I change something. That would be a maintenance nightmare.
However, there's a rather simple alternative that allows you to always use the latest Starling version, except for exactly the changes you need.
- First of all, create a Fork of Starling on GitHub. This is what you'll always use in your projects.
- Now make the changes that you require — possible just small ones like the one from above.
- When a new Starling release comes out, simply merge the new release into your fork. The details are described here.
That way, you'll end up with the official version PLUS your little changes. Git is very smart when it comes to merging changes, so this should work very well, without much effort on your side once it's set up.
[Alternatively, I can offer you to manage a custom Starling version for you. But for that, I'd have to ask you to set up a Premium Support package.]