If you look inside the step LFO, you can see that the values for each step are stored in a VST preset array. That's just like a regular float array, it just has added functions so that VST hosts can read/write the array.
If you want to use an individual bitmap knob for each step, then the array needs a way to know which knob is being moved, so that it can write the value to the correct array index.
Here's a little osm that shows one way to achieve this...
The only change I've made to the animated knob is to add a trigger output from the 'interact' link; this just generates as trigger as you press the mouse button on the knob - the trigger is then used to switch the array index, and select the correct knob to update the array value.
Hope that helps, it will be nice to see what lovely GUI you replace those horrible blocky graphics with!
@djbrynte. Most of what you have learned has been shared publicly so that we can all learn from it, you should be prepared to share your knowledge in the same spirit - it is not polite to expect people to share their e-mail, MSN etc. unless you have arranged a specific collaboration. You have posted a lot of questions and requests over the last few days, that's fine, it is what the forum is here for - but the nature of the questions show that you are not as 'pro' as you would like to think; you are not in a position to expect people to share their personal addresses in return for your assistance.
I'm sorry if this seems harsh, but it is for your own good - you will annoy people into not helping you if you continue to pester - chill out a little and you will enjoy your time here much more.
Feel free to use any schematics and algorithms I post on the forum in your own designs - a credit is appreciated (but not a requirement).
Don't stagnate, mutate to create. Without randomness and serendipity the earth would be just another barren rock.