2005-10-05, 09:41 PM
yeah i was thinking if this was left up to a seperate plugin, and if it was possible it would be easier for you.
i would prefer if you (sub) would just use the screenImageBounds thingy to reposition the image to cope with overscan, since you would only have to put that line of code in one place (and then it would work with every plugin).
we would just need a method like pluginHelper.setScreenImageBounds(rectangle). since when the user wants to adjust the screenImageBounds we would have to set it first to the full image (most likely 0,0,720,480) and then once then figured out the best image size, then call that method again.
so is my logic sound with the plugin crap? does every one think it would work?
i would prefer if you (sub) would just use the screenImageBounds thingy to reposition the image to cope with overscan, since you would only have to put that line of code in one place (and then it would work with every plugin).
we would just need a method like pluginHelper.setScreenImageBounds(rectangle). since when the user wants to adjust the screenImageBounds we would have to set it first to the full image (most likely 0,0,720,480) and then once then figured out the best image size, then call that method again.
so is my logic sound with the plugin crap? does every one think it would work?