Hi,
I change a VDR's setup setting from inside a plugin like:
::Setup.UseSmallFont = 0; ::Setup.Save(); // commit the change to setup.conf
This is done only when the plugin's setting is changed. ( in the Store() ).
When changes are accepted with OK, the setup.conf is written but it is immediately overwritten by a Setup.Save() call from cMenuSetupBase::Store(). How can I avoid this ?
Is there a more orderly way to modify VDR's setup settings ?
On 02/12/08 18:48, sundararaj reel wrote:
Hi,
I change a VDR's setup setting from inside a plugin like:
::Setup.UseSmallFont = 0; ::Setup.Save(); // commit the change to setup.conf
This is done only when the plugin's setting is changed. ( in the Store() ).
When changes are accepted with OK, the setup.conf is written but it is immediately overwritten by a Setup.Save() call from cMenuSetupBase::Store(). How can I avoid this ?
Is there a more orderly way to modify VDR's setup settings ?
Why do you need to change VDR's setup settings? That's VDR's own business ;-)
Klaus
I change a VDR's setup setting from inside a plugin like:
::Setup.UseSmallFont = 0; ::Setup.Save(); // commit the change to setup.conf
This is done only when the plugin's setting is changed. ( in the Store() ).
When changes are accepted with OK, the setup.conf is written but it is immediately overwritten by a Setup.Save() call from cMenuSetupBase::Store(). How can I avoid this ?
Is there a more orderly way to modify VDR's setup settings ?
Why do you need to change VDR's setup settings? That's VDR's own business ;-)
:) True.
The skin plugin I am trying has its parameters buried deep inside submenus. I want the font setting of the skin displayed under the "OSD-Expertmenu". And would like to change it when ever the skin's settings are changed - since they are related.