cstate | 🔥 Open source static status page | Content Management System library

This script will instantly read values typed into your fields and will update the full address dynamic field.

You also need to add id to your dynamictext [dynamictext address-full id:addressfull]

I tend to develop these kind of algorithms by starting with a 'dumb' brute-force algorithm and then optimize it further

You could implement this in a "brute-force" way by a kind of Breadth-first search algorithm, where you are going to just:

• click all buttons on the initial state (4 options)
• for all of the resulting states, you will click all buttons again (16 options)
• etc. where you constantly check whether you reached the goal state.

Something like this:

How you access state in a dialog will depend on the scope of the state.

If the state is scoped to the dialog then you should be using dialog state. More specifically, you should be using the state property of the dialog's associated dialog instance. There's some discussion of that in a recent answer here: Dialogs keep their variable values in new conversation in MS BotFramework v4

(Read about dialog instances here). Anything you want your dialog to keep track of, you should put in the associated dialog instance's state object, and the best place to see examples of how to do that is in the SDK source code itself. For example, you can see how a waterfall dialog keeps track of things like its custom values and what step it's on:

As i said in the comment, you're missing the condition of the country in your states selection.

When you're compiling your command into update_command you are storing this as a Tuple:

When you don't have the requirement of writing data to different files, the next command would work:

Few things to fix/improve.
I'll start off with the actual problem, and then go over stuff you should/could improve.

So the actual problem, every time you run you timer, you set the zoom_toggle variable to be true. So yeah, not much help trying to do any toggles when the value is reset every time.
Move the definition to be at the top of the script, or due to how forgiving ahk is, you could actually entirely skip declaring the variable. That way when it's first used, it's created with the default value of nothing, which evaluates to false.

And now onto other fixes/improvements.
Location of your #directives.
Good/common practice is defining these types of #directives at the very top of your script.

Usage of WinGetPos to get screen width/height.
You could use the A_ScreenWidth and A_ScreenHeight variables to easily get your screen width and height.

Missing return that should end your auto-execute section.
When you launch the script for the very first time, there is nothing that stops the code execution from falling through all the way to your timer's callback label.
Nothing bad will result of this in your case, but for future reference, you don't want this to happen. Use a return to stop code execution and end the auto-execute section.

Redundant code
There is no need to set CoordMode every time you run the timer. Move this command to be at the top of your script.
In your send command, there is no need to wrap - inside { }. That is only done to escape characters that have special meaning in a send command, and - has none. In special cases you may even encounter unwanted behavior by doing this. More about this in the documentation.
Why are Xmax and Ymax being created? They're doing nothing for us?

Usage of Send instead of SendInput
SendInput is faster and more reliable. Should almost always be used over Send.
You can specify SendMode, Input at the top of your script to turn all Send commands into SendInput. Personally I prefer just writing out SendInput.

Legacy code
Technically nothing wrong with using legacy code, but it's definitely not recommended. Compatibility with future AHK versions is non-existent as well. Expression syntax is what should always be used nowadays.
Use the function GetKeyState() instead of the legacy command.
Use the non-legacy operators (&&, ||, etc) instead of legacy AND, OR, etc. Always use := instead of =. Legacy assignment is never used.
Usage of a label is pretty much legacy as well. Should replace with a function, but then I should ensure you understand function scopes as well. If you want, I can.

Here's your revised code:

Something like this should work - I refactored a little bit.

Compiled but not tested.

For first query, You can try below -