Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#712 closed Feature Request (Rejected)

enhanced PixelSearch - search direction & logical mask

Reported by: haura Owned by:
Milestone: Component: AutoIt
Version: Severity: None
Keywords: PixelSearch Cc:


A) Search direction:
For symmetry, support should be included for:

  1. left-to-right, top-to-bottom (default & only current option)
  2. right-to-left, top-to-bottom
  3. left-to-right, bottom-to-top
  4. right-to-left, bottom-to-top

Various software (not just games) use gauges on screen and the ability to efficiently find the top/bottom/left/right extremes of a monochrome area would have high utility.

B) Search using a logical-AND "pixel mask":
Accept X and Y dimensions of a pixel mask. Here, a "pixel mask" is an array of pixels in which _all_ pixels must match the target color for the search to terminate. Shade-variation parameter applies.
Of course this pixel mask must be smaller in X and Y dimensions than the rectangle of pixels being searched.

Sometimes onscreen gauges have gradations or text superimposed and so erroneous matches are possible and these situations can require complex (and slow) functions to be written to avoid false positive search results. Requiring _all_ pixels within a search rectangle to match the target color will provide an efficient program building block for such applications.

C) Search using a logical-OR "pixel mask":
Corollary to (B) only using a logical-OR "pixel mask" and the condition for terminating the search changes to being when _none_ of the pixels in "pixel mask" match the target color. Shade-variation parameter applies.

Note that this yields a _different_ result than the result from a "single pixel at a time" style search.

This is useful for those gauges that taper off or have rounded extremities however, it may _also_ be used to effectively ignore any text or gradations superimposed on a monochrome gauge.

Attachments (0)

Change History (4)

comment:1 Changed 15 years ago by TicketCleanup

  • Milestone deleted
  • Severity changed from Blocking to None
  • Version deleted

Automatic ticket cleanup.

comment:2 Changed 15 years ago by Valik

  • Resolution set to Rejected
  • Status changed from new to closed

It's clear you didn't search the issue tracker hard enough or you would have found #351 which covers the first part of your request.

As for the rest of the request, write your own. We can't possible provide something that is going to make everybody happy so we provide something basic. If you need something for complicated you can build it yourself.

comment:3 Changed 15 years ago by anonymous

Your terse response was not called for.

I most certainly did search for and find #351 before filing this request. #351 showed no disposition details. I suppose I must assume that #351 is not rejected but that it also has no target milestone or assigned owner for implementation.

I did consider referencing #351 but decided not to because it the pixel mask element of my request is what I wished to emphasize. In future I will reference possibly related prior requests and/or submit multiple requests with a narrower focus for each one. Thank you for that piece of learning.

I am sorry to read that pixel mask based searches are not within the target scope of your your planned development. I have already started on a library of my own so thank you for that suggestion.

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.

Add Comment

Modify Ticket

as closed The ticket will remain with no owner.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.