RE: Re: OPTIONS??

[Tony Tofts]

> Sorry Tony ....So the optional message stuff ie rows,
> columns etc doesnt have to be listed....

As an example let's say tvosd has a built-in row= (with a range of 1 to 20
say)

If a user sends an osd.basic message with row=15, then tvosd should display
on row 15 etc

If tvosd has a built-in default of row=5 then if the user _omits_ row= in
his message then tvosd should use 5

In the above example config.list/config.current would not include the row
option

But let's say you _want_ the user to be able to override your defualt of
row=5, you could create a config item of defaultrow (though row would also
be acceptable)

Then if the user _omits_ row= instead of defaulting to row=5 tvosd should
default to row=<current value of defaultrow>
In this case defaultrow _must_ appear in config.list/config.current

I've used defaultrow instead of row in the example to show that they are 2
different things

> Should i have it listed same as Peters TVOSD ...RECONF=ROW etc....???

I would recommend option=row

The possibilities are

Config=row means _must_ be set, _cannot_ be changed

Reconf=row means _must_ be set, but _can_ be changed

Option=row means it doenst have to be set (assumes a pre-defined default),
and can be changed

Reconf would normally be used for something like a comport that _needs_ to
have an initial value set

If tvosd _didnt_ have a default of 5 (or whatever - preset on boot up) then
yes reconf would be correct. But as youre probably already storing a
default
row, then option is probably the one to go for.

Regards
Tony