Opened 17 years ago
Closed 17 years ago
#40 closed Feature Request (Completed)
Pixel functions should accept HWND
Reported by: | Valik | Owned by: | Jpm |
---|---|---|---|
Milestone: | 3.2.11.2 | Component: | AutoIt |
Version: | Severity: | ||
Keywords: | Cc: |
Description
The following pixel functions should accept an HWND:
PixelCheckSum
PixelSearch
PixelGetColor
Adjust PixelCoordMode options:
0 - Removed, no automatic "active window" stuff.
1 - Default, unchanged. Absolute coordinates for the screen if no HWND supplied. Absolute coordinates relative to the window if an HWND is supplied.
2 - Only valid with an HWND, relative to the client area of the window.
This is a script breaking change for those using the "active window" functionality.
Attachments (0)
Change History (8)
comment:1 Changed 17 years ago by Valik
- Type changed from bug to feature request
comment:2 Changed 17 years ago by hiyoal
comment:3 Changed 17 years ago by Valik
- Milestone Future Release deleted
comment:4 follow-up: ↓ 6 Changed 17 years ago by anonymous
I think we can have a non breaking strategy with syntax like
- Pixel...( [HWND,] ...)
or
- Pixel...( ... [,HWND])
personnaly I suggest 1. but if AU3Check or AutoIt4SCite is in trouble with this syntax we can adopt 2.
comment:5 Changed 17 years ago by Jpm
anonymous was me
comment:6 in reply to: ↑ 4 Changed 17 years ago by Valik
Replying to anonymous:
I think we can have a non breaking strategy with syntax like
- Pixel...( [HWND,] ...)
or
- Pixel...( ... [,HWND])
personnaly I suggest 1. but if AU3Check or AutoIt4SCite is in trouble with this syntax we can adopt 2.
It'll be #2. I'm not going to start something with #1. I do not like "skip-able" parameters. They are too confusing. A particular argument should always take the same data-type and not try to auto-deduce context based on the data-type.
comment:7 Changed 17 years ago by Valik
- Owner changed from Valik to Jpm
- Status changed from new to assigned
- Version 3.2.10.0 deleted
comment:8 Changed 17 years ago by Jpm
- Milestone set to 3.2.11.2
- Resolution set to completed
- Status changed from assigned to closed
Added in version: 3.2.11.2
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Thank you for this!! This is a really good idea and it would enable bot makers to increase their bot making abilities so that everything could be done using de-activated windows.
Hiyoal