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

Out of memory/sys_send_keys

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

    Out of memory/sys_send_keys

    As I continue scrabbling my way up the XBasic learing curve, I have run into two problems.

    1. I am running A5V4.5 under XP. As I am entering a script into an event, using the Inline XBasic editor, after a while I get an error, "Out of Windows Memory," which prevents me from entering any more code. The amount of code in the window is far less than some of the examples in the book. Can this be corrected or circumvented?

    2. I am trying to manipulate the contents of an edit control on a form directly. It's easy to read the contents (stuff = :form:control.text), but when you try to alter the contents of an active control (:form:control.text = stuff) the background goes black and the form locks up. I had also thought of using sys_send_keys, but then stumbled on a behavior which seems bizarre and illogical to me. Let's say you have "abc" in the control and you want to replace it with "xyz." From the keyboard you would use {HOME}shift{END}[to highilight all] and then type "xyz." Now, if you send this sequence of keys via sys_send_keys, the unexpected happens:

    sys_send_keys("{HOME}{+END}xyz")

    results in "abcxyz", all highlighted. In other words, the letters reach the control first, THEN the control keys. What gives?

    Henry Gibbons

    #2
    RE: Out of memory/sys_send_keys

    Henry

    I can help with the first problem. Inline xbasic is very limited in the amount of code. When you hit the limit, you get the "out of memory" message. Switch to regular xbasic. While there are limitiation on the amount of code in xbasic, the limitiation is rather huge. The limit is somewhere above 1500 lines.

    Jerry

    Comment


      #3
      RE: Out of memory/sys_send_keys

      try breaking it up into three sends - I think it may be misinterpreting what you want

      Comment


        #4
        RE: Out of memory/sys_send_keys

        Thanks Jerry. It wasn't immediately clear to me that there was a difference between "Inline Xbasic" and "Xbasic," and that you have to convert Xbasic to Xbasic to get the larger code editing window. The manual is not clear on this distinction.

        Speaking of stuff the manuals are not clear on, there are many references to "cards." The index entry for "Cards" in the reference manual refers to page 16, but there is no mention there of cards. Is this old terminology that just hasn't been edited out?

        Henry

        Comment


          #5
          RE: Out of memory/sys_send_keys

          William -

          Thanks for the suggestion. I already tried that, but the result is the same. And you can't use the sleep() function, which stops everything. Puzzling.

          Henry

          Comment


            #6
            RE: Out of memory/sys_send_keys


            Henry,

            "Cards" refers to saved scripts in Alpha Five, Version 1.

            -- tom cone

            Comment


              #7
              RE: Out of memory/sys_send_keys


              Henry,

              If the control is for a field in your table, you don't need to 'select' the text in the control in order to change it. Xbasic simplifies this. Check the Xbasic Reference Manual Ch 15, working with fields.

              You will find what you need to 'put' values to a table field, by placing the table in change mode, and using fieldpointer.value_put() (or any of several other methods)

              If you're changing the text in a label you can write directly to the control's text or value properties, depending on what you need.

              :formname:objectname.text = "xyz"

              -- tom cone

              Comment


                #8
                RE: Out of memory/sys_send_keys

                Tom -

                Actually, while looking for something else, I found what this is. Cards - p. 16 in the user manual is a typo - it should read Cards - p. 164. There cards refers to the forms you fill out directly to perform various actions, as opposed to using the Genies, which fill out the cards for you.

                Comment


                  #9
                  RE: Out of memory/sys_send_keys

                  Thanks, Tom

                  I think I was getting messed up in calling a dialog from the OnKey event - when that happens, and the focus moves away from the edit control, it must change the mode. I'm still not entirely clear about the sequence of events. However, I managed to get this to work finally. Thanks for your help.

                  Henry Gibbons

                  Comment

                  Working...
                  X