COMMENT/DOC, command?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • COMMENT/DOC, command?

    Im using v4.1 and noticed that when I type:

    "COMMENT/DOC"

    in the command window, the compiler automatically adjusts my code back to "COMMENT/OPER", which of course I dont want.

    I have to change the COMMENT to "Document" by right-clicking on the command and using the dialog box option button instead. This of course changes the corresponding code in the edit window to "$$ "

    However typing "$$" in the edit window (as a short cut) or even "$" is apparently disabled in the software?

    Is there a known work around so that all of my comments are placed as "DOC" instead of "OPER" by default?

    Thanks
    Mr. Comment
    SCIROCCO-NT 13-20-10
    B3C-LC Controller (Leitz Protocol), SP600M, TP200
    PCDMIS CAD++ v4.3 MR1(Build: 12/11/08)
    sigpic

  • #2
    Take your cursor out of the comment after you edit it. I noticed on lower versions than what you are using if you edit either the type of comment or the text then go from command mode to report mode the edit does not stick. Make the edit then put your cursor somewhere else in the program to make it stick bfore doing anything else. If that does not fix it then you have an issue I'm not familiar with

    Craig
    <internet bumper sticker goes here>

    Comment


    • #3
      You don't start by typing??

      I start with com - it fills as comment, I hit tab,....start with D, Doc should come up.

      I never use menus for comments,.....

      Still on 3.7 here,.. 4.1 may be different, but typing in the edit window helps many things.
      http://baggy3.info/signani3.gif
      Excercise your mind,..... muscle works better than fat!!

      Comment


      • #4
        Helpful hint...
        With cursor sitting on the toolbars, right click, choose customize, go to keyboard select 'insert" from pulldown menu on the left then go find comment(it's near the bottom), put your cursor in the keystroke box and choose alt and c (while holding down the alt button), click assign, nad then ok. Now whenever you hit the keystroke you have the comment box come up. Does that help you at all?
        sigpic

        James Mannes

        Comment


        • #5
          Unfortunately there is a difference between v3.7 and v4.1 for this command.

          I was using v3.7 and I typed it in just as Paul mentioned earlier. Which of course was very easy, but its doesn’t work in v4.1 even though it initially shows as an option, it just doesn’t stick, even prior to navigating out of the command line with the cursor. The only way it sticks as a doc comment is by using the Comment dialog box. This is probably a bug.

          James’ shortcut key idea may be as close as I can get for now, this way it would at least present me with the correct option so I could select in the first place, but it’s something I will have to force myself to get use to, I don’t like dialog boxes.

          I would like it better if I could set a parameter so that all of the comments were "DOC" by default instead of operator, or if I could just type in the command text “$$” for the doc comment.

          Maybe this will be corrected in v4.2?
          Mr. Comment
          SCIROCCO-NT 13-20-10
          B3C-LC Controller (Leitz Protocol), SP600M, TP200
          PCDMIS CAD++ v4.3 MR1(Build: 12/11/08)
          sigpic

          Comment


          • #6
            Originally posted by MrComment
            Is there a known work around so that all of my comments are placed as "DOC" instead of "OPER" by default?
            Hi MrComment,
            In 4.1 COMMENT/DOC is now done by typing COMMENT/$$ and then pressing TAB. This inserts a programmer comment of $$ in the Edit Window

            It no longer recongizes typing "COMMENT/DOC" to create a DOC command.
            Jared Hess - Techwriter @ WAI
            [View 2008 Reporting Tutorials Here]

            Comment


            • #7
              This is provided by Jared Hess. Got it from the WILCOX site. Don't know if it will help but here it is anyways.
              Last edited by JamesMannes; 08-03-2007, 09:27 AM.
              sigpic

              James Mannes

              Comment


              • #8
                Thanks James and Jared.

                Both of those solutions work well.
                Mr. Comment
                SCIROCCO-NT 13-20-10
                B3C-LC Controller (Leitz Protocol), SP600M, TP200
                PCDMIS CAD++ v4.3 MR1(Build: 12/11/08)
                sigpic

                Comment


                • #9
                  Originally posted by JaredHess View Post
                  Hi MrComment,
                  In 4.1 COMMENT/DOC is now done by typing COMMENT/$$ and then pressing TAB. This inserts a programmer comment of $$ in the Edit Window

                  It no longer recongizes typing "COMMENT/DOC" to create a DOC command.
                  Why is this?? To me the program looks like a jumbled mess with these types of comments in. I really liked the "COMMENT/DOC", made it clear and concise.

                  Comment


                  • #10
                    Originally posted by John Kugler View Post
                    Why is this?? To me the program looks like a jumbled mess with these types of comments in. I really liked the "COMMENT/DOC", made it clear and concise.
                    You have JUST answered your own question with that post.

                    #1) WHY leave something alone that has worked for EVERYONE for YEARS when you can change it to something different?
                    #2) WHY leave the code all clean when by changing something that HAS BEEN stable into something "new" that some one else probably uses?

                    Coder turn-over at Wilcox is all I can think of. They can't keep good people there, so they keep hiring new people, who are rejects from some other company, who then step into a new coding situation and are lost by the LONG EXISTING Pcdmis code, so they "prove" to the "boss" that THEIR way is better, quicker, easier by showing that it takes them (the new guy) a long time to do something the old way whereas it takes a microscopic effort to do it "his" way. In other words, the new guy refuses to learn the existing process and proves his new process is better. BUT, it isn't, it SUCKS for everyone that HAS been using this software and now instead of "clean" Pcdmis code, we now have a bastardization of Pcdmis and 17 other softwares where this hack has previously been employed and been fired.
                    sigpic
                    Originally posted by AndersI
                    I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

                    Comment


                    • #11
                      Originally posted by Matthew D. Hoedeman View Post
                      You have JUST answered your own question with that post.

                      #1) WHY leave something alone that has worked for EVERYONE for YEARS when you can change it to something different?
                      #2) WHY leave the code all clean when by changing something that HAS BEEN stable into something "new" that some one else probably uses?

                      Coder turn-over at Wilcox is all I can think of. They can't keep good people there, so they keep hiring new people, who are rejects from some other company, who then step into a new coding situation and are lost by the LONG EXISTING Pcdmis code, so they "prove" to the "boss" that THEIR way is better, quicker, easier by showing that it takes them (the new guy) a long time to do something the old way whereas it takes a microscopic effort to do it "his" way. In other words, the new guy refuses to learn the existing process and proves his new process is better. BUT, it isn't, it SUCKS for everyone that HAS been using this software and now instead of "clean" Pcdmis code, we now have a bastardization of Pcdmis and 17 other softwares where this hack has previously been employed and been fired.
                      You're probably right....(sigh).

                      Comment


                      • #12
                        Hm, using almost exclusively v4+, I liked the new $$ comments. They break up the flow of features by kicking over to the lefthand side of the screen when in the edit window. It makes it easy for me to pick them out.

                        Comment


                        • #13
                          Originally posted by Chally72 View Post
                          Hm, using almost exclusively v4+, I liked the new $$ comments. They break up the flow of features by kicking over to the lefthand side of the screen when in the edit window. It makes it easy for me to pick them out.
                          I agree Chally. Next best thing to a blank line, which is not possible.

                          Comment


                          • #14
                            Maybe they use $$ because it's just the DMIS code for inserting lines that are not sent to the report and will not display anything when executed?
                            sigpicIt's corona time!
                            737 Xcel Cad++ v2009MR1....SE HABLA ESPAÑOL

                            Comment


                            • #15
                              They use $$ because it reminds us how much money we spent on their software!!!

                              B&S CHAMELEON/PCDMIS CAD++ V2011

                              There are no bugs, only "UNDOCUMENTED ENHANCEMENTS!"

                              sigpic

                              Comment

                              Related Topics

                              Collapse

                              Working...
                              X