Can't reopen advanced conditions if condition can't be graphically represented

Found an unfortunate scenario with the conditions editor. If you type a condition 'as code' that can't be represented in the graphical editor above, you can't re-open the conditions window after you close it. This means if you want to edit it, you have to recreate the trigger from scratch.

For instance, add this to the 'as code' portion...

focused_window_x >= focused_screen_x

You'll see it evaluates to true or false accordingly, meaning it's working as expected. However, since focused_screen_x can't be represented in the 'value' box in the visual editor, you can't reopen the editor. Clicking the button does nothing.

My suggestion would be to have the conditions window show either the simple visual editor or the code window, not both, then let the user switch between them as needed. This way for cases like the above, it could just show the code editor directly.

This would also stop the somewhat annoying tentency of it to 'interrupt what you're typing', to reformat it or show an error, while you were mid-edit, sometimes causing you to lose your work. There, a suggestion would be where you're currently displaying 'Currently true' or 'Currently false', just say 'Invalid condition' and let us keep editing it until it's fixed/corrected, rather than trashing our work. But don't ever trash what we're typing!

Note: I'm filing a separate issue for the conditions editor itself not respecting actual conditions, so look for that one shortly.