[1.1.1] TightVNC: click into VNC window does not work --- fixed 1.1.2

Bug #1742389 reported by RaiMan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
Fix Committed
Critical
RaiMan

Bug Description

I am facing an issue while using SikUli function Region.Click(). I am using this function to detect and click on a Region in a Window. But this fails always. The weird thing is when i do Region.highlight(), it hightlights the particular region correctly. Immediately after that i do Region.Click() which is not clicking on the Region. But in logs it shows it had clicked on it, actually it did not.
The Region is in a window inside "TightVNC" App. When the click happens, the cursor just moves outside the TightVNC, but in logs the clicked X & Y dimensions shows a value which correctly maps to the Region to be clicked. I dont understand what is wrong here. Can someone please help me?

Revision history for this message
RaiMan (raimund-hocke) wrote :

At least as a quick fix I added these object methods to VNCScreen (latest nightly 1.1.2):

// flag a Region Location as being on this VNCScreen
Region set(Region element)
Location set(Location element)

// get new Region/Location on this VNCScreen
Location newLocation(int x, int y)
Location newLocation(Location loc)

Region newRegion(int x, int y, int w, int h)
Region newRegion(Location loc, int w, int h)
Region newRegion(Region reg)

so it now gets less ugly:
- no extra method needed

vnc.getRow(3, 4).getCol(1, 3).click()

write as:
vnc.set(vnc.getRow(3, 4).getCol(1, 3)).click()

summary: - [1.1.1] TightVNC: click into VNC window does not work
+ [1.1.1] TightVNC: click into VNC window does not work --- fixed 1.1.2
Changed in sikuli:
status: New → Fix Committed
importance: Undecided → High
importance: High → Critical
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.