When "Use another path for incomplete torrents" in qBt settings is checked and the corresponding choice in this dialog is

1. "Default": It should fill the (disabled) field with the incomplete save path that will be used (now it's empty)
2. "Yes": This is just a suggestion because currently it follows the GUI behavior. When the incomplete save path has not been overwritten here, IMO it should also fill the field with actual text and not just placeholder text with the incomplete save path that will be used. Why? I think it's easier to change a part of the path than to write the whole thing. I doubt that people type drastically different save paths often where the current way is more convenient.

2. IMO it should also fill the field with actual text and not just placeholder text with the incomplete save path that will be used.

Note that it now allows you to override whether or not an incomplete path is used without specifying a path itself (i.e. use default incomplete path).

When "Use another path for incomplete torrents" in qBt settings is checked and the corresponding choice in this dialog is

1. "Default": It should fill the (disabled) field with the incomplete save path that will be used (now it's empty)

Fixed! Another good catch.

2. "Yes": This is just a suggestion because currently it follows the GUI behavior. When the incomplete save path has not been overwritten here, IMO it should also fill the field with actual text and not just placeholder text with the incomplete save path that will be used. Why? I think it's easier to change a part of the path than to write the whole thing. I doubt that people type drastically different save paths often where the current way is more convenient.

I agree with this. I've switched the behavior.

Note that it now allows you to override whether or not an incomplete path is used without specifying a path itself (i.e. use default incomplete path).

This is true, though I think it's not intuitive for users. They may not expect that leaving the field blank will use the default path. At first I thought it was a bug that the GUI allowed using a blank path, until I looked at the code.

This is true, though I think it's not intuitive for users. They may not expect that leaving the field blank will use the default path.

If so, wouldn't it be better to simply add some explanation label next to it rather than making this feature inaccessible?

This is true, though I think it's not intuitive for users. They may not expect that leaving the field blank will use the default path.

If so, wouldn't it be better to simply add some explanation label next to it rather than making this feature inaccessible?

The feature is still accessible, the user just has to delete the existing pre-filled value before submitting the form.

The feature is still accessible, the user just has to delete the existing pre-filled value before submitting the form.

IMO, this is less intuitive than the opposite action (fill in the field if you want to explicitly set the path).

The feature is still accessible, the user just has to delete the existing pre-filled value before submitting the form.

IMO, this is less intuitive than the opposite action (fill in the field if you want to explicitly set the path).

Both are pretty unintuitive. For now I'll keep the WebUI's behavior matching the GUI and then someone can improve both if they'd like.

I think it's easier to change a part of the path than to write the whole thing. I doubt that people type drastically different save paths often

IMO, in most cases, the default path is sufficient for the user, which has the format <base_path>/<category_name>. However, we provide the option to enable or disable it for specific categories.

I think it's easier to change a part of the path than to write the whole thing. I doubt that people type drastically different save paths often

IMO, in most cases, the default path is sufficient for the user, which has the format <base_path>/<category_name>. However, we provide the option to enable or disable it for specific categories.

I don't understand what you said is related.
Anyway i hadn't thoroughly thought that when the field is filled it means that the user changed the path explicitly.

Rebased onto master now that #22958 is merged. This PR now only contains the changes to the WebUI.

@Piccirello
Thank you!