Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Workspaces don't save window-splitting status #22497

    jjasmith4
    Participant

    Yes, it’s very handy. A workspace, almost by definition, should restore the whole editing environment to exactly what it was when the user saved the workspace. Check out Excel’s workspaces.

    in reply to: Can't reliably predict editor.Documents.Item indices #21938

    jjasmith4
    Participant

    OK — that’s probably a better way to code it. While I disagree with indices changing, I’ll accept it, but I’d like it clarified in the documentation for Documents.Item. Also it’s unclear that Documents Item indices go from 1 to Documents.Count, rather than 0 to Documents.Count-1.

    Finally, I still with there were a way to activate a document by using its name, e.g., editor.Documents.Item(“MyDoc.txt”).Activate(). Check out how Excel uses either names or numbers to index its Workbooks, Worksheets, Charts, etc., collections. It would make for shorter and more reliable code.


    jjasmith4
    Participant

    OK, got it. To me it’s unclear what the button’s tooltip “Heading” and the choices’ tooltips “Heading (0-4)” mean. How about “Heading rows (n)”, where n is the current setting, and “(0-4) heading rows”?

Viewing 3 posts - 1 through 3 (of 3 total)