Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
CCManager settings dialogue plan
oBFusCATed:
How do you plan to handle the per-plugin panels?
Are they going to be a part of the CC settings or every plugin will register a separate item in the list in the dialog?
Alpha:
Plugin settings pages I plan to leave as is. They are still their own plugin, so I see no reason not to.
As for panels (such as scope and symbol tree), I hope to create a generic interface that plugins can share someday.. but that will have to wait.
oBFusCATed:
--- Quote from: Alpha on November 06, 2014, 08:01:29 pm ---Plugin settings pages I plan to leave as is. They are still their own plugin, so I see no reason not to.
--- End quote ---
This will be quite messy from the user friendliness point of view, but I guess it is OK as first step.
Alpha:
Has anyone timed how expensive (or cheap) ConfigManager::ReadXXX() calls are? Should I avoid using them during CC operations (caching settings instead)?
oBFusCATed:
It depends how often they are called. If it is million times per second, I suppose it will make a difference, otherwise I doubt it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version