AutoHotkey Community

Hello, I have been stumped trying to get this working at all. Can you figure this out? Please generate a simple GUI, that when pumped with specs like:

INPUT_W_START=300
INPUT_H_START=350

INPUT_W_END=425
INPUT_H_END=496

Will enable enlargement and shrinkage of the GUI (please note: proportionally), but will not let it grow or shrink past the START & END points specified. This logic assumes the dimensions inputed are congruent/proportional to each other (which #'s those are proportional) Can someone or anyone make this one work? Thank you very much if you can.

Am I correct that you want to keep a fixed aspect ratio scaling of the window within a min/max boundery?

IMHO anyway this would require interception of WinAPI internal WM_SIZE message and subclassing of the GUI window, there should be some examples in other languages for sure

Cool, yes Bobo, this is correct!

Can anyone perform this stunt?

Maybe you were referring to a non-ahk GUI ?

Ah, very excellent, but this only addresses 1 of the factors. The GUI does indeed stay put within the MIN and MAX... however, the ultimate goal is to see if anyone can make it do that + keep the proportions aligned, so, I.E., if the box WIDTH only was stretched, the height would magically follow in sync-step See what I mean?

I think you can do it, just google for some examples in VB or C

See what I mean?

Related:

[Retired] LimitGUISize v1.0 posted by jballi

It must be too hard for AHK? What are these examples in foreign languages? I can't see why nobody can do this.... it is just a fixed element right?

I have given you a starting point - so, why do not you put some efforts and see how hard it is .. and maybe you can post your non-working code .. so others can continue from there.

be the first to implement this in AHK

No, just not interesting enough. Hook/OnMessage on WM_WINDOWPOSCHANGING.

The rigorous way may be using WM_NCCALCSIZE, but it can be a lot more tedious.

There doesn't seem to be much info. out there on those commands. I am fairly new at Win API accessing... but those appear like a solution. So what is going on with those commands -- are we hooking into a general GUI, and forcing it to calculate to a proportional resize? Sorry if I seem confused, trying to get some learning experience here and make this work.