What might help with that is breaking the different portions into seperate library (I think .bm or .bi) files and including them.
But if like me, you prefer all your code in one file (which eliminates dependency issues), you can add comments to the top and bottom of each section that make it easy to jump to, e.g.,
That way you can do a find and simply enter pound sign + {section name} to go to the top, and I think doing a search will start from that line (conversely, to jump to the bottom enter @ sign + {section name}).
I find the QB64PE IDE to be decent, but for extensive editing of big files, I use Notepad++ which has much better editing features (including the option to search/replace in only the selected text) and then when I'm ready to compile/run, I select all, copy & paste into the IDE and run from there.
Hope some of this helps - good luck!
But if like me, you prefer all your code in one file (which eliminates dependency issues), you can add comments to the top and bottom of each section that make it easy to jump to, e.g.,
Code: (Select All)
' BEGIN MYSECTION #MYSECTION
(your code here)
' END MYSECTION @MYSECTION
' BEGIN SECTION2 #SECTION2
(more code)
' END SECTION2 @SECTION2
etc.I find the QB64PE IDE to be decent, but for extensive editing of big files, I use Notepad++ which has much better editing features (including the option to search/replace in only the selected text) and then when I'm ready to compile/run, I select all, copy & paste into the IDE and run from there.
Hope some of this helps - good luck!

