This is doing my head in what am I doing wrong or is a bug in 2.1.1.0?

I want to add a new config parameter to a module so that when I add the module as a component on a page I can pass in some extra config. Done this lots of time. I add the new parameter it to the module.config and the option appears in the module parameter list in the Kooboo admin pages. However it is not visible to my module through ModuleInfo.ModuleSettings.

To actually make it visible to my module code I have to remove the module component from the page/s where I am using it and add it back. I don't need to leave the Page admin dialog, just remove the module and add it back.

This is what makes me think it is a bug in the Kooboo as this workaround is obviously not workable on a large site. I also don't remember having this problem in earlier version when I've used module parameters quite a lot

If I'm doing something stupid I'd love to know! What do you think?
Thanks

Ah yes this makes perfect sense now. I saw the new parameter in the component parameter list but I didn't press Save because the default value is what I wanted. And because it appeared there in the list I assumed that it was saved already

My other modules have many parameters that I was constantly changing in testing so this issue never came up, or if it did come up then it probably mysteriously sorted itself out as I made other changes, inadvertently saving the new values in the process

It's not really a bug in my opinion but it would be useful if somehow you could indicate in the component screen the parameters that have not saved in the database (that have come over from module.config changes)

Thanks Jifeng, that's great