Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 31 - Clicking in a file open or save dialogue may cause the files or some folders to disappear from the list
Clicking in a file open or save dialogue may cause the files or some folders ...
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Application Core
1.3.11
PC Windows 7
: P3 MoonPhase
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-01-28 12:06 UTC by James Crook
Modified: 2018-08-20 11:54 UTC (History)
1 user (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Crook 2010-01-28 12:06:17 UTC
*  GA 30Dec09: Only occasionally reported, and exact behaviour seems to vary per machine. Ed has clarified in e-mail that \audacity\lib-src\FileDialog\win\FileDialogPrivate.cpp v 1.18 2009/11/13 05:21:43 llucius is the code in question. Ed believes wxWidgets 2.9 would eliminate the need for Leland's code but wouldn't be a fix in itself. Meantime we have a patch from Ed to turn filtering off on Win7 which works fine for me. Ed has suggested resubmitting the patch against CVS HEAD to be sure.  (EFMv (Ed) 30Dec09 new "ignore" patch submitted) Ed also said a Windows 7-style file dialog would work fine with native filtering on 7, Vista and XP (but not pre-XP). This would mean wrapping every file dialog call in an OS/version test however.  (EFMv 30Dec09 patch demonstrating this submitted)
    * EFMv 30Dec09 I think this should be a P2 unless my "ignore" patch is applied.
          o GA: Maybe, I'm going on number of complaints. Do we know why this occurs so infrequently? I agree it seems better to apply the patch to turn filtering off for Windows 7. We don't want this issue sullying an announcement of support for Win7.
          o EFMv 30Dec09 I think this is a race condition. When I first started investigating this I had a slow dual core CPU; with that CPU, if I single stepped through the code with the debugger, the original code would occasionally work. I am now running a very fast quad core CPU and even with single stepping the problem always presents.
Comment 1 Gale Andrews 2010-02-05 09:46:18 UTC
Fix committed 19Jan10