if image is not found, match score is 0, but keyword should say that image is not found

Nobody has claimed this yet.

due i'm moving from window to linux the same tests , i make a mistake with the use of the \\ or // so, in windows, this path works

${IMAGE_DIR} ${CURDIR}\\img

but in linux, it should to be

${IMAGE_DIR} ${CURDIR}//img

so, when i try

Screen Should Contain image.png

the keyword fails, but the reason is that image.png is not found in ${CURDIR}\\img path , and no that screen doesn't contains image.png

i think the keyword should return a special message if the image is not found.

tips :
to make the path operative system indipendent, we can use /

@rainmanwy what do you think? i'm your worst nightmare? :)

Start by locating the implementation and tests for the Screen Should Contain keyword, then reproduce the missing-image case with the ${IMAGE_DIR} path shown in the issue. Check how a match score of 0 is currently reported. Done means a missing image produces a distinct, accurate message rather than implying that the image was absent from the screen.

Written by the indexing model from the issue text.