AutoHotkey Community

Hi,

I think there are often cases where some options in a GUI are dependent on one option/checkbox, so that is senseless to let a user alter options that won't have an effect if this option/checkbox is not set true. With a g-label and Gui,Control it's easy to implement this, but for bigger GUIs it's a lot of work. Maybe it could be done more easily when add an option to Controls to bind them to one option. This binding will automatically disable all dependent options if the checkbox is not checked and will enable them if the checkbox is checked.

Maybe this syntax could be used:



btw. is there a way to avoid those "vVariable Checked%Variable%" and "vVariable, %Variable%"-constructs? Isn't that the way a GUI should always be used?

_________________
Tekl

I think this falls into the category of scoring low due rarity of use + large code size. If anyone else would definitely use this feature, please post here. In any case, I'll put it on the list for future consideration.

Thanks for the suggested syntax.

It's a great idea but implementing it would break existing scripts. However, corrupt suggested having a "reverse submit" command that would update each control with the current contents of its variable. Hopefully it will suffice for the purposes you have in mind.

Hi Chris,

Corrupt's idea is really brilliant and more flexible, because so you can undo settings while gui is active. In my case it would be a bit confusing. My big GUI takes some time building, so I decided to improve the 'feeled' performance by early showing the GUI, but let the user see how it is built. So if use a reverse submit the user will the first default-values which will change after the gui hast finished building. Hmm... maybe if a reverse submit is called before creating the first control it could create them directly with the variable-content. Or add a special option:

Gui, 2:+DefaultToVariableContent (maybe a better understandable word)

Thanks for your fast replies

_________________
Tekl

Great idea. I'll try to do it as long as it's not overly large in code size.