AutoHotkey Community

Argh, don't be ridiculous. When lack of interest had anything to do with the quolity of the thing? This is great function and you should update it.


I don't see why function can't be equaly powerful.

_________________

Thanks and I know what you mean. Personally, I also prefer having it in a single procedural entity and found it myself easier to follow. Contrary to my expectation, however, looks like many users feel it complicated in that way, so I tended to write in a function form and expose only necessary steps.


I see. I thought you might have a reason about that.

regarding StdoutToVar.ahk:

First, Where does this actually access cmd.exe?

Secondly, would this be adaptable to work with telnet.exe?

I am trying to get a responsive from of telnet (i.e. to login and run certain commands dependant on what information is currently in the telnet window, hidden or not)

I have tried to use this to access telnet but it does not return anything at all.

When it calls CreateProcess(), but without creating the console window, so you may not notice it.


telnet.exe is an interactive app, i.e., needs an interaction with the user, so I don't think this script is usable with it. The same with netsh.exe.

What does sWork do? I see it is empty in both examples. I'm just curious what it does. Thanks for creating such a great script for us other people on the forum.

It'll set the Current/Working directory, which corresponds to AHK's A_WorkingDir.

Thanks

At last I updated StdoutToVar.ahk and StdoutWithCOM.ahk and combined into one.
They aren't tested thoroughly as I uses console apps less and less thanks to AHK, so please post here if find a bug. Thanks.

The script is simplified further. Now, I think/hope it's really easy to use.

Both this and CMDret are great. Hats off to both authors.

As far as the interest issues go, I think that is due to needing more examples of how it works. If you focus just on StdoutToVar.ahk and CMDret , than possibly more novice or casual users may get lost with how you created the script, DllCall talk, etc...

From a user perspective, maybe when people see more of the possibilities and how to use it that it would generate more interest.

I thought there was little to tell more about it, quite self-evident. I may be wrong. Here are a few more examples.

Hi,

is it possible to use this function with tools like telnet? just to get alle the text telnets writing.
A script like this:
- starting telnet
- getting text by your function (how could this work?)
- sending command to telnet
- getting text again

and so on. I hope its no big deal?

There already is the same question a few posts above.

Yes, i already noticed that. But you said its not possible, because its need interaction with the user. But wheres the problem with interaction? I just get a problem getting the telnet text again and again.

In this case you may use it. But, the problem is: how you're gonna terminate the telnet.exe gracefully? There is no way except using AHK's built-in function "Process, Close" or directly TerminateProcess API (which is easier one in this case). They (actually it) are not graceful exit, you may lose data.