<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/osw/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/osw/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/osw/feature-requests/</id><updated>2003-08-13T10:35:03Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>VST plugins</title><link href="https://sourceforge.net/p/osw/feature-requests/4/" rel="alternate"/><published>2003-08-13T10:35:03Z</published><updated>2003-08-13T10:35:03Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net929a8aea9c69d353487e58a75264a33d106fb17b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Support for VST plugins and/or OSW as VST instrument.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Breakpoint editor transform</title><link href="https://sourceforge.net/p/osw/feature-requests/3/" rel="alternate"/><published>2003-03-09T05:14:29Z</published><updated>2003-03-09T05:14:29Z</updated><author><name>William Sinclair</name><uri>https://sourceforge.net/u/wllm/</uri></author><id>https://sourceforge.netf8c30ffb8d984dd4ecfd95fc1ef5153495f877e8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is a totally necessary feature that requires some&lt;br /&gt;
thought. I would expect minimally these features:&lt;/p&gt;
&lt;p&gt;1) GUI embedded in patch&lt;br /&gt;
2) Easy connection to Line transform&lt;br /&gt;
3) Ability to save breakpoint data. Ideally, both the&lt;br /&gt;
ability to save it within a patch file and also to&lt;br /&gt;
&amp;amp;quot;export&amp;amp;quot; it to a file containing only breakpoint data&lt;br /&gt;
so it can be shared among patches.&lt;/p&gt;
&lt;p&gt;There are several considerations here- should we have a&lt;br /&gt;
general 2d data editor, of which a breakpoint editor is&lt;br /&gt;
only a special case? Should we bother to do this&lt;br /&gt;
gui-intensive transform before our new interface is&lt;br /&gt;
done? What level of user configurability should we&lt;br /&gt;
implement (see Max/MSP env/envi scripts for one example)?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Some way to use tab for transform completions. . .</title><link href="https://sourceforge.net/p/osw/feature-requests/2/" rel="alternate"/><published>2003-03-06T07:51:51Z</published><updated>2003-03-06T07:51:51Z</updated><author><name>William Sinclair</name><uri>https://sourceforge.net/u/wllm/</uri></author><id>https://sourceforge.neta36f376bb294a4f57e5f91182797c9ad657a070e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I think transform completions are very cool, but I just&lt;br /&gt;
can't get used to reaching for the esc key instead of&lt;br /&gt;
the tab key. Maybe the completion key can be user&lt;br /&gt;
assignable? Maybe we could just switch it over to tab,&lt;br /&gt;
since the greater precendent is tab completion?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>At least one level of undo. . .</title><link href="https://sourceforge.net/p/osw/feature-requests/1/" rel="alternate"/><published>2003-03-04T08:26:32Z</published><updated>2003-03-04T08:26:32Z</updated><author><name>William Sinclair</name><uri>https://sourceforge.net/u/wllm/</uri></author><id>https://sourceforge.net385f7cf22e7bddcf728d4659fd4744b29060a120</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be ok to have one level of undo, better would be &lt;br /&gt;
to have unlimited undoes, best would be to have &lt;br /&gt;
a &amp;amp;quot;history&amp;amp;quot; a la Photoshop.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>