Search Results

Search found 6 results on 1 pages for 'emi1faber'.

Page 1/1 | 1 

  • Using tslib (touchscreen input) with DirectFB on embedded system (gumstix overo)

    - by emi1faber
    I'm attempting to use tslib with DirectFB on the gumstix Overo. Everything seems to be compiled correctly, as when DirectFB starts up, I get messages saying "Started 'tslib Input' ... DirectFB/Input: tslib touchscreen 0 0.1 (tslib)" etc. However, I haven't been able to find any example code showing how one reads the X-Y coordinates of a touchscreen press. Is there any example code out there to initialize the touchscreen and return the coordinates of a touchscreen press? Thanks in advance, Ben

    Read the article

  • Possible to change the alpha value of certain pixels on iPhone?

    - by emi1faber
    Is it possible to change just a portion of a Sprite's alpha in response to user interaction? A good example of what I mean is iFog or iSteam, where the user can wipe "steam" off the iPhone's screen. Swapping images out wouldn't be feasible due to the sheer number of possibilities where the user could touch and move... For example, say you have a simple app that has a brick wall in the background that has graffiti on it, so there'd be two sprites, one of the brick wall, then one of the graffiti that has a higher z value than the brick wall. Then, based upon where the user touches (assuming their touch controls a sandblaster), some of the graffiti should be removed, but not all of it, which could be accomplished by changing the alpha value on a portion of the graffiti sprite. Is there any way to do this in cocos2d-iphone? Or, do I need to drop down into openGL, and if so, where would be a good place to start my search on how to accomplish this? Ideally, I'd like to accomplish this on a cocos2d-iphone Sprite, but if it's not possible, where's the best place to start looking? Thanks in advance, Ben

    Read the article

  • Encoding / Error Correction Challenge

    - by emi1faber
    Is it mathematically feasible to encode and initial 4 byte message into 8 bytes and if one of the 8 bytes is completely dropped and another is wrong to reconstruct the initial 4 byte message? There would be no way to retransmit nor would the location of the dropped byte be known. If one uses Reed Solomon error correction with 4 "parity" bytes tacked on to the end of the 4 "data" bytes, such as DDDDPPPP, and you end up with DDDEPPP (where E is an error) and a parity byte has been dropped, I don't believe there's a way to reconstruct the initial message (although correct me if I am wrong)... What about multiplying (or performing another mathematical operation) the initial 4 byte message by a constant, then utilizing properties of an inverse mathematical operation to determine what byte was dropped. Or, impose some constraints on the structure of the message so every other byte needs to be odd and the others need to be even. Alternatively, instead of bytes, it could also be 4 decimal digits encoded in some fashion into 8 decimal digits where errors could be detected & corrected under the same circumstances mentioned above - no retransmission and the location of the dropped byte is not known. I'm looking for any crazy ideas anyone might have... Any ideas out there?

    Read the article

  • Designing a solid API, how?

    - by emi1faber
    Obviously, APIs have exploded over the past few years, but many of them seem poorly designed when it comes to utilizing them... I have an opportunity to design an API however I see fit, but I would like it to be easy to use for those accessing it. Of course, keeping it as simple as possible is a big help, but what are the gotchas that people have run into out there? Anything that should be avoided at all costs or implemented at all costs?

    Read the article

1