AmiMSN beta with file transfer

[MickJT]

I'll come on overmind, and grab the .log off you.

[CaptainHIT]

Good idea! ;-)

[Gav]

Where do you get the following files from as ive looked on aminet.

rexxdosupport.lib
rexxreqtools.library

Thanks

[cgutjahr]

MickJT wrote:
I started AmiMSN thinking I could do it with AWNPipe, but then found out that it's not asynchronous

I'm not sure what you mean by "asynchronous", but it's perfectly possible to create a GUI with AWNPipe, continue with some other things and come back and process the input events   that the GUI collected in the meantime.

It seems the RXDraughts GUI I sent to you was somewhat useful to you, just tell me if you need some more example code ;-)

[CaptainHIT]

@ Gav:

Here!

http://wuarchive.wustl.edu/aminet/util/rexx/rexxdossup_upd.lha
http://wuarchive.wustl.edu/aminet/util/libs/ReqToolsUsr.lha

[CaptainHIT]

@ Gav:

Err, sorry...

http://wuarchive.wustl.edu/aminet/util/rexx/rexxdossupport.lha

Fixed! ;-)

[Gav]

Well thats weird because reqtools.lib is in my libs folder but it still cant find it??

[MickJT]

@Gav

You need rexxreqtools.library not just reqtools.library

@cgutjahr

AWNPIPE isn't asynchronous, which means that you send "con" (as in continue), and then you are forced to WAIT to see if a button has been clicked on. I don't want to wait, I want a command that tells me what buttons have been clicked on and not processed yet.

rxsocket.library allows me to see if there is any data to get,  and then get it...

What I want in AWNPIPE is to first see if a button has been clicked on, and if not, then see if if i've typed anything, and if not, then loop..

AWNPIPE is like ReadLn(), you so ReadLn(File) and it just hangs until it reads a line.. there's no CheckToSeeIfThereIsALineToReadFirst()

hehe..

Check the .rexx, and look at the usage of Lines(), I check to see if anything has been typed in the shell window and then if not, check to see if there is any data from the msn server to be read, and if not, then checks to see any commands u sent in the ircd, and if not, then loop..

If it still doesn't make sense, picture this:

You have a conversation window open, and it can't process what you are typing and can't process the messages being sent to you, because it's forever waiting for you to click on the close gadget to shut the window.. No command to simply see if you've clicked on the close gadget

Look at the .readme for CTGUI on aminet..

[MickJT]

Thought to myself: On second thought maybe AWNPIPE's output can be sent to PIPE:.. That'd fix everything.

Oh no wait, I remember already trying that.. In arexx, after you send a line to PIPE:, you're forced to use Close() before the line is written.. You can see how insanely stupid the PIPE: code in AmiMSN.rexx is, but it's the only way i've been able to do it, Open(), WriteLn() and Close() for each line sent.. It's only this way in arexx, and has got me stumped..