rscotchmer

I feel like I wrote last week's post on Aseprite just yesterday -- time flies near the end of the semester! Since that post, I've made a lot of progress on my issue. For starters, I actually finished it! ...Well, most of it -- waiting on some reviews at the moment, among some other things, but the features I've added work.   You can check out my PR here . Adding elements to the UI wasn't nearly as difficult as I thought it would be, but it still required a lot of thinking on my end... And a lot of sifting through code, too. Mostly for examples, but also to make sure that I was following the project's general style -- the folks working on Aseprite have a unique way of formatting things, and I wanted to make sure I adhered to that as best as I could. Anyway, after a couple hours' worth of work, I managed to finish everything up on a Saturday afternoon. I committed my changes, pushed them, and... Promptly forgot about them for the weekend. Come Monday, t...

For my latest assignment in DPS909, I've been working on this issue in Aseprite . This wasn't really planned -- to be honest, I actually was going to deal with a bug in filer first -- but one thing led to the next, and I suddenly found myself working on this project instead. I talked about how I've dealt with something similar -- making a fill tool -- in last week's blog post -- and much to my delight, that past experience has served me quite well. In fact, modifying the current code for the fill tool to fill pixels connected on a diagonal was hands-down the easiest part in tackling this issue. It took me maybe 20 minutes to implement -- a few lines copied from existing code, a +1 here, a -1 there... Throw in a couple of if-statements, and voila! It's done. The only tricky part came when using the fill tool on a large area caused the program to crash. To determine where the issue was, I used the most basic of debugging techniques -- commenting bits of code...

My next two tasks for DPS909 are to fix two issues that are a bit bigger than the ones I've dealt with previously. Thanks to my prof, I've already got one issue to work on: a bug in Filer where flags are interpreted as strings, not numbers. I'm not entirely sure how much work it will take to fix this -- I think it largely depends on how wide-spread the issue is across files. If it's contained to only a few, that makes my life easy; if not, I imagine I'll be playing a game of "Where's Waldo", where Waldo is one of many instances of the bug. On the bright side, my prof has offered to mentor me through fixing the bug, so I know I can count on some guidance for this. The other issue I wanted to work on is in a different project. I recently got into doing pixel art, which is easiest to make when you've got a specialized program for it. A few Google searches led me to Aseprite , an open-source image editor geared directly toward those of us doin...