AutoHotkey Community

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

That's good info, thanks. I do plan to support the styles you mentioned. In addition, auto-calculating the control's height would only be done if it wasn't specified, so that should be flexible enough.

Rajat · Joined: 28 Mar 2004 Posts: 1718

when can we have access to first preview of these features Chris?
_________________

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

I'll try to get a test version out in a couple of days. Any testing and feedback you or others have time for might help accelerate the release.

Atomhrt · Joined: 02 Sep 2004 Posts: 128 Location: Sunnyvale

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

It's all just C++ with basic API calls. There's no MFC or other "bloating" things in the code, so I don't expect it to get larger by more than 10K due to the GUI features.

Rajat · Joined: 28 Mar 2004 Posts: 1718

beardboy · Joined: 02 Mar 2004 Posts: 444 Location: SLC, Utah

I'm always availabe for NT, 2000, and XP testing.

thanks,
beardboy

Rajat · Joined: 28 Mar 2004 Posts: 1718

It occurred to me that instead of well defined places for every parameter of GUI controls, it'd be easier and more future-proof to make it like progress cmd's flexible params.

for example instead of a cast in stone cmd like 'URLDownloadToFile, URL, Filename'
it'd be better to have it like this:
GUIcontrol, Button, MyButton, x30 y40 Font-Tahoma Color-003300
(omitted H and W as you'll support automatic formatting based on text)
Font and Color etc. can be ofcourse abbreviated.

Also directly supporting style and exStyle ($WS_EX_APPWINDOW or $WS_EX_ACCEPTFILES etc.) is I think a must, as one of my old au3 scripts heavily relies on these and I know how important they are for a proper interface.

thanx.
_________________

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

Rajat · Joined: 28 Mar 2004 Posts: 1718

just for some clarification, i never used $WS_EX_APPWINDOW or $WS_EX_ACCEPTFILES as they are, because it reqd me to FileInclude a definition file making clear what these are.

I just put the actual codes for these like this:
GUISetControl ( "edit", $TEXT, 3, 5, 284, 160, 0x50200104, 0x00000200)
_________________

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

Good point. I'm going to try to make most frequently used styles into option letters. If I discover there are too many styles and controls to realistically include options for, I'll probably add a method to apply "extra styles" to a window or its controls as they were in your example.

Rajat · Joined: 28 Mar 2004 Posts: 1718

Chris · Site Admin Joined: 02 Mar 2004 Posts: 10467

I know there are a lot of styles, but it was my impression that 80% or more of them either do not apply to a particular control, or are so rarely used that mention of it could be made on a secondary page or omitted entirely. Since I don't know this for sure, anyone with time on their hands is welcome to study the styles and rank them according to expected frequency of use, perhaps proposing option letters for the most popular of them.

Option letters might not be all that easy to remember, but they're definitely easier to remember than style numbers. But as you said, those styles could be #included as pre-defined variables.

Rajat · Joined: 28 Mar 2004 Posts: 1718

Though i don't know quite much about the programming aspect of this but i think au3 just takes the style code and passes it on to windows APIs or whatever, so even if its a style unthought of while programming the feature, one could just get the info about it from MSDN and use it. its quite open-ended this way and suits varied needs. that's what custom interface is all about.
ofcourse u'd know better in this regard.
_________________