Quote:
Originally Posted by Vagalume
I think I have to delete more original code it interferes which what I am trying to do.
Which part of the previous code have you deleted to build your tcp tracks from scratch?
|
I started with a "clean sheet" to begin with. I then pasted in the "global" section from V6. At some point in the future, once I understand what that stuff means, I will either leave it as it is or change it to suit my needs. I am guessing that some of those lines will not be required for my purposes.
The TCP code is stuff I have either typed in from scratch or copied from another theme. But when I copy from another theme there are always tweaks required so pretty much all that code ends up being mine, if you know what I mean.
This is my complete code as it stands right now. Note that I have changed the font section to suit what actual font name/style and size that is available to my theme.
Code:
#>-- GLOBALS --
version 6.0
use_pngs 1
tcp_showborders 0
mcp_showborders 0
transport_showborders 0
tcp_vupeakwidth 2
mcp_vupeakheight 2
mcp_mastervupeakheight 4
mcp_altmeterpos 0
use_overlays 0
tcp_vol_zeroline FF666666
tcp_pan_zeroline 66000000
mcp_vol_zeroline FF666666
mcp_pan_zeroline 85000000
trans_speed_zeroline 85000000
gen_vol_zeroline FF000000
gen_pan_zeroline FF000000
item_volknobfg 85000000 FF778485 00474F4F
mcp_min_height 240
tcp_master_minheight 56
mcp_voltext_flags 5 5
tcp_voltext_flags 12
tinttcp 298
peaksedges 0
no_meter_reclbl 1
tcp_heights 4 25 50 64 ; supercollapsed, collapsed, small(norecarm), recarm size
tcp_folderindent 10
envcp_min_height 27
; -- WALTER --
; -- Fonts --
; font #1/10/15/16 - calibri regular 8
; font #2 - calibri regular 9
; font #3/5 - calibri regular 10
; font #4 - calibri regular 11
; font #6 - calibri regular 12
; font #7 - calibri regular 13
; font #8 - calibri regular 15
; font #9 - calibri regular 4
; font #11 - calibri regular 16
; font #12 - calibri regular 18
; font #13 - calibri regular 20
; font #14 - calibri regular 22
; -- Track Control Panel --
clear tcp.*
set tcp.foldercomp h>46 [54 47 19 19 0 1 0 1] [0]
set tcp.folder h>46 [35 47 19 19 0 1 0 1] [0]
set tcp.size [260 70]
set tcp_idx_w 30 ; -- Sets the width of the Track ID area
set tcp.trackidx h<20 [0] [0 0 tcp_idx_w tcp.size{1} 0 0 0 1]
set tcp.trackidx.color [255 255 255]
set tcp.trackidx.font [6]
set tcp.trackidx.margin [0 470 0 470 0.5]
set tcp.label h<20 [0] [35 3 150 18 0 0 0 0]
set tcp.label.margin [3 0 0 0]
set tcp.label.color ?recarm [255 0 0] [255 255 255]
set tcp.label.font [4]
Worth noting that, at this time, I am not bothering with indenting the code. I know that I should do but I am not sure yet which is the best method of doing this. When I used to code in AutoLISP the idea was that you indented each new bracketed section if you couldn't get it on a single line. But if you don't indent, the code still works.
And a quick word on this part of the code:-
Code:
set tcp_idx_w 30 ; -- Sets the width of the Track ID area
set tcp.trackidx h<20 [0] [0 0 tcp_idx_w tcp.size{1} 0 0 0 1]
I only created the tcp_idx_w variable, set here at 30, so that I could edit that easily without having to remember where it lives in the main code for that element.
Just an idea at this time and not essential
cheers
andy