[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] clarification of render_obj.c and gradient themes



Am 16.03.2012, 19:44 Uhr, schrieb Paul Wratt <paul.wratt@gmail.com>:

I do not see any problem here (except that rflags is useless - does anyone
know what REND_NAES3D might mean?).

I would guess its from one of Ozk's wild forays into the (NAES)
unknown, maybe he was trying to reproduce some NAES styles.. It seems
to be centered around 3D style drawing

I defined it and set NAES3D in rflags, but could not see any difference. I'll wait a little and then remove rflags.

static struct xa_gradient box_gradient =
static struct xa_gradient box_gradient2 =
static struct xa_gradient text_gradient =

those last 3 should (also?) be in each gradient file for theming
continuity

They are not used and thus not needed - XaAES stops reading at EOF. But if
you want you can add them to the other gradient-files (disable with
n_steps=-1).

I'll add them to current gradient files as how they are set in
render_obj.c - so there is no conflict if structs are also defined in
gradient file (I guess not if they are working for you)

It would not make any difference, except XaAES would read have to read some more bytes it already knows.

But if someone wants to make his own gradient from those, it might be helpful.

when you say "not needed" and "disable with .." do you mean that they
are not rendered anywhere, or just not with "the other" gradients

Not needed in the standard-gradients (g_blue etc.).

I wanted to write it (and some other config tools) in GFA because I
could use the actual gradient code from XaAES as external objects, but
GFA is not CF friendly, which defeats the purpose of most of the

What a luck ;-)

--
Helmut Karlowski