Forum Discussion

NewManLiving's avatar
12 years ago

Undocumented roRegion Services ?

Apparently you can create an roRegion using the roScreen as its source bitmap, although the resolution/scaling is off. It also appears that roRegion exposes an ifDraw2d interface , resolving it perhaps by calling it's source objects ifDraw2d interface. I created an roRegion using roScreen as its source and then called the (non-documented)
roRegion.DrawObject, roRegion.DrawRect , all of which appears to work. (I don't see any of this documented, but did come across a post on this forum). I am particularly interested in creating regions right from the roScreen buffer which apparently works except for the scaling that is returned. I have not played with any of the pretranslation or scaling flags or rendering functions to see if I could fix it. Any light on this ??? it could possibly help those of us struggling with memory issues. Now I tried all this while a compositor was sitting on top of the screen so I don't know if I would have had different results without the compositor. But before I continue experimenting, I would like some feedback if possible. Perhaps there is some other documentation that I should be looking at

12 Replies

  • Thanks for the info Joel. Maybe you could tell us what is done 'internally'
    With the byte array that can be returned from a bitmap. Seems to have no purpose
    - For us anyway.
  • "RokuJoel" wrote:
    "NewManLiving" wrote:
    It always makes me wonder what really is in the SDK that only the 'privy' know.

    1. Components and functions that have been build for internal use and have not been API reviewed.
    2. ... or that engineering plans to revise significantly
    3. Custom components, developed for specific business partners which we may or may not eventually release to developers - the general philosophy is that we will eventually release most, unless they fall under #2.

    As luck will have it, yesterday i was going over list of classes to see what i am missing - many seem to be in 1-2-3 but there seem to be also

      4. Components which RokuCo is blissfully unaware are still undocumented. Examples would be roInput and roInputEvent, that exist for maybe 3 years now (earliest mention i see is Jul'2011 in this forum), as well as roGlobal (i digged and this one is explained in BrightSign Object Reference Manual)

    If s/o from RokuCo is willing to label them as 1, 2, 3 or 4 accordingly, i'll open a topic with list of those classes?