Hi, 2010/1/6 n3ph <[email protected]>: > I expected to find something like queue or request.. have i left some > hidden triggers???
The commands <id>.push, <id>.queue are registered by queue operators request.queue() and request.equeue(). If you don't have any such operator in your script it's normal that you don't see them. One reason for this is that you could have several queues, and each one gets a different push command. Also, pushing in a queue doesn't describe all what's going on afterwards: should the request be played immediately, should it have a special transition or jingle, etc. But don't get scared, adding a basic queue is very simple: change your main source with fallback([request.queue(id="foo"),main_source]) and you get a queue that overrides the main schedule (in a track sensitive way). You still have the commands alive, metadata, trace and resolving for inspecting existing requests, independently of which source created them. Note that those commands are now prefixed by "request." with the SVN version. Have fun, -- David ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
