Talk:Color of a screen pixel

From Rosetta Code
Revision as of 02:45, 30 May 2009 by rosettacode>Tinku99 (modifying tasks and security)

I propose to clarify the task. In an operating system there can be many screens and many mice and other user output/input raster devices etc. Further under a properly designing operating system you just cannot access an arbitrary pixel on the screen for obvious security reasons. I suppose this task has rather something to do with a certain GUI framework, or, maybe, graphical system? How to get a pixel in X11, Windows API, .NET, OpenGL, GDK, GRAFOR ... infinite list? makes no sense to me. --Dmitry-kazakov 09:38, 28 May 2009 (UTC)

It seems that the language originating a number of tasks recently is not very respective of security. Something of a worry...
OTOH, we could just redefine the task to something that more languages can do with common utilities/libraries and ignore the fact that this will cause the originator pain. —Dkf 10:53, 28 May 2009 (UTC)

Getting pixel information is a basic task related to "accessibility", "testing", and just "getting things done". Thats what programming is for in the first place. Its not a security problem if your are the owner of the computer, and that is what you want to do. If a particular language can not do the task, it should be put in its ignore list. The task should not be modified to fit that language. —tinku99