Talk:Color of a screen pixel: Difference between revisions

From Rosetta Code
Content added Content deleted
(Strange task)
 
No edit summary
Line 1: Line 1:
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. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 09:38, 28 May 2009 (UTC)
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. --[[User:Dmitry-kazakov|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. —[[User:Dkf|Dkf]] 10:53, 28 May 2009 (UTC)

Revision as of 10:53, 28 May 2009

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)