In article < >,
says...
[ ... ]
> predefinedCaptureSetting PredefinedSetting[25];
> PredefinedSetting[0] = {1,0,false,false,false,true,true,false};
> PredefinedSetting[1] = {1,1,false,false,false,true,true,false};
> PredefinedSetting[2] = {0,1,false,false,false,true,true,false};
This syntax only works for initialization, not assignment, so you can do
this:
predefinedCaptureSetting PredefinedSetting[25] = {
{1, 0, false, false, false, true, true, false},
{1, 1, false, false, false, true, true, false},
and so on for all 25 items, or you can do something like:
PredefinedSetting[0] =
PredefinedCaptureSetting(1, 0, false, false, false, true, true, false);
and so on for 25 values.
On a different note, I think I'd define things a bit differently. I'd
probably define the bools as an int (or short, or whatever) and define
some names for bit positions, so your first item would be something
along this line:
Predef[0] = Setting(1, 0, OPTIMIZE_GEOMETRY | RECOMPUTE_NORMALS);
At least to me, "OPTIMIZE_GEOMETRY | RECOMPUTE_NORMALS" seems quite a
bit more meaningful than "false, false, false, true, true, false". The
latter is meaningful ONLY if somebody has memorized the order in which
you've arranged the fields -- and even then, you just about have to
count over to be sure whether a particular "true" is in the third or
fourth position (and adding even a couple more possibilities renders it
much more difficult still).
--
Later,
Jerry.
The universe is a figment of its own imagination.