Difference between revisions of "Bug:294"

From Audacity Wiki
Jump to: navigation, search
(dialogue=>dialog)
m (Text replace - "http://bugzilla.audacityteam.org" to "https://bugzilla.audacityteam.org")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{P5|Extra={{Linux}} {{OSX}}|Description=Bug 294: [http://bugzilla.audacityteam.org/show_bug.cgi?id=294 Keyboard focus not restored to its previous place after opening a dialog]{{BugLink|294}}}}
+
{{P5|Extra={{Linux}} {{OSX}}|Description=Bug 294: [https://bugzilla.audacityteam.org/show_bug.cgi?id=294 Keyboard focus not restored to its previous place after opening a dialog]{{BugLink|294}}}}
 
{{BugSummary|1=
 
{{BugSummary|1=
 
81 Comments.
 
81 Comments.
Line 5: Line 5:
 
* It was also noted in the bug comments that on Mac and Linux, focus did not always return where it was after opening a dialog, but did on Windows.  
 
* It was also noted in the bug comments that on Mac and Linux, focus did not always return where it was after opening a dialog, but did on Windows.  
 
* This bug was fixed for a while, except for the Mac/Linux focus issue as above.
 
* This bug was fixed for a while, except for the Mac/Linux focus issue as above.
* Then it was discovered on Linux that if the new "Importing Uncompressed Audio Files" dialog appeared, the imported WAV/AIFF could not be played using Space. This problem is (mostly) repeatable and is now at [http://bugzilla.audacityteam.org/show_bug.cgi?id=370 bug 370] (Linux-only P3).  
+
* Then it was discovered on Linux that if the new "Importing Uncompressed Audio Files" dialog appeared, the imported WAV/AIFF could not be played using Space. This problem is (mostly) repeatable and is now at [https://bugzilla.audacityteam.org/show_bug.cgi?id=370 bug 370] (Linux-only P3).  
 
* This bug (294) is now demoted to P5 for the Mac/Linux issues where focus does not return to the original place after opening a dialog. We want this to happen for platform consistency.  
 
* This bug (294) is now demoted to P5 for the Mac/Linux issues where focus does not return to the original place after opening a dialog. We want this to happen for platform consistency.  
 
* We know which Mac dialogs result in focus not returning where it was. We may need discussion about Linux although it is believed most dialogs cause focus to move back to TrackPanel.  
 
* We know which Mac dialogs result in focus not returning where it was. We may need discussion about Linux although it is believed most dialogs cause focus to move back to TrackPanel.  
Line 12: Line 12:
  
 
== Other Links==
 
== Other Links==
* [http://forum.audacityteam.org/viewtopic.php?f=18&t=49694 Forum Link]
+
* [https://forum.audacityteam.org/viewtopic.php?f=18&t=49694 Forum Link]
  
  
Line 19: Line 19:
  
 
== Mac behaviour ==
 
== Mac behaviour ==
See http://bugzilla.audacityteam.org/show_bug.cgi?id=294#c41
+
See https://bugzilla.audacityteam.org/show_bug.cgi?id=294#c41
  
  
 
== Linux behaviour ==
 
== Linux behaviour ==

Latest revision as of 13:30, 21 August 2017

Summary Points


81 Comments.

  • This was originally a P3 Linux issue that after importing using (SHIFT+CTRL+I), Space did not play the imported track.
  • It was also noted in the bug comments that on Mac and Linux, focus did not always return where it was after opening a dialog, but did on Windows.
  • This bug was fixed for a while, except for the Mac/Linux focus issue as above.
  • Then it was discovered on Linux that if the new "Importing Uncompressed Audio Files" dialog appeared, the imported WAV/AIFF could not be played using Space. This problem is (mostly) repeatable and is now at bug 370 (Linux-only P3).
  • This bug (294) is now demoted to P5 for the Mac/Linux issues where focus does not return to the original place after opening a dialog. We want this to happen for platform consistency.
  • We know which Mac dialogs result in focus not returning where it was. We may need discussion about Linux although it is believed most dialogs cause focus to move back to TrackPanel.


Other Links


Q&A

Mac behaviour

See https://bugzilla.audacityteam.org/show_bug.cgi?id=294#c41


Linux behaviour