I have one program with 6000+ program words and 1700+ rungs. My rungs are tall as I have all the documentation fields filled in for each element I use. Today, I was paging down the program looking for a specific section. The slider on the right hand side is pretty coarse when you have lots of lines. What occurred to me is that the documentation editor has special buttons to get to the next/prev page, next/prev kind of element, etc. Why not the ladder editor too?
I use stage programming and blocks to organize the ladder logic. If it were possible to jump to the next/prev/topofcurrent Stage or next/prev/topofcurrent Block it would facilitate this eye ball scanning. The thing that you would check (The control-k comment or other advanced document control tag) would always be at the top of the screen after the operation so it would be much easier to see if the one just scrolled to was the one you wanted. I don't use nested power rails, but for those who do, using those commands/tags as stopping points might also be useful.
We're probably talking DS7 by now. But consider this an added advantage of using blocks and stages.
Roger
Topic: how about "intelligent" scroll buttons in ladder view? (Read 10218 times)