Different icons of actions with config options

[Pako]

Would be very useful, if in config tree was the different icon the actions,
which they have some options configuration.
Pako

[Bitmonster]

I actually haven't understood you. Please try to describe it in another way.

[Pako]

Situation:
1) I add new plugin with "createMacrosOnAdd = True" option to config tree.
2) Now I don't know, which Actions have options of configuration and which Actions have no options of configuration.
3) I execute a action, which have options of configuration (but I don't know it), and I get error message:
"TypeError: __call__() takes exactly 2 arguments (1 given)"
4) Now I know, that I must make configuration, but not everybody know ...

My idea:
Action with options of configuration have a "icon 1" and
action without options of configuration have a "icon 2".

Pako

[Bitmonster]

No bad idea, but we would need a new icon background, that is different but also looks like the other action icon background.

[Pako]

And only different colour variant would was perhaps ?
My other idea:
Would be possible, to EventGhost after insert plug-in made automatic configuration with using default values ?
Pako

[Bartman]

Would be possible, to EventGhost after insert plug-in made automatic configuration with using default values ?

So just suppressing the config dialog? You can already assign default values as a plugin developer.

[Pako]

You can already assign default values as a plugin developer.

Certainly, but I have in view not me and my plugins, but common user and all plugins.
Anymore is here alternative solution:
1) Add plugin with "createMacrosOnAdd = True" option to config tree
2) EG step by step opens all configuration dialogs and user must either confirm default value or set the other
Pako

[Bitmonster]

Anymore is here alternative solution:
1) Add plugin with "createMacrosOnAdd = True" option to config tree
2) EG step by step opens all configuration dialogs and user must either confirm default value or set the other
Pako

I have thought of this in the beginning, I guess the user will only use a small part of the available functions of the plugin in the end, and to ask him to configure every action would be much to bothersome. If a plugin has actions that won't work good with default parameters, it should not use createMacrosOnAdd. This option is mainly intended for plugins that only have "straight" actions.