Wouldn't It make more sense to have the highres fix option show second instead of first pass resolution?

[Dolyfin]

I'm generating random seeds until I find one I desire to have a higher resolution of. It currently takes editing 4 resolution boxes in the basic workflow back and forth which is very tedious. Doing 512x res generations to save time, then doing the highres generations with a good seed.

current:

1. find a good 512x512 image,
2. check highres fix,
3. edit normal W x H to 1024x
4. edit first pass W x H to 512x
5. save result
6. uncheck highres fix,
7. edit normal W x H back to 512x
8. repeat (without step 3)

If Highres Fix showed the second/final resolution, and the normal W x H input was used as first pass when it is checked. It would be much more (although different in intuitiveness) faster to use.

[AlUlkesh]

The intuitiveness might indeed be a problem. And you'd have to think about which one to save to the png-info or copy to other screens.

How about a button that switches the resolutions and the highres-checkmark?

[Gerschel]

My preset manager allows you to stack presets.
https://github.com/Gerschel/sd_web_ui_preset_utils.git
Detail save, choose width and height as option, save one as 512x512, do another for 1024x1024. Save other settings under another name.
Then you can apply one for other options, then apply for size. When you want to switch a few things, apply the setting for that, it will adjust the settings you predertemined in Detailed tab.

Caveat. If you have scripts that have same labels, such as Width/Height, they will clash, either disable those scripts in the extensions tab, or go into their script file and modify their label to make it unique. Don't blame me, blame them for not implementing unique identifiers, to them to add unique element id's so I have a reason to update to use those. Make sure to do it for built-in scripts, so you can get Mask Blur clash resolved too.