ID:270993
Dec 3 2006, 9:41 am
|
|
Is there any way to check an output passed to a datum?
|
In response to Mechanios
|
|
That would output [] to the world, yes, but I want know what output was received.
e.g. world/RecieveOutput(message as text) |
In response to DivineO'peanut
|
|
You're not making sense. the only way to see what output was recieved is to output it.
|
In response to Mechanios
|
|
Are you basically saying that when you send a message example you want to see what was outputted to that person or whatever your outputting and see if it sent and the details etc??
|
In response to Nexus6669
|
|
I don't think there's a way to check recived output, or store it. Rather, implement your code example in a different way. Whenever you want to do "world << xyz", do CustomOutput(xyz)
proc/CustomOutput(msg) I'm not sure, but this may also work: /*random code: |
In response to Kaioken
|
|
I've thought of that solution, but it isn't as convenient as receiving the output directly.
|
In response to DivineO'peanut
|
|
I've thought of that solution, but it isn't as convenient as receiving the output directly.It's really pretty much the same if this is the kind of thing you wanna do. |
In response to Kaioken
|
|
You don't understand. While this solution does produce the wanted results, I want to use the '<<' operator and create a procedure that receives the output '<<' produced. It is somewhat more convenient to work with then this.
edit: After messing around with defines and the such, I produced the wanted results. Solved! =P |
In response to DivineO'peanut
|
|
DivineO'peanut wrote:
You don't understand. While this solution does produce the wanted results, I want to use the '<<' operator and create a procedure that receives the output '<<' produced. It is somewhat more convenient to work with then this. Of course I understand. Anyway, the proc receives the output '<<' is ABOUT to produce. :P edit: After messing around with defines and the such, I produced the wanted results. Solved! =P So, defined "<<" to replace to call a proc or so? :P |
In response to Kaioken
|
|
Kaioken wrote:
DivineO'peanut wrote: No, you still don't understand. :| It's more convenient to use '<<' instead of a procedure. edit: After messing around with defines and the such, I produced the wanted results. Solved! =P I made it so
reference << "Hello"
is the same as
SendInput(src,reference,"Hello")
which is hard, as I needed to workaround spaces and the such. =/ |
Wouldn't that work?