Quote:
Originally Posted by SOgNARd=oubt
I just stunbled on the White Tie article about FLOW and read through it.
My rtconfig doesn't have any FLOW commands in it but it sure looks like my Theme has some tcp characteristics that shuffle and or hide elements in a FLOW-like manner.
I guess maybe I am looking for a way to lock down the elements so they do not FLOW?
Any tips?
Thank you.
|
If you read a bit further in the guide
it will go on to tell you that without specific
commands, the 'default_rules.txt' file will take
precedence over rtconfig. Nevermind this
file, however, as you plan on writing
a complete rtconfig. Reading further in
the guide, you will find a command that
tells REAPER not to draw an element at
all, the syntax is set tcp.recarm [0]
of course this works on most elements.
Another thing to be aware of is that
the flow command is not a command.
It is a macro. It has nothing to do
with WALTER or your theme. It only
applies to the default 5 theme. Beyond
WALTER are macros, variables,
preprocessors, coordinate lists, etc.,
that can be used to minimize the
workload of themebuilding, editing,
altering, etc. and minimize data
redundancy and therefore data footprint,
and maximize efficiency and load time.
As WT said in the guide, it is best to
read the entire guide before building
a theme, I would say at least skim it
so it's concepts are not foreign, and
also the SDK, so that you at least
know where to look when your stumped.
there is also the 'Power of pink'
document that you will need, and more
like the open office document that
calculates track tinting...and the list
goes on, but for starters, I would say
grab a theme close to what you want
from the stash, dissect it, and refer
to the SDK and WALTER user guide for
every little thing you don't know.
Never