Quantcast

Finding recent Q2A activity WAS Re: Bug 815 Transcription Toolbar and Transport Toolbar play buttons

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Finding recent Q2A activity WAS Re: Bug 815 Transcription Toolbar and Transport Toolbar play buttons

Gale
Administrator
There is IMO a serious problem with following Q2A.

I would have expected the question on top would have been the
one that had the most recent activity. I'd have expected that
links to questions which had been updated since my last visit
would be displayed as unvisited, and those questions that had
not changed would be visited links. See Nabble as an example.

Or see how phpBB forum software does it - topics with unread
posts are red.

Can this be fixed, or is there a trick I do not know? If not, I don't
have time to wade each question every day to see the latest
changes (if any). And so I really don't want to add more questions
to Q2A.



Gale



On 14 April 2017 at 11:05, James Crook <[hidden email]> wrote:

> I suggest a question on hub to tease out the 'correct' design.
>
> On 4/14/2017 3:10 AM, Gale Andrews wrote:
>> Steve wrote in:
>> http://bugzilla.audacityteam.org/show_bug.cgi?id=815#c15
>>
>>     "It seems to me that the "play at speed" button is behaving like a
>>      "momentary action switch", in that it is issuing a command to start
>>       an action each time it is pressed. (Momentary action switches are
>>       like doorbell switches - they return to the "Up" position after being
>>       pressed).
>>
>>       The "Play" button also appears to be behaving correctly as it
>>       designed to indicate (by the down position) that Audacity is in
>>       "play mode"."
>>
>>
>> So Steve disagrees with Peter and Paul, I think. And meantime this bug
>> is going round in circles, and I don't think there is enough consensus
>> to either close or promote the issue..
>>
>> I think standard Play button has got to be down when playing at speed,
>> if we want the feature that clicking that button restarts at standard
>> speed at the editing cursor.
>>
>> By the same argument Transcription Toolbar does not indicate by
>> depressing its Play button that you can click that button to restart
>> play
>> at speed at the cursor. That seems wrong too, but the visual impact
>> of having both Play-at-Speed Play button and standard Play button
>> depressed simultaneously was thought confusing too confusing.
>>
>> My issue with the current situation is that you can't tell which type of
>> playback is in force. This will matter when we finally fix Play-at-Speed
>> to change the speed on the fly and it will matter if we play only the
>> spectral selection. I think the key to this is therefore letting the current
>> behaviour stand but indicating somehow which type of playback is in
>> force. The main Play button already sacrifices indicating that clicking
>> it starts single play by showing a Loop symbol when there is looped
>> standard or looped play-at-speed playback. Likewise for Cut Preview.
>>
>> So how about we indicate speed when not 1.00x on the Play button?
>> Someone may argue for a temporary waveform display when starting
>> or changing Play-at-Speed. But then would we want to indicate
>> playing the spectral selection in the waveform?
>>
>>
>>
>> Gale
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Finding recent Q2A activity WAS Re: Bug 815 Transcription Toolbar and Transport Toolbar play buttons

James Crook
http://hub.audacityteam.org//index.php/activity
shows recent activity, most recent first.

http://hub.audacityteam.org//index.php/feed/activity.rss
is an rss feed for recent activity

HOT http://hub.audacityteam.org//index.php/questions?sort=hot puts
recent questions and answers at the top.  (Comments are not counted in
this).



On 4/14/2017 8:05 PM, Gale Andrews wrote:

> There is IMO a serious problem with following Q2A.
>
> I would have expected the question on top would have been the
> one that had the most recent activity. I'd have expected that
> links to questions which had been updated since my last visit
> would be displayed as unvisited, and those questions that had
> not changed would be visited links. See Nabble as an example.
>
> Or see how phpBB forum software does it - topics with unread
> posts are red.
>
> Can this be fixed, or is there a trick I do not know? If not, I don't
> have time to wade each question every day to see the latest
> changes (if any). And so I really don't want to add more questions
> to Q2A.
>
>
>
> Gale
>
>
>
> On 14 April 2017 at 11:05, James Crook <[hidden email]> wrote:
>> I suggest a question on hub to tease out the 'correct' design.
>>
>> On 4/14/2017 3:10 AM, Gale Andrews wrote:
>>> Steve wrote in:
>>> http://bugzilla.audacityteam.org/show_bug.cgi?id=815#c15
>>>
>>>      "It seems to me that the "play at speed" button is behaving like a
>>>       "momentary action switch", in that it is issuing a command to start
>>>        an action each time it is pressed. (Momentary action switches are
>>>        like doorbell switches - they return to the "Up" position after being
>>>        pressed).
>>>
>>>        The "Play" button also appears to be behaving correctly as it
>>>        designed to indicate (by the down position) that Audacity is in
>>>        "play mode"."
>>>
>>>
>>> So Steve disagrees with Peter and Paul, I think. And meantime this bug
>>> is going round in circles, and I don't think there is enough consensus
>>> to either close or promote the issue..
>>>
>>> I think standard Play button has got to be down when playing at speed,
>>> if we want the feature that clicking that button restarts at standard
>>> speed at the editing cursor.
>>>
>>> By the same argument Transcription Toolbar does not indicate by
>>> depressing its Play button that you can click that button to restart
>>> play
>>> at speed at the cursor. That seems wrong too, but the visual impact
>>> of having both Play-at-Speed Play button and standard Play button
>>> depressed simultaneously was thought confusing too confusing.
>>>
>>> My issue with the current situation is that you can't tell which type of
>>> playback is in force. This will matter when we finally fix Play-at-Speed
>>> to change the speed on the fly and it will matter if we play only the
>>> spectral selection. I think the key to this is therefore letting the current
>>> behaviour stand but indicating somehow which type of playback is in
>>> force. The main Play button already sacrifices indicating that clicking
>>> it starts single play by showing a Loop symbol when there is looped
>>> standard or looped play-at-speed playback. Likewise for Cut Preview.
>>>
>>> So how about we indicate speed when not 1.00x on the Play button?
>>> Someone may argue for a temporary waveform display when starting
>>> or changing Play-at-Speed. But then would we want to indicate
>>> playing the spectral selection in the waveform?
>>>
>>>
>>>
>>> Gale
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Finding recent Q2A activity WAS Re: Bug 815 Transcription Toolbar and Transport Toolbar play buttons

Gale
Administrator
On 14 April 2017 at 20:51, James Crook <[hidden email]> wrote:
> http://hub.audacityteam.org//index.php/activity
> shows recent activity, most recent first.

I would not easily have guessed that from the "All Activity" name,
but thanks, that satisfies me, I think. I would change the name
if it's customizable.

Peter's question "3-wishes, what would you wish for?" looks like
it will have to be tracked for additions to Wiki Feature Requests,
for any users that are not "us".



Gale


> http://hub.audacityteam.org//index.php/feed/activity.rss
> is an rss feed for recent activity
>
> HOT http://hub.audacityteam.org//index.php/questions?sort=hot puts
> recent questions and answers at the top.  (Comments are not counted in
> this).
>
>
>
> On 4/14/2017 8:05 PM, Gale Andrews wrote:
>> There is IMO a serious problem with following Q2A.
>>
>> I would have expected the question on top would have been the
>> one that had the most recent activity. I'd have expected that
>> links to questions which had been updated since my last visit
>> would be displayed as unvisited, and those questions that had
>> not changed would be visited links. See Nabble as an example.
>>
>> Or see how phpBB forum software does it - topics with unread
>> posts are red.
>>
>> Can this be fixed, or is there a trick I do not know? If not, I don't
>> have time to wade each question every day to see the latest
>> changes (if any). And so I really don't want to add more questions
>> to Q2A.
>>
>>
>>
>> Gale
>>
>>
>>
>> On 14 April 2017 at 11:05, James Crook <[hidden email]> wrote:
>>> I suggest a question on hub to tease out the 'correct' design.
>>>
>>> On 4/14/2017 3:10 AM, Gale Andrews wrote:
>>>> Steve wrote in:
>>>> http://bugzilla.audacityteam.org/show_bug.cgi?id=815#c15
>>>>
>>>>      "It seems to me that the "play at speed" button is behaving like a
>>>>       "momentary action switch", in that it is issuing a command to start
>>>>        an action each time it is pressed. (Momentary action switches are
>>>>        like doorbell switches - they return to the "Up" position after being
>>>>        pressed).
>>>>
>>>>        The "Play" button also appears to be behaving correctly as it
>>>>        designed to indicate (by the down position) that Audacity is in
>>>>        "play mode"."
>>>>
>>>>
>>>> So Steve disagrees with Peter and Paul, I think. And meantime this bug
>>>> is going round in circles, and I don't think there is enough consensus
>>>> to either close or promote the issue..
>>>>
>>>> I think standard Play button has got to be down when playing at speed,
>>>> if we want the feature that clicking that button restarts at standard
>>>> speed at the editing cursor.
>>>>
>>>> By the same argument Transcription Toolbar does not indicate by
>>>> depressing its Play button that you can click that button to restart
>>>> play
>>>> at speed at the cursor. That seems wrong too, but the visual impact
>>>> of having both Play-at-Speed Play button and standard Play button
>>>> depressed simultaneously was thought confusing too confusing.
>>>>
>>>> My issue with the current situation is that you can't tell which type of
>>>> playback is in force. This will matter when we finally fix Play-at-Speed
>>>> to change the speed on the fly and it will matter if we play only the
>>>> spectral selection. I think the key to this is therefore letting the current
>>>> behaviour stand but indicating somehow which type of playback is in
>>>> force. The main Play button already sacrifices indicating that clicking
>>>> it starts single play by showing a Loop symbol when there is looped
>>>> standard or looped play-at-speed playback. Likewise for Cut Preview.
>>>>
>>>> So how about we indicate speed when not 1.00x on the Play button?
>>>> Someone may argue for a temporary waveform display when starting
>>>> or changing Play-at-Speed. But then would we want to indicate
>>>> playing the spectral selection in the waveform?
>>>>
>>>>
>>>>
>>>> Gale
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Audacity-quality mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Loading...