Ximon was talking about it in the IRC awhile back.
[21:36] <@Ximon> But I have some really cool ideas for TPT++
[21:36] <@Ximon> Like tabs and stuff
[21:37] <gajbooks> Creates a tiny bit of pressure then expands like DEUT or MERC to a certain extent when heated enough.
[21:38] <gajbooks> Ximon: What do you mean by tabs? Multiple simulations that you can switch between?
[21:38] <@Ximon> Yes
[21:38] * Cr15py (~Cr15py@CPE001d7e342322-CM000e5cde4dfc.cpe.net.cable.rogers.com) Quit ( Ping timeout: 250 seconds )
[21:39] <gajbooks> Both running at the same time, or pausing when in other tabs?
[21:39] <@Ximon> Probably one at a time
[21:39] <@Ximon> 2 would be a bit slow
[21:40] <Lockheedmartin> Save one temp and start again when activate.
[21:41] <@Ximon> Well, you'd have to do that with TPT
[21:41] <@Ximon> In TPT++ you can actually have 2 loaded at the same time.
[21:41] <@Ximon> I'm trying to make the components reusable in many situations
[21:42] <@Ximon> For example, TPT uses 3 separate pieces of code for rendering scenes,
[21:42] <@Ximon> One for the main game renderer with fancy graphics, 1 for the OPS save format and 1 for the PSV save format
[21:43] <Lockheedmartin> Interesting
[21:43] <@Ximon> It's a pain to maintain, because if you add any new features that have their own render code, you end up having to exclude them from the thumbnail renderers for each save format.
[21:44] <@Ximon> TPT++ solves this by making a reusable component called "render" which can output an image from game data
[21:44] <@Ximon> So there's just one component managing all the rendering in TPT++
[21:44] <Lockheedmartin> Very interesting.
[21:44] <@Ximon> Another use would be to have 2 previews at once.
[21:44] <@Ximon> You could have a normal view of the game, and in another window, you could have the same simulation but in heat view