Quote Originally Posted by WaynePhillipsEA View Post
Yes, you can have more than one component per twin file, that's no problem. The quick-fix suggestion is there because in the first releases of tB we only allowed a single .twin file, so devs were naturally stuffing many, many components into a single file and they wanted a quick way to split them up once we started allowing multiple .twin files. You can safely ignore that suggestion, and tB wont mind at all.

With regards to saving the generated designer code into tB; it seems what you really want is an extensibility API, like you have in VBA. A simple extensibility API would be easy to implement, but the main problem would be that after making a change to a file in the tB virtual filesystem, the compiler will automatically kick in and 'reset' the debug session, including all running code and all global variables because it doesn't yet support Edit & Continue. Until Edit & Continue is supported, we could potentially offer a feature in the extensibility API to turn off the compiler so that it simply doesn't notice the changes to the files that you've made, until your designer exits. Needs a little more thought, but should be achievable.
That makes sense, it would have to be a simpler implementation at first. It could be worth thinking about later. I will help by exposing some events from the designer and I'll make an option to save to the clipboard for quickly transferring the designer code over to tB. It can still save a lot of time designing the initial form starting point. I still have to do a lot of testing to make sure all of the properties save/open correctly.