05.19
I participated in the Bug Quash at 360|Flex. Well, technically it was a day before the conference as a pre-conference event. It went really well and I personally killed 3 bugs.
- SDK-21202 was the fix to a pet bug of my friend at Flex Ninja which he pretty much assigned to me when he heard I was going. The problem is that event listeners of NavBar children aren’t removed, which means if you change a label or icon or such on a child that was removed, the function will be called but then you’ll get a crash since the child is no longer there. It was easier since the workaround was already there as well.
- SDK-21204 was the same bug, only with accordians. Ryan Frishberg actually pointed this out to me, which meant another similar fix. Ryan was at the Quash from adobe to help speed up the patch acceptance process, but he also discovered that a strange guy (me) would be harassing him to look at stuff.
- SDK-21211 was an interesting bug to look at. It turns out that there wasn’t a default setting for the border of tooltips. Even better, the border is what triggered the drawing of the background box. That meant if you used any non-standard border, you’d loose the background. The fix was pretty easy, just make the default value for a tooltip border “toolTipBorder” the default all the time, not just when the border is set to “toolTipBorder”.
Final Thoughts? Flex SDK Bugs actually aren’t that bad to fix. You just have to find stuff that’s simple and try not to overthink what’s going on. Then submit a patch and hope it’s accepted. It’s a little overwhelming to look at the entire SDK, but you don’t have to worry about the whole thing, just deal with your little window, monkey patch a fix first in a simple Flex project (some bugs even have test cases you can use) then once the patch works, tie it back into the SDK itself.
I submitted another patch (SDK-21207) which was rejected, but it had some nice feedback. I’ll probably revisit it and try it again sometime in the future.
No Comment.
Add Your Comment