| View previous topic :: View next topic |
| Author |
Message |
Chris
Site Admin
Joined: 02 Mar 2004
Posts: 10467
|
 Posted: Mon Oct 11, 2004 4:12 pm Post subject: |
 |
|
| Although it's easy for you, me, and other heavy ahk users to update our scripts, the thing that bothers me is the more typical users who download an update 3 months from now but don't read the large amount of accumulated changes in the changelog. They then wonder why all their pixel scripts are broken. Or worse: why their pixel scripts go crazy and click on the wrong objects entirely, possibly causing who-knows-what to happen. |
|
| Back to top |
|
 |
BoBo
Guest
|
| Posted: Sat Oct 16, 2004 11:18 am Post subject: |
|
|
Thought that the Pix command could work based on a default directive (if no other has been set).
#PixBGR (default)
#PixRGB
#PixHex
etc.
So no existing script would have to be changed as all of them lacking non-default directives.
Thx Chris.
 |
|
| Back to top |
|
|
Chris
Site Admin
Joined: 02 Mar 2004
Posts: 10467
|
| Posted: Sat Oct 16, 2004 12:13 pm Post subject: |
|
|
I understand #PixRGB, but not #PixHex. The hex format is already in effect in the latest version, which leaves only two formats: RGB (used by SplashImage and Gui) and BGR (used by Window Spy, PixelGetColor and PixelSearch).
I haven't heard any good reasons yet for adding #PixRGB. If it were added, it might call for Window Spy to diplay both formats, which would make it more confusing for beginners.
If you have a strong preference for RGB format, please describe your reasons (such being able to interact with HTML colors). Thanks. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Register
Profile
Log in to check your private messages
Log in
