Talk:Color of a screen pixel: Difference between revisions
Content added Content deleted
(modifying tasks and security) |
(on clarifying the task) |
||
Line 2: | Line 2: | ||
:It seems that the language originating a number of tasks recently is not very respective of security. Something of a worry... |
: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) |
: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) |
||
:just like any other task, this is based on the typical running environment for your program. However, I have added the line: "The mouse cursor may or may not have to be active in a gui created by your program." —[[User:tinku99|tinku99]] |
|||
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. —[[User:tinku99|tinku99]] |
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. —[[User:tinku99|tinku99]] |