AutoHotkey Community

That is vice. Since it would be even harder to adjust Auto-Syntax-Tidy to it. I'm currently expending it to allow OTB and that is pretty tricky already.

When can new GUI controls be awaited? May I start with Misha's TreeControl dll, or are the AHK commands comming any time soon?

_________________
Ciao
toralf

Wherever you can't use OTB (like parsing loops?) this allows you to use the line taken by the open brace. It's not so bad, I'd do it - I guess I have an ugly coding style

_________________
GitHub • Scripts • IronAHK • Contact by email not private message.

The Tree control and perhaps a few others are expected to be done sometime between v43 and v45. v42 will probably be more enhancements to context-sensitive hotkeys and hotstrings.

As for timing, v42 should be out within a week, and the others usually follow at about 2 or 3 week intervals. But as always, these are rough estimates that depend on how long R&D actually takes, as well as how much time I have.

*Happy*
So if v42 comes within a week,
v43 will be 3 weeks or end of February.
v44 will be 5 weeks
v45 will be 7 weeks or end of March.

So, if everything goes straight we will have something new to play with in March/April :)))

I'll do my best to get you as much time as possible. :)))

_________________
Ciao
toralf

In v1.0.41.02, "GuiControl Move" was changed to eliminate flickering when resizing or moving controls [thanks Serenity]. However, this may cause painting artifacts for some control types under certain circumstances. If so, please update your scripts to use GuiControl MoveDraw instead.

Thanks. By the shift of the commands it will even save me to update my scripts. :))

_________________
Ciao
toralf

Although some flickering occurs, it's definetly a major improvement. Thanks.

_________________
GitHub • Scripts • IronAHK • Contact by email not private message.

Thanks; I'll change it to say "reduce" vs. "eliminate".

Much better! To see the difference within minutes is cool. Despite it hasn't hurt me before. The ListView is stable now, only a very little flicker is in the frame (w2000). Has to test it w/ W98 @ home later today.

Thanx!

_________________
Peter

Wisenheiming for beginners: KaPeGe (German only, sorry)

Thanks for the Window specific hotkeys.

Perhaps next version you can get process specific hotkeys as well.

i.e. #IfProgram Notepad.exe

_________________
//TODO: Create kewl sig...

Although process-specific hotkeys probably won't be added, you could use #IfWin with an ahk_group containing some ahk_pid entries for your processes. Alternatively, ahk_class might be more suitable than a process name in many cases.

If there is demand, a WinTitle of ahk_process could be supported so that you can specify a process name with any windowing command. However, I don't recall this ever being requested, so it seems unlikely many people would use it.

Also, you could overload WinGet...

My suggestion was for ahk_pn, but I did semi-request it...(if you add either, please add ahk_pn as a shortcut to ahk_process...it's short & sweet, like ahk_id & ahk_pid). I'd also like ahk_title, then you could support multiple titles or support a title as not the being 1st param...there may be other uses, supporting a title where it currently ain't supported (I can't think of an example tho).

_________________
AutoHotkey-Hotstring.ahk - Helping the world spell "AutoHotkey" correctly! (btw, it's a lowercase k!)

I've made a note to consider it (assuming process name ever gets added).

It seems overly complicated given rarity of use and that GroupAdd+ahk_group can already do it. But I'd welcome any real-world examples that demonstrate otherwise.