@Mirabella
Well, using this program to learn CS is not a good idea I’m afraid. The generated code was made to work not look pretty haha.
It basically generates a unique *label over each action, text, condition etc. and then uses “goto label” for each connection to said bubble. It’s efficient to generate, and it just works when you run your CS game in the browser, but it’s not a good way to learn programming.
In case you aren’t aware, the far right button on the file menu will display the generated CS code for the currently active scene. (just not in a splitscreen)
If you have the code editor Notepad++ it will automatically refresh any opened file that’s been modified. So, if you open the generated .txt file in N++, every time you save your project, the code changes will show up on there. Making it kind of a hacky way to get splitscreen. lolz
Too bad about your desk 
but yes, I had the same problem when working on my laptop, which is why I added the spacebar controls. (:
I believe it was @stainedofmind who suggested arrow key movement and zoom using Q and E a few posts back as well.
Now, I have been planning on rewriting the CS generation code. If I break the project down into a tree-list first, then follow each branch individually, I can produce CS code that could potentially represent what a real human being would write. This is all theoretical and floating around in my head though.
To be able to look at the code and either modify it or the project and have them affect each other is going to be really difficult to implement. Not saying that it’s not possible, or that I’m not willing to do it, just that I feel it would be impractical and a little beyond the scope of why I created Chronicler. If you want to write your own CS code, I highly recommend @CJW’s editor. [Tool] ChoiceScript Development Environment - #155 by lordirishdas
copy and paste this hosted Choice of Dragon source into it and mess around. CS is quite straitforward once you get the hang of it. (:
https://www.choiceofgames.com/dragon/scenes/startup.txt
Having said all that, a splitscreen view of the code is not overly difficult to implement, if you (or anyone else) still feels that it would be a good addition, I can add it to my planned features list.
So, how would ya’ll feel is the best use of time for the next update?
- A separate bubble for choices.
- A rewrite of the CS code generation.
OR - Finishing the CS code import function?