search for: argument2

...e should describe each element of the argument list (which is afcourse OK) in a form: \item{arg_i}{Description of arg_i.} When I started with R it really helped me that some "man pages" used \item{arg_i}{Mode. Description of arg_i.} e.g. \item{argument1}{Logical. Bla bla bla.} \item{argument2}{Integer. Bla bla bla.} \item{argument2}{Character. Bla bla bla.} Although one can most of the time deduce from the man page what mode should each argument be, I belive that it would enhance redeability if mode specification would be mandatory. I would also like to see that there is some sort o...

.... It makes it possible to send the success and failure functions information about the browser state when the call was made. Yahoo! UI user code looks like var callback = { success: function(o) {/*success handler code*/}, failure: function(o) {/*failure handler code*/}, argument: [argument1, argument2, argument3] } The example comes from http://developer.yahoo.com/yui/connection/#async Can this be done with Rails link_to_remote()? If not is there a workaround? Thanks, Peter

Hi, I noticed that when dial terminates it does not return to the dialplan, and therefore can not execute any entry after Dial(). Is there any trick to overcome this limitation ? How I am supposed to handle the returned vales DIALEDTIME, ANSWEREDTIME if I can not execute anything after Dial()? I made a workaround with DeadAGI (below) but it is unreliable: if 2 calls end

The changes to vorbisfile that I suggested earlier have now been committed - this is mostly a merge of my code with a similar patch from Martin Vogt (thanks Martin). The old ov_open() interface remains untouched - and for many people, this is all you'll need to use, ever. It now calls the new interface with appropriate arguments. The new ov_open_callbacks() function adds an extra argument to