48DESIGN

Does that mean that it's then also no longer limited by VRAM but normal RAM instead?

> There's an option here for scripts to advertise limits and locking of the samplers Can you point me to the right file/line? I also didn't see anything about disabling...

Thanks @dfaker for the proposal! Instead of `compatible_samplers`, I named it `ui_restraints`, and it returns an object with a `methods` property that holds an array of allowed methods. That way,...

> Couldn't it just use the CFG Scale then and we wouldn't need to link the UI elements? Or extending on that question: Can we really be sure that no...

Due to said concerns, I decided against implementing the linking between default and script UI elements. So this includes the sampling method restriction only, but it's usable in other scripts...

Wait - now we have unnecessary code in there. I didn't know you had already prepared anything that you wanted to merge into this PR. So my code from 19...

If a script doesn't provide the new def, nothing will change. I had it implemented frontend-only at first, but I thought it was a good idea to have it available...

> Shouldn't it say `ui_restriction` rather than `ui_restraint`? I'm not a native speaker, so if there's a difference I didn't intend anything by it and would be totally fine with...

Thanks for having my back @JustMaier, but wouldn't your proposal be more likely to break anything or at least be more complex to prevent breaking anything instead of the additional...

Yeah, having it all under `ui` would probably make sense! My second paragraph regarding the volume of code changes and JS was targeted towards @AUTOMATIC1111