Pi - Long lines of Basic not shown in !Edit
John Sandgrounder (1650) 574 posts |
I have a large Basic program with lines of Basic statements which fill the 1920 screen width in !Edit. Except that they don’t display completely. The end of the line is missing. The program is not corrupted, but it is difficult to edit. |
|
Steve Drain (222) 1620 posts |
You might consider this. A tokenised line cannot be more than 251 characters. Edit expands tokens, making a displayed line longer, and maybe it has a maximum length. In any case, such a long line cannot be retokenised. Was the long line produced by a crunching program? If so, go back to the uncrunched source to edit it. |
|
John Sandgrounder (1650) 574 posts |
The lines (more than 1) were originally produced on a RiscPC (or maybe even an Acorn A410) and have since been edited on the RiscPC and on Virtual Acorn. The lines are less than 250 characters (tokens expanded) and are retokenised successfully when the file is saved. The file has never been crunched (or renumbered). If I change the screen mode to 1280×720 (or less), the program edits perfectly well with the full length of the line displayed (albeit, wrapped as it always did on the lower resolutions screens of the older computers). |
|
Chris Hall (132) 3554 posts |
Pure text files are also shown in !Edit with the ends of very long lines shown as spaces. I find this mildly irritating. |
|
Chris Evans (457) 1614 posts |
!Edit has always had draw/redraw problems especially with long lines/long files. |
|
Rick Murray (539) 13840 posts |
Does anybody else with big display and BASIC code in !Edit see redraw problems? I know of erratic redraw errors with large binaries, just wondering if this one reported here is triggered by the way the program in question is laid out or if any BASIC program with long lines would trigger it? |
|
John Sandgrounder (1650) 574 posts |
This is not triggered by anything special. (and does not need a Basic file) Just open !Edit with a 1920×1080 screen. |
|
John Sandgrounder (1650) 574 posts |
NO – Please NOT. CTRL C and CTRLV already have very specific functions unique to RiscOS. |
|
nemo (145) 2546 posts |
Fixed it for you. It would best be an option (which Edit already supports) or be switchable by the presence of the ClipboardHolder module. |
|
Steve Pampling (1551) 8170 posts |
Always a good idea – I find pressing Ctrl-V when using nano1 to edit something somewhat irritating. 1 You need to geek around a little to understand the reference (like I don’t understand why Ctrl-W initiates a search and Ctrl-O writes without exiting. What was wrong with Ctrl-F and Ctrl-W for god sake? Or did they just select random keys?) |
|
Chris Evans (457) 1614 posts |
True, whilst being slightly more convenient sometimes, being out of step with the rest of world should only occur when very significant benefits accrue. Having a configuration option to revert for those people who don’t use other OSs seems a good way to satisfy almost everybody.
Do you mean Edit supports options or options re CTRL C & V can be set in the latest !Edit ? |