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

Official 2.0 Release not Working with UX Component

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

    Official 2.0 Release not Working with UX Component

    I have a complex UX component that was completed about 1 month ago that no longer works in working preview or any of the browser previews. I get an error of "Script Error" and a URL of "a5res:javascript/a5.js". This error repeats approx. 8 times on working preview and the page rendered shows 4 sets of the "First page, Last page, Previous page, and Next page" icons.

    Following is what I have tried to correct:
    1. I have deleted any linked JS and CSS in addition to any custom xbasic and javascript functions inside the UX to no avail.
    2. I have created a new UX and copied the controls from clipboard.
    3. I have restored the prior 10 backups with the same result.


    Is there anything else the community can suggest to troubleshoot or does this appear to be an issue with 2.0?

    On a side note, I would not have even noticed this error if I didn't accidently call this embedded UX in a application I am working on. When it loaded, the styling was off and the images were not loading which prompted me to directly open the UX to see what the problem was. Once open, pressing the working preview revealed the script error. I can confirm that the UX worked 1 week ago as it has for a while.

    Any assistance would be appreciated.
    Thanks,
    James

    #2
    Re: Official 2.0 Release not Working with UX Component

    In the UX builder with the Controls displayed, have you tried clicking the "menu" option in the toolbar, just above the control list, and selecting "Recalculate All Controls" ?

    I had a UX go bad two weeks ago. I cannot be sure, but I think it had to do with updating alpha. I found the problem by running Chrome with the debugger turned on and when it caught the error in the main a5 javascript file I used the callstack in chrome's debugger to work backwards, placing break points until I could figure out that a particular control was triggering the problem. Nothing seemed to be wrong in the source for that control when looking at its properties in the builder. Deleting the control from the UX and putting it back in from scratch solved the problem.

    Comment


      #3
      Re: Official 2.0 Release not Working with UX Component

      Thanks for the reply Rich. Yes I did. Several Times. To update, I isolated the issue to a specific List control inside the UX. I deleted the list and recreated it from scratch using a copy of the one I deleted (a quasi cheat sheet). The recreated list works which makes absolutely no sense to me considering it was an exact reproduction of the one I deleted. Anyway, it's all good now.
      Thanks,
      James

      Comment


        #4
        Re: Official 2.0 Release not Working with UX Component

        Wow James, that is really an issue that will be extremely good to know why is this happening with some components.

        Whenever I need to download an Alpha update, it scare the hell out of me due to this kind of hidden issues that may happens from time to time, obviously due to all different web/mobile projects it may be difficult to ping point the exact reason why your component was not working with the update, but if anybody can provide an inside on this, would be very helpful for all.
        Edhy Rijo
        Progytech
        (Computer Consultants)
        The makers of CardTracking.Net
        www.progytech.com

        Comment


          #5
          Re: Official 2.0 Release not Working with UX Component

          It actually does make sense that a recreated list would work. The code that alpha uses to build the component probably changed in between the build you used to create the UX and the current one. Somehow it wasn't playing nice with the new building code.

          Things like this happened to me multiple times throughout the pre-releases. I just did what you did and narrowed down the problem. Once I did that, I'd send in a bug report, letting them know what they broke. They'd usually have a quick fix for me right away or at least the next day.

          Comment


            #6
            Re: Official 2.0 Release not Working with UX Component

            Hi Jinx,

            Thanks for explanation, much appreciated.
            Edhy Rijo
            Progytech
            (Computer Consultants)
            The makers of CardTracking.Net
            www.progytech.com

            Comment

            Working...
            X