Difference between revisions of "Delayed playback response on click info"
From Rivendell Wiki
(Created page with "<pre> Date: Sun, 18 Nov 2007 20:21:06 -0500 From: Fred Gleason <email@example.com> Subject: Re: [RDD] ALSA - no sound but meters work To: User discussion about the Riv...")
Latest revision as of 15:24, 12 March 2018
Date: Sun, 18 Nov 2007 20:21:06 -0500 From: Fred Gleason <firstname.lastname@example.org> Subject: Re: [RDD] ALSA - no sound but meters work To: User discussion about the Rivendell Radio Automation System <email@example.com> On Sunday 18 November 2007 20:10, Dan Mills wrote: > Not easily (it is the standard behaviour of the graphical interface > toolkit we use), but in practise you very quickly become used to it (and > even start taking advantage of it). > Particularly on a touch screen having some way to abort an accidental > touch (just drag to an insensitive area before releasing) is useful. This behavior is quite intentional. Say you're an announcer that wants to start a cart at a particular point during a live read. You really don't want to have to take your eyes off the script to make sure you've positioned your 'pointing device' (be it mouse, finger or whatever) correctly. This way, you can do so *before* you start your read, and just 'letting go' triggers your audio. Cheers!