Scrolling suggestion

All,

Just been playing with ChatGPT and getting a little flustered with the length of the project when I had not built up much code. It was adding blank lines in everywhere and I soon ran up several hundred lines of code - well a lot of code but the number of code lines was far exceeded by the blank lines and separators for function etc etc.

I managed to resolve that by suggesting that blank lines should be minimised routinely and that seemed to work.

But, I also got frustrated with scrolling through several hundred lines of code to edit the odd lines. I know you can flick the page etc but thought a button may help.

On the left of the editor you see a grey line which reflects the size of your page and position of it, scrolling moves the line up and down showing you where you are in your masterpiece.

My suggestion is that a button is placed overlapping that grey line (but not interfering with its function) which you can drag up or down to scroll through the code with the button moving proportionate to the size of your code screen so the button reflects the percentage position on the code. In other words - when the button is at the top of the code window you are at the top of the editor window, button at bottom code window is at bottom of the code editor.

Just thought that may help if you have long code windows.

Views ???

P.s I know you can divide code across several tabs but even then some tabs can get quite long, especially when using ChatGPT.

Are you using pro?

The pro move is to use working copy with codex and have ChatGPT edit your code directly.

Make a GitHub repo with working copy, use website Codex to assign that repo as an environment, then from any Codex that can reach that environment, including on the phone, you can give ChatGPT instructions and let it make the changes itself. It will make them as a pull request, which you can then confirm, which then will modify the repo as a distinct commit, so you can roll it back if you need to.

Then to see the changes in action, pull them into Codea using working copy.

It might sound complicated but for big projects it can save a lot of time.

1 Like