starred/WiFiManager

Fork 0

mirror of https://github.com/tzapu/WiFiManager.git synced 2026-04-27 09:05:56 +03:00

[GH-ISSUE #466] can't use lambda expression for setSaveConfigCallback #393

New issue

Closed

opened 2026-02-28 01:25:05 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 01:25:05 +03:00

Owner

Originally created by @liebman on GitHub (Dec 3, 2017).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/466

in my setup() function I have:

    bool save_config = false;
    wm.setSaveConfigCallback([&]()
    {
        save_config = true;
    });

This fails with an error: error: no matching function for call to 'WiFiManager::setSaveConfigCallback(setup()::__lambda1)'

However I also have:

    wm.setAPCallback([](WiFiManager *)
    {
        configColor();
    });

And this works!

Any ideas?

Originally created by @liebman on GitHub (Dec 3, 2017). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/466 in my `setup()` function I have: ``` bool save_config = false; wm.setSaveConfigCallback([&]() { save_config = true; }); ``` This fails with an error: `error: no matching function for call to 'WiFiManager::setSaveConfigCallback(setup()::__lambda1)'` However I also have: ``` wm.setAPCallback([](WiFiManager *) { configColor(); }); ``` And this works! Any ideas?

kerem

2026-02-28 01:25:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-28 01:25:06 +03:00

Author

Owner

@DarkFox commented on GitHub (Dec 19, 2017):

You need to call it like this:

    wm.setSaveConfigCallback([]()
    {
        save_config = true;
    });

Since setSaveConfigCallback doesn't take any arguments.

@DarkFox commented on GitHub (Dec 19, 2017): You need to call it like this: ``` wm.setSaveConfigCallback([]() { save_config = true; }); ``` Since setSaveConfigCallback doesn't take any arguments.

kerem commented

2026-02-28 01:25:06 +03:00

Author

Owner

@liebman commented on GitHub (Dec 19, 2017):

@DarkFox correct, I used this where save_config is a local variable:

    bool save_config = false;
    wm.setSaveConfigCallback([&]()
    {
        save_config = true;
    });

It's supposed to capture the save_config variable so I don't need to make it global as its only used in this one function. Maybe its really a tool chain bug?

@liebman commented on GitHub (Dec 19, 2017): @DarkFox correct, I used this where save_config is a local variable: ``` bool save_config = false; wm.setSaveConfigCallback([&]() { save_config = true; }); ``` It's supposed to capture the save_config variable so I don't need to make it global as its only used in this one function. Maybe its really a tool chain bug?

kerem commented

2026-02-28 01:25:06 +03:00

Author

Owner

@DarkFox commented on GitHub (Dec 19, 2017):

Yeah, I was in the same situation. I decided to just make it a static on my wifi handling class. It's not like I've got multiples of it anyway. Though it is poor style.

@DarkFox commented on GitHub (Dec 19, 2017): Yeah, I was in the same situation. I decided to just make it a static on my wifi handling class. It's not like I've got multiples of it anyway. Though it is poor style.

kerem commented

2026-02-28 01:25:06 +03:00

Author

Owner

@tablatronix commented on GitHub (Feb 1, 2018):

Should we not just add WiFiManager* to all callbacks?

@tablatronix commented on GitHub (Feb 1, 2018): Should we not just add WiFiManager* to all callbacks?

kerem commented

2026-02-28 01:25:06 +03:00

Author

Owner

@liebman commented on GitHub (Jun 19, 2018):