Post by jeeswg » 21 May 2019, 17:43
- Fair points re. the Range object, I've updated the post to provide an enumerator object version.
- That said, I tested my original function, and it worked great at 1 million keys, and reasonably well up to 10 million keys. I'd be unlikely to use it for over a thousand keys.
- I don't mind what the C++ code what would like for a built-in Range function. However, the specifics of the start/end/step parameters are subtle, and what I wanted to pin down in the post.
- After writing this post, I saw essentially the same idea here:
Adding help function: TokensToScriptObject and two related macros. by HelgeffegleH · Pull Request #110 · Lexikos/AutoHotkey_L · GitHub
https://github.com/Lexikos/AutoHotkey_L/pull/110
- Both you and Helgef have suggested that being able to easily add keys to an AHK basic object, within the C++ code, could be useful, and I agree.
- I wondered if you had any use cases in mind.
- Fair points re. the Range object, I've updated the post to provide an enumerator object version.
- That said, I tested my original function, and it worked great at 1 million keys, and reasonably well up to 10 million keys. I'd be unlikely to use it for over a thousand keys.
- I don't mind what the C++ code what would like for a built-in Range function. However, the specifics of the start/end/step parameters are subtle, and what I wanted to pin down in the post.
- After writing this post, I saw essentially the same idea here:
Adding help function: TokensToScriptObject and two related macros. by HelgeffegleH · Pull Request #110 · Lexikos/AutoHotkey_L · GitHub
[url]https://github.com/Lexikos/AutoHotkey_L/pull/110[/url]
- Both you and Helgef have suggested that being able to easily add keys to an AHK basic object, within the C++ code, could be useful, and I agree.
- I wondered if you had any use cases in mind.