Select Next button not working

[hafinwala]

Windows 11
The next button is not working. The cursor doesn't move, and the same page is printed.
Based on your response to other queries, I have tried to check if it's an accessibility issue but there is no option to provide permission to the app to control the mouse.

[hafinwala]

Also, is there a way I can click manually on the next button, lets say every 2 seconds and the app just take the screenshots.

[hafinwala]

Ok, so i tried it in different app and it works but strangely it does not work in selecting the next button on VitalSource bookshelf!

[manhtai]

So you're saying vitalsource can somehow detect it's auto clicks and prevent it? Interesting.

[LukeKvamme]

Hey guys, I know it's a couple months later but maybe this will help others if they see this. I also found that the next button was not working, so I used some code from one of my personal projects to try getting the pixels for the next button instead--and it worked just fine afterward.

Comparing the coordinates, the next button (if using the button within the GUI) seems to grab / display the wrong pixels, which is weird because the mouse goes to the right spot during its execution. After plugging in the coordinates that my personal code obtained, it ended up working just fine. So to anyone who sees this, try finding the coordinates of the next button without using the GUI. The program I used uses the pyautogui.position() function from pyautogui.

If you are on a 1440x2560 (2k) monitor, the next button coordinates that worked for me are at (2433, 1386). Hope this helped.

[gritty-Kitty]

Agree with LukeKvamme.

Oddly, on a 4K monitor setup at Portrait on Monitor-3.

PRINTING to maximum width claims to be Rectangle: {92, 353} and {868, 1359} which is "nowhere" near the 4K resolution of 2160x3840, and yet, the program captures the area CORRECTLY, despite not aligning with 4K coordinate system.

The NEXT button, on the other hand, appears to require the REAL coordinates and captures incorrectly. It captured {871.5, 1625} similar to the goofy numbers for the PRINTING area, but mouse was lost somewhere near the middle of the screen. The winning coordinates by manual trial and error were {1960, 3650}.

** So, multiply the PERCEIVED Next capture coordinates by 2.25, and autocorrect.