I've been having some difficulties sending commands to an EQ1 session via the "type" command. Lock foreground is checked for EQ1, and in some cases things work fine.
however I have a script like the following:
function main()
{
type "/assist fred\n"
}
which appears to do nothing. The command does not occur, it doesn't show up in the command history (ie the shift-arrow buffer). If I open up the note window with "/note", the text is entered into the note with or without the session having focus. But it doesn't seem to go into the main chat window.
I have even placed the cursor in that window and left the session active without success.
I have tried to relay the type command from another machine, as well as relay a runscript command. Neither assist occurs. I know the script is started since I can add a "messagebox" to the script, and it always appears.
No errors are seen on any of the 4 consoles (two IS consoles, two session consoles). The assist works fine if I type it in from the keyboard.
I searched the forums and didn't see anything similar. Hopefully I missed something simple.
PS: sometimes the assists work if I shorten the strings, such as using "/as" instead of "/assist". Again, the text is entered into the note window just fine in all cases.
Any recommendations?
EQ1 and the type command
Moderators: Lavish Software Team, Moderators
You would really have a much easier time executing commands like that if you load ISXEQ, and use the EQCommand command instead of using the Type command. Type is always going to be less reliable than direct execution of the command (e.g. when another window has focus, like the note window, your Type will go to it instead of where you intended).
That said, I can run some tests and see if Type works for me in EQ1 from a script, but if it does, that's kind of the end of what I can do in this case.
That said, I can run some tests and see if Type works for me in EQ1 from a script, but if it does, that's kind of the end of what I can do in this case.
Thanks for the suggestion. Innerspace has been fine for the most part, and I figured that SOE would more likely be looking for ISXEQ than Innerspace.
Anyhow, (and I hate to ask this), but where do I get ISXEQ? Ismods has a compiled version from 2006, which is incompatible with the current IS. It has source from that era as well.
Macroquest2.com has macroquest in its download section, but no ISXEQ that I could see. The ISXEQ forum on the MQ2 site has an announcement from 2005 for the latest version.
All in all, I'm confused. Anything you could do to set me on the right path would be appreciated.
Regarding the type command: I notice that if I leave off the return at the end of the command, wait a bit and then send the return, things work for me.
type "/assist fred"
wait 5
type "\n"
The problem isn't that the output is going to the wrong spot, but that it acts as if the text is going in faster than EQ wants to accept it.
Another observation: if I leave off the return, the text goes into the command line and stays there. So if we immediately send another copy (ie bind the function to a key and hit it multiple times) the text appends correctly. This occurs when the session does not have focus. Yes, this is what one expects to occur. My point is that adding the return is where things go south on my end. The text with the return is discarded by EQ.
Perhaps that will help figure out what is going on.
Anyhow, (and I hate to ask this), but where do I get ISXEQ? Ismods has a compiled version from 2006, which is incompatible with the current IS. It has source from that era as well.
Macroquest2.com has macroquest in its download section, but no ISXEQ that I could see. The ISXEQ forum on the MQ2 site has an announcement from 2005 for the latest version.
All in all, I'm confused. Anything you could do to set me on the right path would be appreciated.
Regarding the type command: I notice that if I leave off the return at the end of the command, wait a bit and then send the return, things work for me.
type "/assist fred"
wait 5
type "\n"
The problem isn't that the output is going to the wrong spot, but that it acts as if the text is going in faster than EQ wants to accept it.
Another observation: if I leave off the return, the text goes into the command line and stays there. So if we immediately send another copy (ie bind the function to a key and hit it multiple times) the text appends correctly. This occurs when the session does not have focus. Yes, this is what one expects to occur. My point is that adding the return is where things go south on my end. The text with the return is discarded by EQ.
Perhaps that will help figure out what is going on.
I downloaded MQ, and built ISXEQ with VS 2008. No troubles there, although there were no VS2008 libraries supplied. I used the vs90 libraries, and the project linked. However, when I tried to load the extension IS crashed.
I don't keep old compilers around, so I am going to need to do things with Innerspace directly.
I don't keep old compilers around, so I am going to need to do things with Innerspace directly.
Sounds like you have bad pointers or offsets. Is your MQ/ISXEQ build up to date?hendar wrote:I downloaded MQ, and built ISXEQ with VS 2008. No troubles there, although there were no VS2008 libraries supplied. I used the vs90 libraries, and the project linked. However, when I tried to load the extension IS crashed.
I don't keep old compilers around, so I am going to need to do things with Innerspace directly.
-j
Yes there is incompatibility with the libs unfortunately, I need to do a proper lib build for vs2008. In the meantime you can probably get a compiled copy of ISXEQ from the folks in #isxeq on irc.lavishsoft.com.
http://embed.mibbit.com/?server=irc.lav ... l=%23isxeq
I will check on the return thing. It should work fine doing
If not, then there's a problem with the emulation queue. I should be able to do testing on this today.
http://embed.mibbit.com/?server=irc.lav ... l=%23isxeq
I will check on the return thing. It should work fine doing
Code: Select all
type "/assist whatever"
press enter