Re: [Audacity-devel] Extended import filtering
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2010-04-11 12:20:10
|
| From LRN <lr...@gm...> | Sat, 10 Apr 2010 20:48:29 +0400 | Subject: [Audacity-devel] Extended import filtering > On 10.04.2010 19:50, Gale Andrews wrote: > > | From LRN <lr...@gm...> > > | Sat, 10 Apr 2010 10:32:28 +0400 > > | Subject: [Audacity-devel] Extended import filtering > > > >> On 08.04.2010 8:28, Gale Andrews wrote: > > ... However I am afraid in either Unicode Release or ANSI Release on > > Windows, I still can't get the basic functionality to work. The ANSI > > is unmodified SVN. > > > > I have a "*.wav" rule with "FFmpeg-compatible files" as the first item. > > Cfg has: > > > > Item0=*.wav\\*|libav:libsndfile:liboggvorbis:libflac:libmad:lof > > > > which seems correct. The File Open/Import filter is set to the default > > "All files". (I think it should default to "All supported files", but still). > > WAVs dragged in with Explorer still open with libsndfile (either > > alisased or not, according to the Preferences). > > > > If I drag in MP3s that open fine in 1.3.12 Unicode Release, I get > > "error importing... - if it is uncompressed, try Import Raw". > > > > Adding the rule appears to be irrelevant to this problem. I cannot > > drag MP3s in even on an initialised .cfg, unless I set the Open/Import > > filter to "All supported files", "MP3 files" or "FFmpeg-compatible files". > > If I do that, the MP3 comes in via FFmpeg (either imported via the > > dialogue or dragged), even if "All supported files" or "MP3 files" is > > selected. So if FFmpeg is unavailable, MP3s cannot now be imported. > > > > Maybe build Release and take a look? > > > Works for me. With exactly this filter line. In Unicode Release. > What's your wxWidgets version? The recommended 2.8.10 of course. Two other users of the Windows "Nightlies" confirm the same behaviour. I can try a Win debug build to compare, but the behaviour is identical on SVN Unicode Release in Ubuntu 9.10 (absolutely stock SVN, wx 2.8.10, configure and make, no compile time options). Have you tried downloading your Unicode build on to a non-developer machine? > >>> ... and David wrote: > >>> > >>> > >>>> With respect to the ctrl+up and ctrl+down shortcuts for moving items > >>>> up and down. I think it could be argued that alt+up and alt+down might > >>>> be a better choice. In lists, ctrl+up/down is normally used for > >>>> changing the focus without changing the selection, and in tables > >>>> ctrl+up/down are normally used to move to the top and bottoms of > >>>> columns. Internet Explorer uses alt+up/down for moving favorites up > >>>> and down the list in the favorites center. > >>>> > >>>> > >>> FWIW, xplorer2 (Explorer replacement) does use CTRL + up/down to > >>> move list items. But I don't think either CTRL or ALT are all that > >>> discoverable to sighted users. Does Widgets support up button and > >>> down button to move a selected list item? That seems quite a common > >>> solution. > >>> > >>> > >> Fixed. Now there are 4 additional buttons for moving things up and down. > >> All with hotkeys (Alt+<char>). Ctrl+Up/Down are still supported, and > >> drag'n'drop reordering is available for rule table. > >> > > Drag n' drop does not work for me, either with a cheap ball mouse on > > Linux or with my mouse emulator on Windows (yes, both real and > > emulated mouse can drag and drop properly) :=). > > > That's weird. But then, i've developed that on Windows. Drag'n'drop > seems to be very platform-dependent, maybe i've missed something. Another user has confirmed drag n drop does not work in my "Nightly" (in Vista, Logitech optical mouse). > > I think the four buttons make Prefs. way too wide. On Ubuntu 9.10 at > > 800 x 600, the last button for moving the selected filter down says > > "Move selected". Could we just have buttons that say "Move Up" and > > "Move Down" and they work on the selected rule or filter? You cannot > > select a rule and a filter at the same time, so that should not be a > > problem. Or "Selected Rule/Filter up" and "Selected Rule/Filter down"? > > > > > You can select a rule and a filter at the same time. At least on Windows > you can. Currently selected row defines the contents of the list and > stays selected. I can see the rule remains highlighted (in grey) when you tab or click into one of the importer fields (which then takes over the OS "selected" colour from the rule). However the rule doesn't appear to be active, because up/down keys only affect the importers. > > Or, if we need four buttons, drop the "selected" word. > Sounds sensible. Can we do that then please, if we need the four buttons? > >>> Is there any flexibility to extend the tree a bit farther down below the > >>> bottom of the panel to the right? As it is now, there "looks" adequate > >>> space to accommodate a taller tree without need of a scrollbar. > >>> > >>> > >> No. Dialog template means that "OK" and "Cancel" buttons get the whole > >> line for themselves. > >> > > There is a scrollbar on Linux, so why not on Windows? > Ask wxWidgets developers. By the way, there IS a scrollbar on Windows, > i've seen it. It just disappears... > > > A truncated > > "Mouse" item does not look very good. Also each time I launch Prefs. > > on Windows, the tree panel now bleeds into the boundaries between > > the static boxes. For example this on Win XP: > > http://www.gaclrecords.org.uk/launch_prefs.png > > > > When you select another node in the tree, the problem corrects itself. > > > > This is caused by the scrollbar being shown and hidden again. It must appear subliminally then because I can't see it. Have you reported this to Widgets? It seems a serious restriction - apart from the current cosmetic problems, it would mean we can never add another preferences page on Windows without increasing the default window height. Thanks Gale |