AutoHotkey Community

Allow a specified control to have a set font size.
Rather than setting the font size for the entire interface.

Do you mean like this?
:roll:

That looks pretty good.
Lol damn, you got me.
Maybe I should stay in ask for help.

Much easier and straighforward would be if we could do this:


If many such isolated font changes have to be done throught the script without possibility to batch them together (different GUI #, different groups/sections), the number of code lines would diminish, as currently we have to add a Gui, Font after each change to restore to default (see below).

Moreover, such syntax would/should allow overriding a whole section of user-defined font settings, only for the current control:

Using tBold seems to conflict with the use of T for tabstops in Edit controls. Another example is W (font weight), which is already used for width. There may be other cases.

Even if there aren't any other cases, another potential drawback would be the reduction of option letters available for future use.

So at this point, I'm not sure it would be worthwhile.

Letter e could be used for Weight (or is that one taken too?) As for t in Edit... can a Tab be present in the options section...?

Nevertheless, looks like this parameter section needs some revamping. Maybe double-character prefix for options would be needed.

Although I can see that inline font settings would be useful, the benefit/cost doesn't seem that attractive. Since there are probably dozens of GUI features that seem like a higher priority (e.g. improved control over radio buttons), it might be a long time before inline fonts are supported.

could you use full words/abbreviations? or would it not be good idea?

_________________
rawr. be very afraid
*poke*
Note: My name is all lowercase for a reason.
"I think Bigfoot is blurry, that's the problem. It's not the photographer's fault, Bigfoot is blurry. So there's a large, out-of-focus monster roaming the countryside."

Bit by bit, these small improvements sum up to ease the life of the scripter. The workflow would be more dynamic if all options and syntax would be as straight and logical as the environment allows.

Personally I confess I must keep the Help file open at all times when working on scripts because there's always a doubt whether "this" should be "this way" or "the other".

Forgive me, this is already getting too general. But it's always good to take a step back and look at the big picture. And yes, I know there are two points of view that are usually opposite - user's and programmer's - and that many times compromise must be accepted. Hopefully it's always for the best.

Anyway, it's good to have open discussion so good ideas can come out and get implemented.