starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Option to select font size #10687

New issue

Open

opened 2026-02-21 20:54:37 -05:00 by deekerman · 9 comments

deekerman commented

2026-02-21 20:54:37 -05:00

Owner

Originally created by @kramola-RU on GitHub (Jul 8, 2020).

The font is not comfortable (too small) in the "Renaming" window.
Could you add an option to selecting the font size in this window?
If the option cannot be added, could you just increase the font size two times?

Originally created by @kramola-RU on GitHub (Jul 8, 2020). The font is not comfortable (too small) in the "Renaming" window. Could you add an option to selecting the font size in this window? If the option cannot be added, could you just increase the font size two times? ![123](https://user-images.githubusercontent.com/51376332/86973498-55a26400-c17d-11ea-9410-4500e50c55bd.jpg)

deekerman added the

Feature request

GUI

Accessibility

labels

2026-02-21 20:54:37 -05:00

deekerman commented

2026-02-21 20:54:40 -05:00

Author

Owner

@jagannatharjun commented on GitHub (Feb 13, 2021):

@glassez @Chocobo1 why we don't support inline renaming of file. similar to changing priority, rather than opening a new dialog use QItemDelegate::createEditors to show a line edit into the column itself.

@jagannatharjun commented on GitHub (Feb 13, 2021): @glassez @Chocobo1 why we don't support inline renaming of file. similar to changing priority, rather than opening a new dialog use QItemDelegate::createEditors to show a line edit into the column itself.

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@glassez commented on GitHub (Feb 13, 2021):

@glassez @Chocobo1 why we don't support inline renaming of file. similar to changing priority, rather than opening a new dialog use QItemDelegate::createEditors to show a line edit into the column itself.

Maybe because it allows you to do additional validation of the entered data?

@glassez commented on GitHub (Feb 13, 2021): > @glassez @Chocobo1 why we don't support inline renaming of file. similar to changing priority, rather than opening a new dialog use QItemDelegate::createEditors to show a line edit into the column itself. Maybe because it allows you to do additional validation of the entered data?

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@jagannatharjun commented on GitHub (Feb 13, 2021):

Maybe because it allows you to do additional validation of the entered data?

it seems it is because the model doesn't handle the actual renaming of the file which is absurd.

@jagannatharjun commented on GitHub (Feb 13, 2021): > Maybe because it allows you to do additional validation of the entered data? it seems it is because the model doesn't handle the actual renaming of the file which is absurd.

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@glassez commented on GitHub (Feb 13, 2021):

it seems it is because the model doesn't handle the actual renaming of the file which is absurd.

TorrentContentModel is incorrectly/inconsistently designed. I recently started working on redesigning it, but it's still unfinished (I'm doing it at the same time as another thing). Maybe I'll post a draft PR later to hear more ideas for improving it.

@glassez commented on GitHub (Feb 13, 2021): > it seems it is because the model doesn't handle the actual renaming of the file which is absurd. TorrentContentModel is incorrectly/inconsistently designed. I recently started working on redesigning it, but it's still unfinished (I'm doing it at the same time as another thing). Maybe I'll post a draft PR later to hear more ideas for improving it.

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@jagannatharjun commented on GitHub (Feb 13, 2021):

TorrentContentModel is incorrectly/inconsistently designed. I recently started working on redesigning it, but it's still unfinished

I just started working on it :P

@jagannatharjun commented on GitHub (Feb 13, 2021): > TorrentContentModel is incorrectly/inconsistently designed. I recently started working on redesigning it, but it's still unfinished I just started working on it :P

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@v-kamskyi commented on GitHub (Jan 11, 2025):

I hadn't read this request before publishing a similar one - about the possibility of increasing the font. Am I right in understanding that the option has not been implemented and is not planned?

@v-kamskyi commented on GitHub (Jan 11, 2025): I hadn't read this request before publishing a similar one - about the possibility of increasing the font. Am I right in understanding that the option has not been implemented and is not planned?

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Jan 11, 2025):

Am I right in understanding that the option has not been implemented

Correct.

and is not planned?

Not currently, I'd like to have this option along with having a bold text option in transfer list.

It may happen in a future version though....

@xavier2k6 commented on GitHub (Jan 11, 2025): >Am I right in understanding that the option has not been implemented Correct. >and is not planned? Not currently, I'd like to have this option along with having a `bold` text option in transfer list. It may happen in a future version though....

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@Milor123 commented on GitHub (May 22, 2025):

it's really frustrating that in the middle of 2025 this application has nothing to help me read better, I just can't see and I'm on a 24 inch monitor.

I'm looking for threads here on github and none of them give a useful solution, DPI scaling is not a viable solution, and the windows system DPI override doesn't solve anything.

What should I do with desktop version?

@Milor123 commented on GitHub (May 22, 2025): it's really frustrating that in the middle of 2025 this application has nothing to help me read better, I just can't see and I'm on a 24 inch monitor. I'm looking for threads here on github and none of them give a useful solution, DPI scaling is not a viable solution, and the windows system DPI override doesn't solve anything. What should I do with desktop version?

deekerman commented

2026-02-21 20:54:44 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**