AutoHotkey Community

[Watcher]

It occurred to me today, since I work with pixels a lot, why don't I just remove the RGB param off of all my commands, I don't really care if it's RGB or BGR... then I remembered that the reason I have to put that in is that many commands in AHK expect the RGB format. That being the case would it not make sense to have PixelGetColor default to RGB or at least have a #PixelGetColor directive to set it and prevent having this contradiction?

Just a thought.

[Serenity]

I'd prefer it if RGB were the default.
_________________
"Anything worth doing is worth doing slowly." - Mae West

[Chris]

The reason there is no directive for it is that the RGB mode seems rarely needed. If you could give some real world examples in which RGB mode is frequently used, that could help justify a new directive.

The reason RGB isn't made the default is to avoid breaking existing scripts.

[Serenity]

RGB is the standard for web graphics; I use RGB to paste values into html directly. Also, neither Photoshop or Paint Shop support BGR mode.
_________________
"Anything worth doing is worth doing slowly." - Mae West

[Chris]

But how does that relate to PixelGetColor and PixelSearch? In other words, what are the common reasons for wanting to use RGB mode with these two commands?

The only reason that comes to mind is to make them compatible with the RGB colors used by GUI and other commands. But the need for that seems too rare to justify a new directive.

[Serenity]

Thats a good point, I've written one script to get the color of the current pixel and send the RGB value to the clipboard but for that script alone simply specifying RGB is fine. I guess I expected it to be standard because it seems to be standard elsewhere.
_________________
"Anything worth doing is worth doing slowly." - Mae West