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

OnChange Events not working

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

    OnChange Events not working

    I am testing out the latest Alpha version and I have discovered that all of my onchange events (in textbox controls) are getting errors.

    I restarted the server, but that did not help.

    Anyone else seeing this issue?

    I am still developing in an older version, so I haven't changed a UX in the latest version and pushed to the latest version - but everything else is working fine.

    I can't even get an alert('test'); to fire from an onchange event.

    If I move the exact same code to onblur or any other event, it works fine - it's only onchange that is affected. In the console log is says that the event is not defined.

    I tried recalcing all controls, deleting the control and putting it back - no joy. It works fine in my current version, but if I try on the latest, it fails.

    I will be doing more testing but thought I would shoutout here to see if anyone else has encountered this issue.

    #2
    So, I went into the newest version, recompiled a UX and republished - now the onchange events work.

    So there is something going on when using a UX that has not been recompiled recently.

    My live version is from Dec 6, 2020 - so it's getting a little long in the tooth - but the onchange events worked fine until now so far as I know.

    Will do more testing and send a sample to Alpha if I can put something together.

    Comment


      #3
      I'm on 8099 - won't be moving from it as it works (has a few small issues - but nothing I can't manage) and I haven't seen anything in subsequent releases that would make a difference to how I develop.

      Pete
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        I'm trying 8417 and I am not seeing this behavior. But seeing as it was released this morning and your post is from yesterday, I am guessing you are referring to 8368. Every time there is a new version of Alpha, I first do a recalculate of all controls. I have never recompiled and I am not too sure I even know what that means.

        I have actually been on 8000 for some time. Every new version after that had some issue that prevented me from upgrading. But 8417 seems to be promising so far. No issues in my preliminary test runs.

        Comment


          #5
          Rusty,

          I have my live version, from which I do all updates to the system, and I have a dev server. The live version is several versions back.

          I do my development in the same version as my live server and often publish things to dev in order to test them.

          There are some things that will not work properly this way, but the onchange event has never been one of them.

          You are right - if you are actually moving to a new version, you should definitely relalc all controls before doing so. But when you are simply trying out a new version, it is nice if you can install that new version and most things simply work, even if they have not been recompiled.

          I can certainly make a backup copy of the system, recalc everything in the latest version, publish and then test. THEN the onchange event will work.

          But of all the events I would expect to fail, the onchange event is not at the top of the list. It's been the same event since Windows 1.0 and will remain the same until Windows 99 I expect.

          ​The question is - is this the result of a bug, or is this a change in behavior that I'll just have to work with.

          Comment

          Working...
          X