Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Documenting code problem

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

  • Documenting code problem

    In the process of documenting script code I have, run into what appears to be a "glitch" in the code editor.
    In all cases after reaching about 30 carriage returns, from within the editor and using " ' " as the first character for the documentation line.On save and run (using icon button in code editor toolbar) results in a dlg error msg box which, always refers to the last line number of the commented code. Deleting , cutting , copy $ pasting does not solve this problem. The line index after remove line number as referenced in message box returns the subsequent previous line number.
    The only workaround is select all cut , save empty scriptfile, close, open and then paste.

    Any thoughts on this matter?
    “There is nothing like a dream to create the future.”
    But then again:
    Basic research is what I am doing when I don't know what I am doing and to steal ideas from one person is plagiarism; to steal from many is research!

  • #2
    Re: Documenting code problem

    No problem here.
    Care to post an example?

    Comment


    • #3
      Re: Documenting code problem

      No problem here.

      I entered 42 comment lines, then a simple XDialog. Everything saved and ran fine.
      -Steve
      sigpic

      Comment


      • #4
        Re: Documenting code problem

        I have had this happen in ver 8 and 7 and it was a missing end if statement that was the culprit. Sometimes the error messages are a bit cryptic.
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


        • #5
          Re: Documenting code problem

          First I write the code and run it. Only when I have the required result do I start the commenting procedure.
          “There is nothing like a dream to create the future.”
          But then again:
          Basic research is what I am doing when I don't know what I am doing and to steal ideas from one person is plagiarism; to steal from many is research!

          Comment


          • #6
            Re: Documenting code problem

            Chris,
            If the code is not too long, post it and we can look at it.
            Mike W
            __________________________
            "I rebel in at least small things to express to the world that I have not completely surrendered"

            Comment


            • #7
              Re: Documenting code problem

              see this thread
              “There is nothing like a dream to create the future.”
              But then again:
              Basic research is what I am doing when I don't know what I am doing and to steal ideas from one person is plagiarism; to steal from many is research!

              Comment


              • #8
                Re: Documenting code problem

                Originally posted by christobal View Post
                see this thread
                I'm by no means that familiar with xdialog, but shouldn't there be a closing parentheses after the last %dlg% tag?
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment


                • #9
                  Re: Documenting code problem

                  Have been watching this because I am having problems in the other thread because of the javascript but no Robin there is no need for a terminating close bracket. the
                  Code:
                  <<%dlg%....%dlg%
                  serves as a wrapper for the dialog layout commands

                  Comment


                  • #10
                    Re: Documenting code problem

                    Originally posted by Lance Gurd View Post
                    Have been watching this because I am having problems in the other thread because of the javascript but no Robin there is no need for a terminating close bracket. the
                    Code:
                    <<%dlg%....%dlg%
                    serves as a wrapper for the dialog layout commands
                    Now I see that there is no opening parentheses, hence no need for a closing one.

                    What about this statement:

                    Code:
                    <cr:DateEdit id = "de" format=[COLOR=red]"dd /MM /yyyy"[/COLOR]/>
                    Should there be spaces in this format statement? I have noticed that the genie will sometimes insert spaces which need to be removed.
                    Robin

                    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                    Comment


                    • #11
                      Re: Documenting code problem

                      Code:
                      <cr:DateEdit id = "de" format="dd /MM /yyyy"/>
                      The editor doesn't allow comments within the HTML code it sees them as part of the html syntax. With regards to the spacing, this is javascript syntax and out of the scope of the code editor because it is between the html <<%html% , %html% tags of the script.
                      “There is nothing like a dream to create the future.”
                      But then again:
                      Basic research is what I am doing when I don't know what I am doing and to steal ideas from one person is plagiarism; to steal from many is research!

                      Comment


                      • #12
                        Re: Documenting code problem

                        The editor doesn't allow comments within the HTML code it sees them as part of the html syntax.
                        No.
                        Same way as in xdlg.

                        Comment


                        • #13
                          Re: Documenting code problem

                          Hi Chris,

                          Originally posted by christobal View Post
                          ...The only workaround is select all cut , save empty scriptfile, close, open and then paste.

                          Any thoughts on this matter?
                          I have seen something similar at times where there is a line that is causing a syntax error. There was some invisible character that seemed to be causing issues with the compile.

                          One solution is to retype the offending line after deleting the entire line (and sometimes including the line above and below in case it was at the beginning or end of the line.

                          Another way is to export the code, then import it back in. This may solve the issue.

                          As far as commenting code, I in a 10000 line function, I have about 2500 additional lines of comments, some running on for probably 300 lines. Be careful that you do not include special key words at the beginning of the line, e.g.

                          'DESCRIPTION
                          'LIMITATIONS
                          'PASSWORD

                          etc.
                          Regards,

                          Ira J. Perlow
                          Computer Systems Design


                          CSDA A5 Products
                          New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                          CSDA Barcode Functions

                          CSDA Code Utility
                          CSDA Screen Capture


                          Comment

                          Working...
                          X