AutoHotkey Community

Why don't you just write a function for it.

@Guest:
Alright, I'm going to call you on this one. Are you purposely trying to create a circular argument? This is the Wish List forum - hence the wish & reasons for the wish. Demonstrations of functions have already been provided. Oddly enough, it seems like several users have written functions for this - therefore confirming that it is desirable functionality. However, as you are again trying to point out, it is not required functionality - as there are workarounds. But then again, we are in the Wish List forum ...

Also, note that I have to assume that you're the same guest because you aren't signed in.

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

Not at all. I just suggested a solution for his particular problem. What's wrong with that.

Which means a workaround has been already provided. Then why did he still claim the suggest as if there had not been a solution yet? That appears he is creating a circular argument from my view.

There are more than one guest besides me in this thread. Note that you won't know which one is which in this forum allowing anonymous guests. This is irrelevant to this discussion.

The problem is that most user who desire that simple functionality have to write own function or search the forum for a solution, often writing own function is faster, so we end up with many function doing same simple stuff.

AutoHotkey should be able to do things like this on its own because it is so simple to implement.
Imagine {Tab 3} would not be possible, would you then also suggest to write own function for that to expand {Tab 3} to {Tab}{Tab}{Tab}?

This would be worthless since we could use a function as Guest suggested.

_________________
AHK_H (2alpha) AHF TT _Struct WatchDir Yaml _Input ObjTree RapidHotkey DynaRun

The process of designing syntax in a methodical manner is not simple and way harder than implementing the functionality with a non-organised design.

OK, I got one idea. What about allowing the expression mode and all numerical values in expression are regarded as delay.

It would not be possible to expand it if the functionality of {Key n} did not exist.

Expression mode is already allowed + this will send a number + this is not possible in current ahk design + we would break compatibility
If there was no {Tab 2}, we would write a function that would replace it with {Tab}{Tab}:!:

_________________
AHK_H (2alpha) AHF TT _Struct WatchDir Yaml _Input ObjTree RapidHotkey DynaRun

I will try a different tack: will someone list a sample of threads creating, or asking for, these functions? Seeing their prevalence might help to demonstrate the need for this feature.

I have over 30 small functions adding tiny functionality that I've never posted because they are too small...

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

PowerPro has had this feature for ages without any problems. It uses this syntax:



Notice that there is no space following the 'w'. People use it all the time - just search the forum for {w1}, {w2} etc., you'll find hundreds of posts: http://tech.groups.yahoo.com/group/power-pro/messages/

I'm sure something similar could be implemented in AHK without breaking old scripts. Maybe use {sXXX} so that waits 501 ms between sending 'Alpha' and 'Omega'.

Please, please, please implement this feature!

Thanks.

That might actually work, it won't break backwards compatibility as in my little test just now {s501} is simply ignored e.g. nothing is sent. Not saying it should be implemented, but if it is this would be the way to do it I think.

seems fair enough to me, doesnt break and for the reader distinguishable that its not like send {s 501} times, if the developers could be convinced of its
use then this seems like a rather fail safe way to implement

We should probably collect suggestions and do a poll to find out what majority of users thinks.

My vote goes definitely to number in {} brackets (that is what I have implemented in AHK_H).
{0} to {9} = send the digits as usual
{any digit higher 9} = sleep

It is very logical in my view and also does not break any scripts.
Also a sleep less than 16ms is not possible anyway.

_________________
AHK_H (2alpha) AHF TT _Struct WatchDir Yaml _Input ObjTree RapidHotkey DynaRun

Hotkeyit, i like that you are willing to expand the send, command, the convenience/cornerstone of AHK revolves imo about Hotkeys
so, while you are it, sometimes it bothers me that the send command triggers other hotkeys ie:

Typing in ty creates a rather nasty loop

So normally we would specifically have to turn off the looping key in advance:

and turn them back on/off (tedious) one at the time, it would be nice if instead you have a overruling option between brackets to say that the following text must be send literal as is (notifies ahk to temporarily deactivate the correspondinng hotkeys found in the send string and reactivate the hotkeys after the literal text is send.

For example using quotes


or if a variable is used and we dont know in advance if the variable may contain keycombo to trigger other hotkeys
for example if supplied by user:

or


thoughts?

Just use the standard available options

Guest is correct here. Some users may want the triggering of other keys. This is by design. The $ modifier tells the hotkey to (among other things) ignore simulated input.

</hijack>

_________________

(Common Answers) - New Tutorials Forum - Humongous FAQ