I'd rather not have .aif as part of the name of audioclips once they are in a stack. Is there a way to change the names of audioclips wihtout touching the source files? thanks sqb
------------------------- Stephen Barncard San Francisco http://barncard.com _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution From [email protected] Thu Apr 23 19:21:55 2009 Return-path: <[email protected]> Envelope-to: [email protected] Delivery-date: Thu, 23 Apr 2009 19:21:55 -0700 Received: from exprod5mx199.postini.com ([64.18.0.45] helo=psmtp.com) by mail-archive.com with smtp (Exim 4.67) (envelope-from <[email protected]>) id 1LxB35-0006q0-CM for [email protected]; Thu, 23 Apr 2009 19:21:55 -0700 Received: from source ([140.211.11.3]) by exprod5mx199.postini.com ([64.18.4.10]) with SMTP; Thu, 23 Apr 2009 18:21:54 PST Received: (qmail 95993 invoked by uid 500); 24 Apr 2009 02:21:53 -0000 Mailing-List: contact [email protected]; run by ezmlm Precedence: bulk List-Help: <mailto:[email protected]> List-Unsubscribe: <mailto:[email protected]> List-Post: <mailto:[email protected]> List-Id: <dev.ode.apache.org> Reply-To: [email protected] Delivered-To: mailing list [email protected] Received: (qmail 95981 invoked by uid 99); 24 Apr 2009 02:21:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 02:21:53 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2009 02:21:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 529D1234C003 for <[email protected]>; Thu, 23 Apr 2009 19:21:30 -0700 (PDT) Message-ID: <1018308788.1240539690316.javamail.j...@brutus> Date: Thu, 23 Apr 2009 19:21:30 -0700 (PDT) From: "Alexis Midon (JIRA)" <[email protected]> To: [email protected] Subject: [jira] Created: (ODE-595) SimpleScheduler#stop does not cancel jobs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org X-pstn-neptune: 0/0/0.00/0 X-pstn-levels: (S:99.90000/99.90000 CV: 7.6261 FC:95.5390 LC:93.6803 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s CV gt3 gt2 gt1 r p m c X-pstn-addresses: from <[email protected]> [294/10] SimpleScheduler#stop does not cancel jobs ----------------------------------------- Key: ODE-595 URL: https://issues.apache.org/jira/browse/ODE-595 Project: ODE Issue Type: Bug Components: BPEL Runtime Affects Versions: 1.3.2 Reporter: Alexis Midon Assignee: Alexis Midon Fix For: 1.3.3 The current implementation of org.apache.ode.scheduler.simple.SimpleScheduler#stop does not try to interrupt the jobs that are actively executed nor to cancel jobs already in queue waiting to be executed. This is contradictory with the goal of the stop method. The stop method must do its best effort to interrupt any on going executions and cancel jobs in queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
