My focus is on having a stable program, without bugs, that compiles without serious warnings...
If you had tested my full patch you would have found it without compiler errors and working. For warnings, well there are a bunch of warnings present since before I joined, why not focus on them?
What is your focus?
Do I sense a trace of sarcasm here?
You patch was judged as a patch. I cannot judge your ideas, I can only judge your code. It was a more complex way to draw images than needed, so I decided to implement a simplier version.
But I told you and every one else that it wasn't a "patch" patch, it was work in progress for the sole reason that you wanted small updates. If you won't accept a patch like that, then you should have said, no we will not look at it, finish the project first
However, the way button images are draw changes absolutely nothing on how the GUI elements are arranged for different sized boxes.
That is because you refused to look beyond the patch. I said the patch was the base structure for the theme system that I will build on. I did explained how this was going to be used, but I still got old assumptions as replies (in best case, usually no reply at all).
In the latter there was no progress for a long time, which is the real show stopper for any themable UI. Well that will most likely be my task for now it seems.
So is it my fault that I had to wait for you to implement stuff in the trunk? What should I have done? My way to respect your efforts where to not post a new patch every week that cancels the patch you worked on. Instead I waited for you to implement them before I continued. So this isn't really in my hands...
I had planned to finish this before Christmas, but that was with the assumption that my code went straight in to the trunk (or whatever)... Instead I have wasted weeks in waiting and now it is my fault?