[1.1.0] Mouse.move(x, y): seems to block subsequent usage of Region.click()

Bug #1569721 reported by RaiMan on 2016-04-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sikuli
High
RaiMan

Bug Description

I'm using Sikuli V1.1 with Java 1.7. (I'm calling the Sikuli Java SDK)

I just added a little code to move the mouse and "click" ( Mouse.down()) followed by Mouse.up() ) to select an item from a combo box. It seems to work fine however the next operation presses the submit button with a {region}.click() operation and that hangs. It never returns.

Thanks,
Spence

RaiMan (raimund-hocke) wrote :

*********** from the related question

// This opens the list of items in a combo box.
        Pattern header = new Pattern(_EDIT_ACCOUNT_DIALOG);
        header.similar(0.80f);
        Region tmp = exists(header).grow(0, 0, 0, 350);
        tmp.find(_ACTIVE_COMBO_BOX).click();

// This selects one of the items in the combo box.
      Mouse.move(0, 50);
      Mouse.down(Button.LEFT);
      Mouse.up();

// This code then clicks the dialogs "Submit" button.
        Pattern header = new Pattern(_EDIT_ACCOUNT_DIALOG);
        header.similar(0.80f);
        Region tmp = exists(header).grow(0, 0, 0, 350);
        tmp.click(_SUBMIT_BUTTON); <<<---- This is where the problem occurs. The click NEVER returns.

Changed in sikuli:
status: New → In Progress
importance: Undecided → High
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers