WLX - Fontview_qt - Possible updates

[advice2020]

I had a couple of ideas for the fontview_qt WLX plugin.
First off, I mentioned this in the past but thank you for making this plugin, I really like this one.
Great that user can type in their own text, rather than being forced to use text about quick brown foxes :)

Was not sure if I should combine them all in one post, if needed I can separate this out into separated posts.
I also decided to put this in the "Issues" section because then could be closed if ideas were not desired to be added.
Hope all of this is okay.

SUGGESTIONS
1.) Maybe could make it so that when user clicks inside the text field, that the current text in the field automatically gets highlighted, so user can quickly type in new text, replacing the old text in the field completely.

2.) Might be due to limitation of font sizes of fonts that I used to test this plugin, but might be nice to offer even larger font sizes for maximum font size. This way if type in shorter words can really increase the size.

3A.) I noticed that there is a drop down in the left side of the plugins toolbar with the current fonts name.
Any font I have tested, the drop down arrow does not appear to do anything, there is always only one item in the list (current font name).
I had thought it might be a list of all the fonts in the current folder being viewed in DC file pane.
Unless (not sure if this exists) maybe there are fonts that contain multiple versions inside one font file, and maybe this drop down would show them if it did?
Or maybe this was just used coding wise on purpose to just supposed to show one item at a time.

3B.) I could not verify the following because as mentioned above only one item per drop down, but I originally tried scrolling mouse on top of the drop down to see if I can change fonts up/down. If this drop down is meant for a list of items, and it does not include mouse scrolling on top of it to cycle through the fonts, could it be considered to add this.

If these updates are not desired, can just close.
Thank you for reading this.

[advice2020]

If they are not desired to be added to the official plugin itself, if anyone knows of any modifications I can make to the cpp code file itself to add these to my own compile, please let me know.
For example, have not tried yet, but I saw that the 2.) item I mentioned could probably be changed by modifying the following in the cpp code.

fontsize->setMinimum(6);
fontsize->setMaximum(72);
fontsize->setValue(gSize);

72 is a large font size so it must have just been the fonts I was using to test, that were smaller.

[j2969719]

1. QLineEdit does not have clicked signal, which means it will require creating a new subclass and reimplementing mouse events, which means it will require rewriting the plugin in OOP, which in turn will make this wierd half-joke of writing plugins in cpp/qt via lambda functions even less funny

2. although it is technically possible cant remember many apps that allow to set size value above 72, but yep you can achieve this by modifying the line with setMaximum

3. these wlx plugins always work with the selected file and do not load other files from the current folder for viewing bypassing doublecmd. the dropdown list is added in case QFontDatabase returns more than one font families

[advice2020]

Thank you for your response
1.) Usually more of an action for a hotkey that applies focus to a field, for example Ctrl+F to find in most applications.
Not that important, was trying to think of some way of replicating with a mouse based action because keyboard shortcut would not make sense either.

2.) Yeah 72 is often the max, some applications I have seen go higher such as LibreOffice applications.

3.) Ahh that is similar to what I mentioned, where some files maybe include multiple versions in one file, none of the fonts I tested contained this so did not have any way to test, just wanted to be sure.

Okay, well nothing really left to discuss :)