TcMenu designer 2.1 was released yesterday, this release goes back to a single code base, with builds for all platforms. You can watch the video that describes the main changes and rationale.

It is fully compatible with the store version, and if there's anything you're missing from the new version, or there's a workflow that doesn't work properly, feel free to either raise an issue or report it here in the forum.

Release link: https://github.com/davetcc/tcMenu/releases/

You can also see our latest blog post on the background too: https://www.thecoderscorner.com/team-blog/thoughts/q2-2021/tcmenu-menu-designer-2.1-released/

UI 2.1.2 was released today with a few minor fixes, after a week of testing.

Available at https://github.com/davetcc/tcMenu/releases/

With this release of the UI fixing up a few bugs after even more heavy testing, we are imminently going to release tcMenu library V2.1. The plan is:

1. Let 2.1.2 bed in for a few days while we get the documentation ready on our site.
2. Flip the link and make library 2.1 current, and 1.7 the previous.

We don't want to repeat the 1.7 mistake where the documentation was not ready when we released it.

We've released a release-candidate of tcMenu library for 2.1 as we've tested everything fully now, and are happy for people to start using it.

For those who want to try it now, please go ahead, but be aware the documentation is still being worked upon. Instructions are provided in the library release page. But basically it's a case of download the library and switch streams to BETA in Edit -> General Settings.

It will become a full release by the end of this week, once the documentation is ready.

https://github.com/davetcc/tcMenuLib/releases

In fact I'll do a top level topic for the Uno mode, as some others could hit the same issue.

TcMenu 2.1.3 plugins and library are now the main stable branch as of now. We've tested it as best that we can but we cannot ever capture everything. Please try 2.1.3 and give us any feedback here, if you run into problems it's quite easy to revert to 1.7.

You can stay on 1.7 quite easily, there's another top-level thread showing how to do this.

Why did it jump to 2.1.3 instead of 2.0? Because we did at least 10 internal builds, tested and better tested them, fixed anything that we could, and tried again.

We stand ready to answer any usability questions around themes in the designer UI, don't be afraid to ask!