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

Modifying Form Events on the fly

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

    Modifying Form Events on the fly

    I thought at one time I had this figured out, but I guess I have misplaced my previous work on it. I have searched the forum and found what looks like a solution, but cannot make that work.

    Here's the question: How may I modify a form's events (OnKey, OnTimer, etc.) on the fly? I would like to use another open form as the template for the event code and set the code up right after the form initializes from a form-loading script that I use. I've studied the code in the manual (page 56) and applied it as directed to no avail, but the manual specifically states that the code shown in it applies to object events on a form, not form events themselves.

    Any help is greatly appreciated.

    Tom Lyon

    #2
    RE: Modifying Form Events on the fly

    Tom,
    The following script will show your form's on key event:
    showcode = :My_form.code.OnKey
    ui_msg_box("Display Onkey script",showcode)

    It is text. I assume you could change it with something like the following:

    newcode = "first line" + chr(13) + chr(10) + "second line"
    :My_form.code.OnKey = newcode

    Comment


      #3
      RE: Modifying Form Events on the fly

      I get 'argument is incorrect data type when issuing:
      showcode = :PIM6.code.OnKey
      ui_msg_box("Display Onkey script",showcode)

      It's a multiline script..going to try it with a single line script.

      Comment


        #4
        RE: Modifying Form Events on the fly

        Ran into some more info.

        I wrote this script to test things out:

        PIMdata = :Pimmenu.code.OnKey
        PIMfile = file.open("alpha5ca5PIMPIMkey.txt", FILE_RW_SHARED)
        PIMfile.write(PIMdata)
        PIMfile.close()
        PIMfile = file.open("alpha5ca5PIMPIMkey.txt", FILE_RW_SHARED)
        :PIM6.code.OnKey = ""
        while .not. PIMfile.EOF()
        PIMline = PIMfile.read_line() + chr(13) + chr(10)
        :PIM6.code.OnKey = :PIM6.code.OnKey + PIMline
        end while
        PIMfile.close()
        PIMdata = :PIM6.code.OnKey
        PIMfile = file.open("alpha5ca5PIMPIM6key.txt", FILE_RW_SHARED)
        PIMfile.write(PIMdata)
        PIMfile.close()

        After running it, PIMkey.txt has a file size of 3594 bytes.
        PIM6key.txt has a file size of 1050 bytes.
        Coincidentally, pasting all but the last line of PIM6key.txt into the OnKey code of PIM6 works. Pasting the last line gives the 'Out of Windows Memory" error. I'd guess that when using XBasic to modify code, an action script is assumed, which reaches the 1K character limit.

        Tom Lyon

        Comment


          #5
          RE: Modifying Form Events on the fly

          you can certainly make your onkey code
          script_play(global_script)
          which should get around any size limit.

          Comment


            #6
            RE: Modifying Form Events on the fly

            Hi Peter,

            I would normally use a function call, but it's the same difference. However, I would not normally do that for certain events, particularly the OnTimer and OnKey events. These are so low-level, that any extra time for the script play or function call could have an impact on keyboard responsiveness.

            Instead, replacing the code with the desired code (hopefully written as efficiently as possible) would be the preferred method.

            We'll have fun arguing the pros and cons next week! See you at the Alpha 5 Conference! :?)

            Regards,

            Ira J. Perlow
            Computer Systems Design & Associates
            [email protected]
            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


              #7
              RE: Modifying Form Events on the fly

              I tried the script method..it's just tolerable, but not much fun. Hopefully, I can rewrite the code. I only need to shave 2/3 of it :)

              Tom Lyon

              Comment


                #8
                RE: Modifying Form Events on the fly

                If using global scripts makes it "just tolerable" you mean generally poor keyboard responsiveness, you could try something else.

                1) If you have a number of fields that need some fancy key behavior, you could turn it on at the onarrive event of the field obj. Then you could turn it off when departing the field object.This way, your basic data entry would be unaffected by extensive onkey code except when editing a particular field.
                2) If you have any large tasks that are coded into the onkey event, put the code for the task on a button and execute a buttonpush in the onkey event code.If the task is somewhat time consuming ( like a guery ) the overhead time for the buttonpush won't be a factor.

                Comment


                  #9
                  RE: Modifying Form Events on the fly

                  I understand what you are suggesting. However, I guess I should explain why I want to modify event code on the fly. I am looking to code a development tool. I want to be able to modify the code in a source form and copy it to the actual forms that will be using it on the fly, of which there are 7. I have tried my darndest to reduce the size of the code, but cannot get it to the 1000 character limit. I'm trying to push A5 a little harder than it was designed for and it is winning the battle.

                  I will learn to get more proficient with cut and paste :)

                  Tom Lyon

                  Comment

                  Working...
                  X