Bc2000 (for the BCF2000 & BCR2000)

Royce (especially) -

When not specifying .init in globals under $preset, I assume there 
should not be listed any other globals (with the possible exception 
of .name) when the intention is a preset "overlay" - that is, not 
modifying any settings except the controls specified following. This 
way the "basic" preset globals still apply.

Conversely, I assume that specifying .init does not reset other globals 
to some default values. Rather that all usual global variables need to 
be specified, as one cannot know what they may have been previously set 
to.

Are these assumptions correct?

Sorry - in the previous post, I should not have used the 
term "global" variables; the variables are those listed under $preset 
only. Actual "global" settings are not involved.

Art Hunkins

--- In bc2000@yahoogroups.com, "abhunkin" <abhunkin@...> wrote:
>
> Royce (especially) -
> 
> When not specifying .init in globals under $preset, I assume there 
> should not be listed any other globals (with the possible exception 
> of .name) when the intention is a preset "overlay" - that is, not 
> modifying any settings except the controls specified following. 
This 
> way the "basic" preset globals still apply.
> 
> Conversely, I assume that specifying .init does not reset other 
globals 
> to some default values. Rather that all usual global variables need 
to 
> be specified, as one cannot know what they may have been previously 
set 

> to.
> 
> Are these assumptions correct?
>

Thanks for this info, Royce. Your observations rule out the 
possibility of any "overlay" preset - one that keeps values from the 
previous preset except for buttons/encoders etc. newly programmed.

It also means that .init is superfluous.

In any case, it's useful to know what the defaults are. It could save 
quite a bit of typing.

Art Hunkins

--- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote:
>
> Art
> 
> 
> > When not specifying .init in globals under $preset, I assume there
> > should not be listed any other globals (with the possible 
exception
> > of .name) when the intention is a preset "overlay" - that is, not
> > modifying any settings except the controls specified following. 
This
> > way the "basic" preset globals still apply.
> 
> I'll call them preset general parameters (as you corrected in a 
later
> post).
> As Mark pointed out in his excellent guide if you don't use a 
parameter
> the BC sets it for you.
> 
> So send
> $preset
> .name' Just a test"
> .snapshot on
> .request on
> .egroups 2
> .fkeys off
> .lock on
> .tx $F0 $41 $13 12 $F7
> .init
> 
> and you'll get back the same values,
> 
>   but if you now send (worst case)
> $preset
> 
> you'll get back
> 
> $preset
> .name '                          '
> .snapshot off
> .request off
> .egroups 4
> .fkeys on
> .lock off
> .init
> 
> All the parameters are reset.
> Any parameters you sent along with $preset are , of course, set
> correctly but the others are reset.
> 
> > Conversely, I assume that specifying .init does not reset other
> globals
> > to some default values. Rather that all usual global variables 
need to
> > be specified, as one cannot know what they may have been 
previously
> set
> > to.
> 
> So even if you don't use .init all the values you don't send are 
reset

> to the BC's  default values.
> A bit of an unexpected trap there.
> 
> All the best
> 
> Royce
>