Suppress variables name

Questions and Help
1

Is there a way to achieve this, but still get different variables for each formtoggle?

Option 1? {formtoggle: name=Yes; default=no}{endformtoggle} {formtoggle: name=No; default=no}{endformtoggle}
Option 2? {formtoggle: name=Yes; default=no}{endformtoggle} {formtoggle: name=No; default=no}{endformtoggle}
Option 3? {formtoggle: name=Yes; default=no}{endformtoggle} {formtoggle: name=No; default=no}{endformtoggle}

OR

Option 1? Yes{formtoggle: name=; default=no}{endformtoggle} No{formtoggle: name=; default=no}{endformtoggle}
Option 2? Yes{formtoggle: name=; default=no}{endformtoggle} No{formtoggle: name=; default=no}{endformtoggle}
Option 3? Yes{formtoggle: name=; default=no}{endformtoggle} No{formtoggle: name=; default=no}{endformtoggle}

2

Hi,

Thanks for reaching out. Yes, in this case the second option would be preferred if you want to label each formtoggle as "Yes" or "No", since if you give the actual formtoggle that name, it will be activated at the same time as all others with that name.

You can use notes to wrap around the "Yes" and "No" text so that they display in the preview but are not inserted in the final snippet:

Option 1? {note}Yes{endnote}{formtoggle: default=no}{endformtoggle} {note}No{endnote}{formtoggle: default=no}{endformtoggle}
Option 2? {note}Yes{endnote}{formtoggle: default=no}{endformtoggle} {note}No{endnote}{formtoggle: default=no}{endformtoggle}
Option 3? {note}Yes{endnote}{formtoggle: default=no}{endformtoggle} {note}No{endnote}{formtoggle: default=no}{endformtoggle}

Best regards,
Alexander

3

The goal is to evaluate each option individually. For example, to check whether Option 2 = Yes, I would need to give each formtoggle its own 'name'. That way a simple yes and clean checkfield is not possible. I was wondering whether I could either hide this name, or somehow define a variable in the background linked to the formtoggle.
Alternatively, I would have to use 'Option 1' as the name.

4

Hi,

I think I am a bit confused on your goal. In the case you are describing, what is the problem with using the option as the name of the toggle? If you hide the name, wouldn't that prevent from knowing which toggle you are selecting?

{formtoggle: default=no; name=Option 1?}{endformtoggle}
{formtoggle: default=no; name=Option 2?}{endformtoggle}
{formtoggle: default=no; name=Option 3?}{endformtoggle}

Can you please give me an example of your desired sample output?

Best regards,
Alexander

5

My goal is to use just yes/no options because

1. it looks cleaner, and
2. it’s necessary to differentiate whether a process has been started or not. No activation doesn’t necessarily mean “no.” In case of multiple questions, I need to use Yes1, Yes2, or Process XY + No Process XY (or similar)

I was just wondering if I missed something. Otherwise, I’ll just stick to using the name as the description.

6

Hi,

Thanks for the clarification. Based on what you are describing, I don't think there is another way to do it in Text Blaze.

One alternative is using a dropdown menu for each process/option with a blank option, yes option, and a no option, as opposed to toggles.