Modern hardware is built for multitasking. In order to make that work you have one and only one program managing the display (typically the OS), and all other programs go through the OS and access the data indirectly.
This allows the OS to do things like window layering, and prevents conflicts. What would happen if two programs were trying to draw data to same part of the screen at the same time? Which would "win"?
This is why everything is done through libraries. Direct access to the hardware is simply impractical. Not because it's too complicated, but because it is prone to conflict and doesn't play well with other programs.
There is almost never a practical reason to bypass this pipeline. And I'm really wondering why you would even want to consider doing it. Why wouldn't using a library work for your needs? Why do you feel you need to skip the middle-man?
Unless you're looking to write your own OS, I really don't see the point here.
|Chemical Engineer wrote:|
|And I think this because no one's telling me how. I don't think that they're trying to push me around and mess with me - it's more likely that they just don't know.|
To address this: I don't know how. I've never had the need.
I question whether you really have the need, or if you just think you have the need.
|However, I do have to mess with the plumming. Do I really need to explain why?|
I suppose you don't. It would certainly satisfy my curiosity, which would be appreciated, but it wouldn't put me any closer to give you the answer you're looking for.
At best if you could explain why you think you need it, we might be able to explain why you really don't, and be able to suggest an alternative way to do what you want that has the same end result.