nekosu

Sorry, I've been a little busy these days. I'll start checking this right now.

There is a problem in your first solution. The PreferencesPage(base class of PreferencesPageTemplate) binds some actions of PreferencesWindow(e.g. reset, default, apply). When we reuse it for object in a popup...

After some thinking, I discover that we bind the data and ui too tight. Maybe we should remove ui, default value, etc. from settings.json and declare it in code. And...

We can refactor PageTemplate into a widget so that we can create a object wrapper and use it. After all, the problem is that how to properly treat the objects....

I think it's ok. If really want to move it out, maybe add support for os-specified param in setting 🤔

> Or we can try to find a different way to implement #733. Maybe a widget contains a HBoxLayout, with a QCheckBox and a clickable label? It should work.

I think there should be some caculation problems but I haven't found it.

Then formatter could be reimplemented by this. Maybe we need a method to customize ui in setting dialog.

@sonulohani It seems that the problem is the QCodeEditor cannot provide an option for this. So you can add an issue in cpeditor/QCodeEditor. After that issue closed, we can restart...

I think you two just talk about the same thing: Add an option/logic to auto run all testcases(even passed before) before submit, or a button to do it(in different to...