Blog

  • A Murder of Scarecrows

    Via her majesty.

    That’s “a flock of Scarecrows” to save you the dictionary.com trip. A Flash game which pits you, a seed tossing gang of trees, beset to lob your seeds at scarecrows so they will be imbued with the ability to swing away the crows/ravens. I’m not sure of the moral stance here. I mean, trees are pretty good I would think, and imbued scarecrows have been both good and evil in the movies… the birds, however, are definitely the antagonists.

    Regardless, the drawing and design is just awesome. The intricate drawing and rendering for the graphics is dark, yet inviting; sinister, yet sad. I really like it.

  • Geeks Don’t Get Overtime

    Via Her Majesty

    I believe it was the FCC or somesuch acronymn that wrote a book that her majesty was reading for class, and it mentioned Rule 6; about professionals, mainly non-monkey-button-pushers, do not get overtime.

    The ending of the article, however, strikes a chord about being confused… I don’t ever remember hearing of anyone getting overtime anyway. I mean, Eminen did at the factory in his movie, and I’ve heard of other blue collar ‘esque jobs when my parents would talk about such things. Currently, I’m happy with the contracting situation as I get paid hourly, and the more I work, the more hours I get paid for. It’s the same amount, but I’m still getting paid for the amount I do.

    At any rate, I really have no clue how this affects people/businesses… has anything changed, and does this really impact anything? I don’t really see this as bad news as more of a reflection of how things already are. I don’t know enough really, though, to comment with authority.

    New overtime rules are mostly bad news for employees

  • getNextHighestDepth gotcha: Part Deux

    Via Ryan.

    Blogspammers managed to break and foobar my MoveableType commenting system while I was on vacation for 2 weeks. However, comments like this remind me why I slave so hard to ensure it’s easy for readers to comment on my blog.

    Since commenting is currently disabled till I fix it, here is the comment that got lost in a black hole, but brought to light a reason behind a problem I was having.

    *******

    This was driving me nuts, too. The answer is here. The long and short of it is if you are
    using a button component in your movie and create, duplicate, or attach a
    movieclip using _root.getNextHighestDepth(), the movieclip’s depth will be
    1048576, at which depth the mc.removeMovieClip() method will not remove the
    clip. It is important to remember that other components rely on the button
    component for functionality, and so components like UIScrollBar will also
    trigger this bug. In addition, the component does not have to even be on
    stage; having the component present in the library is enough to provoke this
    behavior.

  • How long are you staying on Mars? 2 weeks…weooOohHoo-eeks

    If you know what movie that’s from your da man/whoa-man.

    For real, I’m out of here for 2 weeks, not to Mars though. I won’t even be able to check email. Only electronics I’m allowed to touch are my gaming systems and my cell phone. If there is tons of blogspam (which there will be), I’ll clean up the mess when I get back. Getting merrr’d, then heading to the sunken city for a moon of bee food. Peace oUUOUOUOUOUUUTTT!

    :: end of transmission ::