justin = {
main feed
,
music
,
code
= {
cockos
,
reaper
,
wdl
,
ninjam
,
jsfx
,
more
}
,
askjf
,
pubkey
};
Ask Justin Frankel
No reasonable question unanswered since 2009!
Suggested topics: programming, music, sleep, coffee, etc.
Note: please do not ask questions about REAPER features, bugs or scheduling, use the
forums
instead.
Name:
Ask:
Human (enter yes):
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Question:
Reaper is such a great program, and I love that you aim to maintain full backward compatability. With that in mind, are there any parts of the program (code-wise or conceptually) that you wish you'd done differently from the start, in order to save major headaches in the present day? Are there any bits of code that you'd like to throw away or re-do, but simp
Asked by BennyG (86.27.83.x) on January 24 2014, 11:17pm
Reply on January 25 2014, 3:15am:
Heh just yesterday we redid the way regions are stored -- there were markers before regions, so when adding region support I implemented regions as a special pair of markers. So since then (2006), any time you wanted to check the size of a region, you had to do a full linear scan of the list to find the matching side. That was a fun thing to fix-- it took a few hours, and you get to remove a bunch of stupid code. There were only a few spots that needed new code written, one of which being RPP file reading/writing, where you get to figure out the most efficient way to encode the region/marker data in such a way that old REAPER versions (2006 to current) will properly read it back. Fun!
Comment:
Your Name:
-- Site Owner's Name:
(for human-verification) Comment:
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Copyright 2025 Justin Frankel
.
|
RSS