Documentation Editor

[Bolt]

Would it be feasible for the Edit Mode (Ctrl+E) and Accept (F8) functions to work when the Doc Editor is open?  There's no telling how many times I've tried to use Ctrl+R inside the Editor only to have to go back to a program block, hit Ctrl+E, and return to the Editor.  Or not found what I was looking for, gone back to the program, hit F8, and returned to find my new elements created in the Editor.

[franji1]

That sounds like a good idea - I don't see any possible strange "secondary" issues.

Some operations must be context-based, like Find (Ctrl+F), so you can't do a Ladder Find from within Documentation Editor for the same reason you can't do a Documentation Find from the Ladder Editor.

[Bolt]

Great!

Since you kinda brought it up... How about a way to jump from the selected element in Doc Editor to the first instances in the ladder code, and from the program blocks you can then Ctrl+Shift+F from there to keep walking through the instances?

[BobO]

Great!

Since you kinda brought it up... How about a way to jump from the selected element in Doc Editor to the first instances in the ladder code, and from the program blocks you can then Ctrl+Shift+F from there to keep walking through the instances?

I think all of this is possible. Since Ctrl D already does a search, I think Ctrl L (which already goes to a ladder view), could do a search as well.

For the record, Ctrl + and Ctrl - already walk instances.

[Bolt]

Great!

Since you kinda brought it up... How about a way to jump from the selected element in Doc Editor to the first instances in the ladder code, and from the program blocks you can then Ctrl+Shift+F from there to keep walking through the instances?

I think all of this is possible. Since Ctrl D already does a search, I think Ctrl L (which already goes to a ladder view), could do a search as well.

For the record, Ctrl + and Ctrl - already walk instances.

Sounds workable to me.  I did not know/remember about Ctrl L, had been doing it with Ctrl Tab

The issue I have with Ctrl + and Ctrl - is once you hit a block with multiple values, it tends to lock out on the next step.  Say V0 is your pointer, it will walk through it's use as a contact, etc, but once you get to COPY instruction, it sticks there not knowing which element to chase.  Any work around I'm missing here?

[BobO]

The issue I have with Ctrl + and Ctrl - is once you hit a block with multiple values, it tends to lock out on the next step.  Say V0 is your pointer, it will walk through it's use as a contact, etc, but once you get to COPY instruction, it sticks there not knowing which element to chase.  Any work around I'm missing here?

I wouldn't call that a bug, but it is definitely an undesirable implementation. I will look into whether that could be altered to retain the element that got you there, rather than grabbing the first in the list. Might be trivial...might not.

I'm also looking into whether we could add an xref tooltip to the element field in the doc editor. Rather than blindly jumping to the first usage, it would give you the same options that you get from the ladder display.

[Bolt]

Great!

Since you kinda brought it up... How about a way to jump from the selected element in Doc Editor to the first instances in the ladder code, and from the program blocks you can then Ctrl+Shift+F from there to keep walking through the instances?

I think all of this is possible. Since Ctrl D already does a search, I think Ctrl L (which already goes to a ladder view), could do a search as well.

I really dig the new jump to logic button in the Doc Editor (and how it turns gray when element not used). However, now it would be nice to have it linked to Ctrl L.  I know, I'm picky....