Hmm...so Roland, when I discussed this with you via email, I remember bringing up that LDCad doesn't recognize a ROTSTEP as a separate step, which it sounds like you are addressing with this? I mention it because since then I've noticed Lpub3D seems to follow the same logic, ROTSTEPs are only used to set orientation but require a STEP to be paired with to be read as a separate step. MLCad is the one that treats ROTSTEPs and STEPs as steps.
If I had to vote for which program to match, I would say Lpub3D all the way - but maybe this needs to be discussed with Trevor to ensure some consistency.
Edit: I _really_ like the idea that it just sets it based on whatever your current camera position is - very efficient! Maybe make a right-click option on a ROTSTEP in the source view to set the camera back to that position if you need to go back and check?
Edit 2: I realized my error! (see below) Lpub recognizes ROTSTEPs as STEPs. Apologies for causing so much confusion.
If I had to vote for which program to match, I would say Lpub3D all the way - but maybe this needs to be discussed with Trevor to ensure some consistency.
Edit: I _really_ like the idea that it just sets it based on whatever your current camera position is - very efficient! Maybe make a right-click option on a ROTSTEP in the source view to set the camera back to that position if you need to go back and check?
Edit 2: I realized my error! (see below) Lpub recognizes ROTSTEPs as STEPs. Apologies for causing so much confusion.