SWAP$(expession$, string1$, string2$)

Give it a try, it costs you nothing !
lyizb
Posts: 179
Joined: Fri Feb 12, 2021 8:23 pm
Has thanked: 82 times
Been thanked: 60 times

Re: SWAP$(expession$, string1$, string2$)

Post by lyizb »

Thank you--that is useful to examine. Everything I have done so far has been bottom up (over the course of 20 years in this location), but it looks like I would benefit from a top down approach.

All my nodes so far have had a capital letter as an ID, e.g., "A" through "Z", but I've reached the point where I need to add "a" through "z". And I need to integrate logging of restart causes, watchdog handling, and ESP-Now messaging. Some older devices use TCP but since Annex doesn't support that, I've also used UDP. ESP-Now appears to be a better choice--at least in parallels as I rework things.
User avatar
Electroguard
Posts: 1028
Joined: Mon Feb 08, 2021 6:22 pm
Has thanked: 335 times
Been thanked: 378 times

Re: SWAP$(expession$, string1$, string2$)

Post by Electroguard »

We all have to start from ground up initially while we get a feel for where things should be going and how they might get there.
But my continued development keeps resulting in a working but ever-uglier inefficient warty hodgepodge.
I've been making do like that for years, until the recent discovery that I can integrate espnow quite easily with my existing easynet, but it will result in an even bigger hodgepodge.
So with the benefit of Franchesco's latest excellent multi-tab update I decided it was time for a planned top-down rewrite to remove the warts and smoothly include new features. It means a lot of self-inflicted debugging, but that's made easier by being able to selectively turn things off.

My espnow devices all have a static IP node address even though they might end up out of pingable range. By using the node numbers, it offers up to 250 unique addresses including for espnow devices (eg: my espnow speechserver can be targeted by name or by its node address of 42).
Post Reply