RE: [Flash Operator Panel] Advice on op_buttons.cfg file generation

["Ian Plain" <ian@xxxxxxxxxxxxxxxxxxx>]

Try.

include => button.d/*.cfg

As the follwing works fine

include => op_butt_1_11.cfg
include => op_butt_14_24.cfg
include => op_butt_27_37.cfg
include => op_butt_40_50.cfg
include => op_butt_53_63.cfg

Thanks
Ian Plain 
http://www.cyber-cottage.co.uk 
Get us to call you 
http://www.cyber-cottage.co.uk/voip/callback.htm
-----Original Message-----
From: Safet Susic [mailto:panoramisk@xxxxxxxxx] 
Sent: 31 July 2008 18:56
To: operator_panel@xxxxxxxxxxxxxxxxxx; t.sawah@xxxxxxxxx
Subject: Re: [Flash Operator Panel] Advice on op_buttons.cfg file
generation


In op_buttons.cfg, I included this :

include button.d/button_*.cfg

In buttons.d, I stored :
button_4123.cfg
button_4124.cfg
...

I didn't work.
Too bad it didn't as it could provide a safe and easy way to add, change
and remove button definitions. I'm wondering if I will add myself this
wildcard capability without breaking FOP portability or features.


Does anyone foresee any danger (as I won't be able to test on several
platforms) ?
Regards

No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.5.8/1582 - Release Date:
30/07/2008 18:37
 

No virus found in this outgoing message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.5.8/1582 - Release Date:
30/07/2008 18:37