On Thu, Jul 11, 2019 at 5:43 PM Christopher Pisz via Boost-users wrote:

boost::asio::steady_timer...only performs the callback once and does not fire again. I am not sure what I am doing wrong. Any suggestions?

That's how it is supposed to work. If you want it to fire again, call async_wait again. Regards

On Fri, 12 Jul 2019 at 03:43, Christopher Pisz via Boost-users < boost-users@lists.boost.org> wrote:

I am trying to perform a task on an interval and I made a POC using boost::asio::steady_timer. When I debug it, it only performs the callback once and does not fire again. I am not sure what I am doing wrong. Any suggestions?

Why would it 'fire' more than once, there is no loop? int main() { boost::asio::io_context ioContext; auto pooper = Pooper(ioContext); while ( true ) { pooper.Run(); ioContext.run(); } std::cerr << "Exited..." << std::endl; } Now it will poop till you drop. Other than that, this appears to be [you don't state what you would like to achieve] some kind of event-loop, where you suspend till the next frame. You can suspend the current thread with std::this_thread::sleep_for ( std::chrono::milliseconds ( milliseconds_to_sleep ) ); or std::this_thread::sleep_until ( some_time_point_in_the_future ); using just std-lib facilities. Having said that, have a look at SFML ( https://www.sfml-dev.org/), which has all those things, event-loop, event-polling, mouse, touch, joy-stick, sound, image rendering, window creation etc. degski -- @realdegski https://edition.cnn.com/interactive/2019/06/middleeast/saudi-teen-death-pena... "Anyone who believes that exponential growth can go on forever in a finite world is either a madman or an economist" - Kenneth E. Boulding

It looks like my problems aren't with the timer at all. This listing pretty much mimicked example 3. It ends up that my problem is that if you click on a console window in windows 10, the program ceases execution when it enters "quick edit" mode. I was not aware of that new behavior and thought the timer was not working. The program run fine, as is, if you don't touch the mouse. Sorry, false alarm. On Thu, Jul 11, 2019 at 7:42 PM Christopher Pisz wrote:

I am trying to perform a task on an interval and I made a POC using boost::asio::steady_timer. When I debug it, it only performs the callback once and does not fire again. I am not sure what I am doing wrong. Any suggestions?

// DoMouseEvents.cpp : This file contains the 'main' function. Program execution begins and ends there. //

#include #include "boost/asio/deadline_timer.hpp" #include #include <chrono> #include <iostream>

class Pooper { boost::asio::io_context & m_ioContext; boost::asio::steady_timer m_timer;

public: Pooper(boost::asio::io_context & ioContext) : m_ioContext(ioContext) , m_timer(boost::asio::steady_timer(ioContext)) { }

void Run() { m_timer.expires_from_now(std::chrono::seconds(5)); m_timer.async_wait(boost::bind(&Pooper::OnTimerExpired, this, boost::asio::placeholders::error)); }

void OnTimerExpired(const boost::system::error_code & error) { if (error.failed()) { std::cerr << "boost error: Failed" << std::endl; }

std::cout << "Poop" << std::endl;

try { // Move the mouse int x = 500; int y = 500; if (!::SetCursorPos(x, y)) { int errorCode = GetLastError(); std::cerr << "SetCursorPos error: " << errorCode << std::endl; }

// Left button down x = 65536 * 500; y = 65536 * 500; ::mouse_event(MOUSEEVENTF_ABSOLUTE | MOUSEEVENTF_LEFTDOWN, x, y, NULL, NULL);

// Left button up x = 65536 * 500; y = 65536 * 500; ::mouse_event(MOUSEEVENTF_ABSOLUTE | MOUSEEVENTF_LEFTUP, x, y, NULL, NULL);

m_timer.expires_from_now(std::chrono::seconds(5)); m_timer.async_wait(boost::bind(&Pooper::OnTimerExpired, this, boost::asio::placeholders::error)); } catch (std::exception &) { std::cerr << "An exception occured." << std::endl; } } };

int main() { boost::asio::io_context ioContext; auto pooper = Pooper(ioContext); pooper.Run(); ioContext.run();

std::cerr << "Exited..." << std::endl; }