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

Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

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

    #16
    Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

    I don't agree with you at all, what's happening now in declaring errors, should have happened up until now. Anyhow it's resolved. The reason I say this is, if you recalculate all controls most, if not all errors are corrected, - so if what you say is correct, how does this action correct developer error if its totally to blame.
    Last edited by peteconway; 08-22-2017, 03:41 AM.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #17
      Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

      In the last release build (4491), we added a alert box to capture errors generated from JavaScript added by user functions. In builds 4346 and older, errors in that code were written to the console log, but not shown to the user. This made troubleshooting the code difficult as the errors were not visible and often went unnoticed or ignored. Later pre-release builds added the verbose detailed message which can now be turned off in the component properties.

      A side effect of both additions was all errors found when executing JavaScript were captured and shown in the alert. These were not limited to errors in user code, but included errors caused by running an older component in a newer build where some supporting code had changed, or the system JavaScript file had changed. If the problem was not in user added code, recalculating the component, resaving the component, or just clearing the browser cache would normally cure the problem. But errors in user code would still show the alert() as they still existed.

      When the verbose alert was made conditional, the first simple alert boxes were removed. However, one alert was missed. This has now been corrected in the next pre-release. If you turn off the detailed error reporting, the error reporting behavior will be the same as in builds 4346 and older. Errors in user code may not be visible.

      If you suspect an error in user code, turn on the detailed JavaScript error reporting for testing. This will give some clues on the nature and source of the error. Most browsers also include troubleshooting tools to show the console and show errors that are not reported in a message box.

      Comment


        #18
        Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

        Thanks Jerry, appreciate this clarification. All the best.
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #19
          Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

          How do you turn on the detailed JavaScript error reporting for testing?

          Comment


            #20
            Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

            Originally posted by adrian4289 View Post
            How do you turn on the detailed JavaScript error reporting for testing?
            Advanced properties ...

            Capture.jpg
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #21
              Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

              Thank You!

              Comment


                #22
                Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                I am still seeing the pesky JS Errors.

                I am running a tabbed UI that loads several UXs.

                Today I installed the latest Pre-Release Build 4538-4945.

                Next I unchecked "Capture detailed javascript error information" on all UXs.

                Then I re-calculated the tabbed UI and all the UX components at the component level.

                The errors occur when I download a file.

                Specifically, If I have UXs open in the tabbed UI, and and have not closed any of the UXs since first launching the browser (Chrome), I can download a file with no errors. BUT....

                If I should close one or more of the UXs, by clicking the "x" in the tab, and then download a file, upon clicking "Save" to save the file to a local folder, I get a js error that references the alias of the tab that was just closed.

                It will fire one js error alert for each UX that was opened and then closed.

                Untitled.png


                And just now I got one of these...

                Untitled2.png
                Last edited by Pizzadude; 08-22-2017, 01:12 PM.

                Comment


                  #23
                  Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                  Here is a video showing what I am seeing...

                  https://www.screencast.com/t/r5uynfrV

                  Comment


                    #24
                    Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                    Here is an example of the error being detected, but I have not been able to figure out how to fix it.

                    Untitled.png

                    Comment


                      #25
                      Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                      Joe, I'm seeing a few of those similar type of errors and I'm wondering if they are related to the TabbedUI somehow.
                      Mine are all "TBI_COMPONENTNAME_xxxxxxxxxx_DlgObj is not defined". The TabbedUI seems to be the only component that does not have the option to suppress the error messages.

                      Error.jpg

                      I don't know, I'm just guessing now and like you, I don't know how to fix those either. If you can produce a reproducible test case, suggest a bug report to Alpha. I'm not sure how to reproduce mine yet.

                      Anyone able to help suggest a way to track these down???


                      Actually, I can reproduce this very similar to you ... but in a bit of an odd way at the same time.

                      1. Open a component in the TabbedUI
                      A. Don't close the component and open Firebug .. the error doesn't pop up
                      OR
                      B. Close the component and open Firebug .. the error pops up (for every component that was opened then closed).

                      I'm not sure what Firebug has to do with it, but that's the only way I can reliably reproduce it at the moment.
                      Last edited by iRadiate; 08-23-2017, 09:12 AM.
                      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                      Comment


                        #26
                        Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                        Stephen, I think the tabbed UI is generating the particular error you are referring to. I am going to see if I can make a simple example and reproduce it, and then send in a bug report.

                        this._beforePersistToStorage is a different problem. Anyone else seeing this?

                        Comment


                          #27
                          Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                          Cross your fingers Jerry is watching this post. He may chime in.
                          Insanity: doing the same thing over and over again and expecting different results.
                          Albert Einstein, (attributed)
                          US (German-born) physicist (1879 - 1955)

                          Comment


                            #28
                            Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                            HERE IS SOME IMPORTANT ADVICE UNTIL THIS SETTLES DOWN: Make certain you have a full set of AA Backups of your project, from what I have seen it looks as though something gets placed in the project folder when you make an edit in your component, then things can go haywire.. I have found the only way back from this is to restore the project and re-publish it. Save some yourself heartache.
                            Insanity: doing the same thing over and over again and expecting different results.
                            Albert Einstein, (attributed)
                            US (German-born) physicist (1879 - 1955)

                            Comment


                              #29
                              Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                              Originally posted by Pizzadude View Post
                              Stephen, I think the tabbed UI is generating the particular error you are referring to. I am going to see if I can make a simple example and reproduce it, and then send in a bug report.

                              this._beforePersistToStorage is a different problem. Anyone else seeing this?
                              Joe, here is something Jerry showed me that you can try. From the Web Projects Control Panel, Click Edit, Search In All Web Project Files

                              Search_Project.jpg

                              In the search for field, enter this._beforePersistToStorage and it should return all places where that code is being called. Then you can examine it further or try commenting it out.
                              Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                              Comment


                                #30
                                Re: Pre-release Build: 4530 removes the pesky JS Errors - also appear stable.

                                In the search for field, enter this._beforePersistToStorage and it should return all places where that code is being called. Then you can examine it further or try commenting it out.
                                Interesting... It found only one item:

                                FactoringCompanies.a5wcmp| this._beforePersistToStorage({mode:'incrementalRefresh', data: data});

                                I don't think FactoringCompanies.a5wcmp was open when the error was generated. I will explore further.

                                Comment

                                Working...
                                X