2.3 has been fully released. Both Libraries and UI.

The fix was released earlier today, 2.3 of both IoAbstraction and tcMenu are available now, I have built and tested a menu on ESP32S2 with an OLED screen and rotary encoder.

TcMenu 2.3 both library and UI have been released today. There are several major steps forward in this version.

Firstly, it has preview support for embedded Java on Raspberry PI. It can automatically build a UI that can then be highly customized. This support is in preview.

EmbedCONTROL has gone through a heavy refactor, and clean up. We'll continue to clean up and improve it, but the heaviest of the work is done.

Menu In Menu can be used on Java boards, allowing an embedded java device to embed many remote menus within a single device.

Many bugs have been fixed, libraries upgraded, and usability improvements applied.

https://github.com/davetcc/tcMenu/releases/tag/2.3.0

Make sure to update IoAbstraction and tcMenu libraries in your Arduino IDE at the same time!

IoAbstraction 2.3 was released today, it supports rotary encoders that are not on an interrupt pin. It also better support ESP32S2 boards.

I've actually got a couple of hours in and tested IoAbstraction and tcMenu library on all platforms, they will be in Arduino library manager and platformIO next time they poll.

The 2.3 UI has a lot of fixes in it too and will follow soon.

Once we've done a bit more testing we'll release the mac version for the beta. It takes a bit of effort to notarize and sign the executables so I'll make sure it passes a smoke test first.

You could use the latest version of tcMenuLib library from GitHub without any problems. Just backup your current version and pull down the latest from there. It's the library that is causing the problem here and it should work fine with 2.2 designer for now.

Will be fixed in IoAbstraction 2.3 due very soon. It also finally sorts out the annoyance where encoders always needed pinA to be an interrupt capable pin.

See

https://github.com/davetcc/IoAbstraction/issues/152

The library should be in a good state now, I am testing it already, for what you want it may be better than 2.2. You'd just need to take a zip of the latest from GitHub.

One of the issues with lists in 2.2 was around selection. In 2.2 we focused (too much) during testing on touch screens (as they were pretty new at that point), and in all honesty, list items on an encoder did not work that well in 2.2.

In 2.3 I've tested different sizes of list in greater detail and they all seem to work. I'm starting the release testing now on 2.3 and will ensure that lists are stable in all cases.

Nothing actually wrong. But you should be able to drop this line, you could try commenting out and should still run:

menuMgr.setEepromRef(menuMgr.getEepromAbstraction())

Reason: it shouldn't be needed, it will already have been set within setupMenu(). You just need to make sure that any EEPROM usage is after setupMenu() is called as it's not initialized before that.

If you're on ESP32-S2, there are some known issues at the moment. After I get 2.3 of the designer out my plan is to go back and add proper support for ESP32-S2.

Up until recently some popular display libraries did not work well with them either and there wasn't much demand. Now that seems to be changing. I have a device to hand so it is just time..

There is a bug with lists that have only 1 item in 2.2, it is fixed in 2.3 which is about a week or so away.

Unfortunately, all my lists so far had many items so I didn't notice this bug.

Have you set the EEPROM abstraction up somewhere? Either from the code generator settings in designer or at the top of your sketch before calling load?

https://www.thecoderscorner.com/products/arduino-libraries/tc-menu/menu-eeprom-integrations/

Please could you provide an isolated sketch that re-creates this issue, along with the version of tcMenu, IoAbstraction, TaskManagerIO and SimpleCollections libraries that are installed?

The best way to get version info is from Help / Diagnostics menu in the designer.

In fact there is even an example dedicateed to taking over the display called IIRC takeOverDisplay.

Firstly, please understand that this is an open-source project, there will be gaps, and there will be times you'll need to do a little digging.

There are a lot of examples and they are tested by me and many other people with every release that is made, although they should come up if your hardware matches and be easily modifiable if not, and between them, they demonstrate the vast majority of features.

Runtime lists (and custom choice items) are demonstrated in many examples, EspAmplifier may be the most complete in terms of how they are used. They are also documented here: http://thecoderscorner.com/products/arduino-libraries/tc-menu/menu-item-types/list-menu-item/

Firstly, please understand that this forum is run by volunteers, we simply can't process things ASAP.

The menu starts out initialised and running, so once you build it onto a board it will immediately start if everything is configured correctly.

You take over the display when you want to use it yourself. You'll be called back in what's often referred to as a "game loop" where you refresh the screen if you need to. It will give you the current value of the encoder and also if the button has been pressed. This suffices for some but not all. When you need more control over the input, you can manually provide the input facilities yourself.

Take over display: http://thecoderscorner.com/products/arduino-libraries/tc-menu/renderer-take-over-display/

Providing input to tcMenu manually: http://thecoderscorner.com/products/arduino-libraries/tc-menu/menumanager-and-iteration/#controlling-the-menu-items-manually