[mythtv-users] "Default Settings" notification on playback

[Tom Dexter]

On Wed, Oct 8, 2014 at 4:46 PM, Hika van den Hoven <hikavdh at gmail.com> wrote:
> Hoi Tom,
>
> Wednesday, October 8, 2014, 10:43:19 PM, you wrote:
>
>> On Wed, Oct 8, 2014 at 11:47 AM, Hika van den Hoven <hikavdh at gmail.com> wrote:
>>> Hoi Karl,
>>>
>>> Wednesday, October 8, 2014, 5:45:27 PM, you wrote:
>>>
>>>
>>> How do you shorten the time. Since 0.27 I all the time get an annoying
>>> pop-up after waking the frontend that it's connected to the backend.
>>> As if I need to know that it works. Telling that it can't connect, if
>>> it can't, is enough.
>>>
>>> Tot mails,
>>>   Hika                            mailto:hikavdh at gmail.com
>>>
>
>> I can't recall when it was, but quite some time ago the any
>> configuration for those OSD timeouts (which I believe used t be
>> controlled by themes??) was removed.
>
>> For myself I found most all of the default timeouts way to long.  I've
>> been using this patch ever since (this works with 0.27.3).  As far as
>> I know this is the only way to change those.  Someone correct me if
>> I'm wrong:
>
>> --- libs/libmythtv/osd.cpp    2013-12-04 15:54:35.000000000 -0500
>> +++ libs/libmythtv/osd.cpp    2013-12-04 15:54:56.000000000 -0500
>> @@ -157,7 +157,7 @@
>>      m_fontStretch(100), m_savedFontStretch(100),
>>      m_FunctionalType(kOSDFunctionalType_Default), m_FunctionalWindow(QString())
>>  {
>> -    SetTimeouts(3000, 5000, 10000);
>> +    SetTimeouts(2000, 2500, 10000);
>>  }
>
>>  OSD::~OSD()
>
>> Tom
>
> Thanks! I still have to upgrade my frontend to 0.27.3 so I'll apply it
> then.
> What is the meaning of the three values in the SetTimeouts function? I
> assume it are milliseconds.
>
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com
>

Those are the default milliseconds for the short, medium, and long OSD
timeouts respectively.  The defaults are 3, 5, and 10 seconds.  I
can't recall which tend to get used for which, but you'll be able to
tell based on the current behavior.  As you see I left the 10 second
one alone.  That tends to get used only for things that I usually
*want* staying there that long.

Just note that those timeouts *do* include any OSD fadeouts...that is
it's the time from original display until the text is totally faded.

I especially found the timeouts far too long when jumping forward and
back etc.  Those changes are about perfect for me.

Hope this helps!

Tom