X 1.0rc1 Observe() not working (0.10.2: on Windows)

I have a problem with observe too but it's unrelated to windows.
Adding this line at the top of SikuliEventManager::update fixed it for me...

cvCvtColor(screen_image, screen_image, CV_RGB2BGR);

This line is in the FinderProxy::createFinder function which is used by find() but not observe()

You can see see that the image that's passed to this function via observe() is faulty by adding cvSaveImage("/tmp/t.png", screen_image); at the start of the update() function.

The cool thing about this is that I've noticed that it still matched the image with all the wrong colors but it just gave it a lower score.
Maybe you're using a different image in windows?

Here's a patch for various problems I've had with observe()

* wrong colors being used, not getting the same matches.
* when no similarity is specified, similarity is set to 0.8 (MIN_SIMILARITY in event-manager.cc) which is different than the default 0.7 with find(), etc.

I am using ubuntu x64

just committed niknah's patch. (r324, r325)
Thank you, niknah!

This is still broken on Sikuli-X-1.0rc1-win32

I am running Windows Vista.

The observer has some fundamental problems. We've had a new implementation and will incorporate it into the next release.

I Will be waiting for this thing to be solved on windows.

Thanks.

a temporary solution, if you want to wait for changes in a region:

theRegion = the-region-to-observe
img = capture(theRegion)
for i in range(10):
   if not theRegion.exists(img,0): break
   wait(1)

""""a temporary solution, if you want to wait for changes in a region:

theRegion = the-region-to-observe
img = capture(theRegion)
for i in range(10):
   if not theRegion.exists(img,0): break
   wait(1)""""

But this stops your script, and avoids it to do other things during this search.

The good thing about observe it's to run it in background. At least for me

@Danielo: """"a temporary solution, if you want to wait for changes in a region:

yes, when writing that, I knew what you really wanted: ... if you want to WAIT for changes...

but I thought, that you might spend some time with the rest of your workflow AND have a chance to test it.

Tip: the above solution packed in a def() and then threaded runs in background :-) (see your other question)